CompaniesContentstackIncidents
Contentstack: Contentstack Launch - Service Disruption - Cloudflare Incident
Google Cloud outage, Jun 12, 2025 · 101 vendors, 107 incidents
Contentstack’s incident is a second hop: it blames Cloudflare, which was affected by Google Cloud. (hop 2, posted +3 h 41 min vs the first vendor naming Google Cloud)
“…Contentstack Launch - Service Disruption - Cloudflare Incident Earlier today, there was an unexpected period of downtime with our Contentstack platform. Around 2 PM ET, we experienced an upstream outa…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Google Cloud<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>29 vendors, 28 blamed Google Cloud<br/>Pinecone, Northflank, imgix +26"]:::blames
root --> h1
h4["1 to 4 hours later<br/>12 vendors, 11 blamed Google Cloud<br/>Smartsheet, Daily, Confluent +9"]:::blames
root --> h4
later["Later<br/>1 vendor, 1 blamed Google Cloud<br/>Zilliz"]:::blames
root --> later
p0["Firebase<br/>own incident not archived"]:::inferred
root -.-> p0
k0["Codeium, Windsurf<br/>+13 min"]:::hop2
p0 -->|"blamed Firebase"| k0
p1["Anthropic<br/>posted +28 min, did not name Google Cloud"]:::timing
root -.-> p1
k1["GitHub, GitHub Copilot<br/>+24 min"]:::hop2
p1 -->|"blamed Anthropic"| k1
p2["Cloudflare<br/>own incident not archived"]:::inferred
root -.-> p2
k2["Doppler, Jupyter (Anaconda), Socket +4<br/>+35 min to +3 h 41 min"]:::hop2
p2 -->|"blamed Cloudflare"| k2
me["Contentstack (this incident)<br/>posted +3 h 41 min"]:::me
p2 -->|"blamed Cloudflare"| meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Affected components: Launch - Web ApplicationMicrosoft Azure US Region - Launch - Web ApplicationLaunch - Content Delivery Network (CDN)Microsoft Azure US Region - Launch - Content Delivery Network (CDN)Google Cloud Platform US Region - Launch - Management APILaunch - Management APIAmazon Web Services US Region - Launch - Web ApplicationLaunch - Web ApplicationGoogle Cloud Platform US Region - Launch - Edge ServicesLaunch - Edge ServicesLaunch - Web ApplicationMicrosoft Azure EU Region - Launch - Web ApplicationGoogle Cloud Platform EU Region - Launch - Content Delivery Network (CDN)Launch - Content Delivery Network (CDN)Amazon Web Services US Region - Launch - Edge ServicesLaunch - Edge ServicesLaunch - Content Delivery Network (CDN)Microsoft Azure EU Region - Launch - Content Delivery Network (CDN)Launch - Edge ServicesMicrosoft Azure EU Region - Launch - Edge ServicesAmazon Web Services EU Region - Launch - Web ApplicationLaunch - Web ApplicationGoogle Cloud Platform EU Region - Launch - Management APILaunch - Management APILaunch - Management APIMicrosoft Azure EU Region - Launch - Management APIAmazon Web Services US Region - Launch - Content Delivery Network (CDN)Launch - Content Delivery Network (CDN)Amazon Web Services EU Region - Launch - Content Delivery Network (CDN)Launch - Content Delivery Network (CDN)Google Cloud Platform US Region - Launch - Web ApplicationLaunch - Web ApplicationGoogle Cloud Platform US Region - Launch - Content Delivery Network (CDN)Launch - Content Delivery Network (CDN)Google Cloud Platform EU Region - Launch - Web ApplicationLaunch - Web ApplicationLaunch - Management APIMicrosoft Azure US Region - Launch - Management APIAmazon Web Services EU Region - Launch - Management APILaunch - Management APIAmazon Web Services US Region - Launch - Management APILaunch - Management APILaunch - Edge ServicesMicrosoft Azure US Region - Launch - Edge ServicesGoogle Cloud Platform EU Region - Launch - Edge ServicesLaunch - Edge ServicesAmazon Web Services EU Region - Launch - Edge ServicesLaunch - Edge Services
Timeline of updates
- investigating
Please be informed that sites hosted on Contentstack Launch are currently experiencing 500 errors due to an ongoing Cloudflare outage. Our CDN provider is currently experiencing an issue that may be impacting site performance or availability. Our team is actively working with Cloudflare to expedite resolution. We appreciate your understanding and patience during this time. For any urgent concerns, please don’t hesitate to contact our Customer Success Team.
- investigating
Our team is actively monitoring the state of the Cloudflare Outage. We will continue to provide updates as more information becomes available. You can also track real-time updates on the Cloudflare Status Page. https://www.cloudflarestatus.com/
- monitoring
Cloudflare services have begun to recover, and Launch sites appear to be gradually coming back online. Cloudflare is actively working to fully restore stability. We’re closely monitoring the situation and will share updates as things progress.
- monitoring
Launch sites have been fully recovered as services have resumed from Cloudflare. We are closely monitoring the situation and will share updates as it progresses.
- resolved
Earlier today, there was an unexpected period of downtime with our Contentstack platform. Around 2 PM ET, we experienced an upstream outage that affected our Launch service. This stemmed from technical issues with our CDN provider (Cloudflare), a service we rely on for speed and reliability. We know this disruption was likely very frustrating to you, as it was to us. Cloudflare service full availability took 3 hours 12 minutes to return, and Contentstack Launch service was fully restored immediately. Although it's rare to see major services go down, it did happen this time - and we're continuing to attempt to learn more about what happened here (as are many other Cloudflare customers). Thank you for your patience and continued trust. We will review our system to improve the reliability of our CDN provider. We’re committed to delivering the dependable, enterprise-grade experience you expect. If you have any concerns or feedback, we are here to help.
Changes Rewindex caught on this incident
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Contentstack profileRecent Contentstack incidentsMarkdownJSON