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…”
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.
What changed
Struck in red is what Contentstack removed; blue is what they added. Muted text is unchanged context.
BeforeAfter
AddedTitle#1
Before: not present
After: Contentstack Launch - Service Disruption - Cloudflare Incident
AddedImpact#2
Before: not present
After: critical
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2025-06-12 21:35 UTC
AddedResolved time#5
Before: not present
After: 2025-06-12 21:35 UTC
AddedAffected components#6
Before: not present
After: Amazon Web Services EU Region - Launch - Content Delivery Network (CDN), Amazon Web Services EU Region - Launch - Edge Services, Amazon Web Services EU Region - Launch - Management API, Amazon Web Services EU Region - Launch - Web Application, Amazon Web Services US Region - Launch - Content Delivery Network (CDN), Amazon Web Services US Region - Launch - Edge Services, Amazon Web Services US Region - Launch - Management API, Amazon Web Services US Region - Launch - Web Application, Google Cloud Platform EU Region - Launch - Content Delivery Network (CDN), Google Cloud Platform EU Region - Launch - Edge Services, Google Cloud Platform EU Region - Launch - Management API, Google Cloud Platform EU Region - Launch - Web Application, Google Cloud Platform US Region - Launch - Content Delivery Network (CDN), Google Cloud Platform US Region - Launch - Edge Services, Google Cloud Platform US Region - Launch - Management API, Google Cloud Platform US Region - Launch - Web Application, Launch - Content Delivery Network (CDN), Launch - Edge Services, Launch - Management API, Launch - Web Application, Microsoft Azure EU Region - Launch - Content Delivery Network (CDN), Microsoft Azure EU Region - Launch - Edge Services, Microsoft Azure EU Region - Launch - Management API, Microsoft Azure EU Region - Launch - Web Application, Microsoft Azure US Region - Launch - Content Delivery Network (CDN), Microsoft Azure US Region - Launch - Edge Services, Microsoft Azure US Region - Launch - Management API, Microsoft Azure US Region - Launch - Web Application
AddedUpdateinvestigating#7
Before: not present
After: 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.
AddedUpdateinvestigating#8
Before: not present
After: 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/
AddedUpdatemonitoring#9
Before: not present
After: 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.
AddedUpdatemonitoring#10
Before: not present
After: 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.
AddedUpdateresolved#11
Before: not present
After: 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.