Critical incident

Contentstack: Contentstack – Azure NA – Web Application Unavailability

Affected: Web Application

Current status of Contentstack: Operational — live Contentstack status

Timeline

1. Jun 17, 2026, 13:23 UTC
   investigating
   We are currently investigating an issue affecting the Web Application in the Microsoft Azure US Region. During this time, users may experience difficulties loading the Contentstack Application. Other regions and content delivery of already-published content remain unaffected. Our engineering team has been mobilized and is actively working to identify the root cause and restore normal service. We understand the impact this may have on your operations and are treating this with the highest priority. Customer Action: No action is required from customers at this time. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].
2. Jun 17, 2026, 13:32 UTC
   identified
   The root cause of the issue affecting the Web Application in the Microsoft Azure US Region has been identified. Our engineering team is currently implementing a fix to restore normal service. Other regions and content delivery of already-published content remain unaffected. Customer Action: No action is required from customers at this time. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].
3. Jun 17, 2026, 13:38 UTC
   monitoring
   The issue affecting the Web Application in the Microsoft Azure US Region has been mitigated and services are operating normally. Our team will continue monitoring system performance closely to ensure stability. Customer Action: If you are still experiencing difficulties loading the Contentstack application, please clear your local browser cache and reload the page. If you encounter any difficulties accessing our services, please reach out to our Customer Success team for assistance at [email protected].
4. Jun 17, 2026, 13:44 UTC
   resolved
   This incident has been resolved.

Updates as published by Contentstack (original).