Vendor reports: major outageResolved · vendor status “resolved”Official status API

Contentstack Launch - Service Disruption - Cloudflare Incident

Reported by Contentstack · Hosting, CDN & Edge · source last read just now

Official source (opens in a new tab)
Vendor start
Jun 12, 2025, 21:35 UTC
Vendor's clock
Resolved
Jun 12, 2025, 21:35 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
Not available
Needs both vendor times

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Contentstack reports major outage: "Contentstack Launch - Service Disruption - Cloudflare Incident".[E1, E2]
  • The vendor marked it resolved at 2025-06-12 21:35 UTC.[E3, E7]

Affected products and regions

  • Components: Launch - Web Application, Launch - Web Application, Launch - Management API, Launch - Management API, Launch - Content Delivery Network (CDN), Launch - Content Delivery Network (CDN), Launch - Edge Services, Launch - Edge Services, Launch - Web Application, Launch - Web Application, Launch - Management API, Launch - Management API, Launch - Content Delivery Network (CDN), Launch - Content Delivery Network (CDN), Launch - Web Application, Launch - Web Application, Launch - Edge Services, Launch - Edge Services, Launch - Management API, Launch - Management API, Launch - Content Delivery Network (CDN), Launch - Content Delivery Network (CDN), Launch - Edge Services, Launch - Edge Services.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2025-06-12 21:35 UTC · summary s1, evidence 1253aba0e3ffd87a

Evidence (7)
  1. E1Contentstack reports major outage. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Contentstack Launch - Service Disruption - Cloudflare Incident". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2025-06-12 21:35 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Launch - Web Application, Launch - Web Application, Launch - Management API, Launch - Management API, Launch - Content Delivery Network (CDN), Launch - Content Delivery Network (CDN), Launch - Edge Services, Launch - Edge Services, Launch - Web Application, Launch - Web Application, Launch - Management API, Launch - Management API, Launch - Content Delivery Network (CDN), Launch - Content Delivery Network (CDN), Launch - Web Application, Launch - Web Application, Launch - Edge Services, Launch - Edge Services, Launch - Management API, Launch - Management API, Launch - Content Delivery Network (CDN), Launch - Content Delivery Network (CDN), Launch - Edge Services, Launch - Edge Services. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2025-06-12 21:35 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Launch - Web Application, Launch - Web Application, Launch - Management API, Launch - Management API, Launch - Content Delivery Network (CDN), Launch - Content Delivery Network (CDN), Launch - Edge Services, Launch - Edge Services, Launch - Web Application, Launch - Web Application, Launch - Management API, Launch - Management API, Launch - Content Delivery Network (CDN), Launch - Content Delivery Network (CDN), Launch - Web Application, Launch - Web Application, Launch - Edge Services, Launch - Edge Services, Launch - Management API, Launch - Management API, Launch - Content Delivery Network (CDN), Launch - Content Delivery Network (CDN), Launch - Edge Services, Launch - Edge Services

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

Contentstack is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Jun 12, 2025, 21:35 UTCVendor-reported startVendor time
  2. Jun 12, 2025, 21:35 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.