Zephyr Scale experienced a major incident on June 10, 2026 affecting Zephyr Cloud (US) and Zephyr Cloud REST API(US) and 1 more component, lasting 7h 30m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 10, 2026, 03:16 PM UTC
Some tenants are facing error due to authorization errors, unable to use Zephyr.
- identified Jun 10, 2026, 03:17 PM UTC
The issue is connected to an incident with Atlassian: https://jira-software.status.atlassian.com/incidents/c436c8y239dv We are following up with the to understand the timeline for fixing it.
- monitoring Jun 10, 2026, 03:19 PM UTC
Atlassian has fixed the issue. We are monitoring Zephyr to see if the authentication is being fixed. It might take longer for Zephyr to recover, as Jira has to process missed scheduled triggers to update the authentication for impacted users.
- resolved Jun 10, 2026, 03:21 PM UTC
All tenants have been updated, and the system is fully operational again.
- postmortem Jun 10, 2026, 03:21 PM UTC
The issue has been caused by an error with the Forge platform, logged by Atlassian on their StatusPage: [https://jira-software.status.atlassian.com/incidents/c436c8y239dv](https://jira-software.status.atlassian.com/incidents/c436c8y239dv) With Forge not processing scheduled tiggers properly, Zephyr can’t refresh authorization tokens for tenants. This has not impacted all tenants, but about 300-400 tenants were still impacted. After the issue was fixed with Atlassian, it took a long time for all authorization tokens to be refreshed for Zephyr. We are following up with Atlassian to check why it has taken so long, and what can be done in the future to minimize the impact for Forge apps. We apologise any inconvenience.