Orchestry experienced a major incident on July 18, 2024 affecting Web Application and API and 1 more component, lasting 5h 53m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 18, 2024, 11:00 PM UTC
We are currently investigating this issue.
- investigating Jul 18, 2024, 11:06 PM UTC
We are continuing to investigate this issue.
- investigating Jul 19, 2024, 12:31 AM UTC
We are continuing to investigate this issue.
- monitoring Jul 19, 2024, 01:33 AM UTC
Outage due to underlying Microsoft Azure Central Region Outage on July 18th 2024. Orchestry services have been restored and we are now monitoring.
- resolved Jul 19, 2024, 04:53 AM UTC
This incident has been resolved.
- postmortem Jul 19, 2024, 10:02 PM UTC
**Postmortem: Degraded Orchestry Services Due to Azure Outage in US Central Region - July 18, 2024** **Overview:** On July 18, 2024, Orchestry experienced a significant outage in its US region, impacting various services and disrupting operations. The outage lasted approximately 5 hours, starting in the evening Pacific Time \(PT\). The root cause of the outage was traced to the [Azure US Central outage](https://azure.status.microsoft/en-us/status/history/) - Tracking ID: 1K80-N\_8. With the exception of Job Queues, Orchestry’s Services failed over to Azure’s US East region. This kept services online but with significant degradations in performance until the Azure US Central region was restored and Orchestry’s US Services recovered.