Live / Contentstack / Incident
Contentstack: Contentstack – Azure EU – Multiple Services Disruption
Contentstack · contentstack.comMajor incidentResolved2026-11-04 16:34 UTC
Public — what happened
Summary
Contentstack said a disruption in its Azure EU region, starting at 11:59 UTC on 2026-11-04, affected several services. Customers there could see errors when retrieving content through its delivery APIs, failed or delayed publishing, and slow webhook delivery, while other regions were not affected. The company said a primary database server problem was identified at 12:00 UTC and traffic was moved to a healthy server, but publishing delays continued, and at 13:16 UTC it said a long-running background data operation was putting heavy load on its systems. At 16:24 UTC Contentstack said the problem had been mitigated and publishing was working normally, and the incident was marked resolved at 16:34 UTC, with customers asked to republish any entries that were still unpublished.
Affected
Content Management API, Content Delivery API, GraphQL Delivery API, Webhook Dispatcher
Timeline
- Started — 2026-11-04 11:59 UTC
- Investigating — 2026-11-04 11:59 UTC
- Identified — 2026-11-04 12:00 UTC (4 updates)
- Monitoring — 2026-11-04 16:24 UTC
- Resolved — 2026-11-04 16:34 UTC · 4h 35m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Contentstack against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Contentstack: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Contentstack report →
More from Contentstack
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.