Zephyr Scale had 5 outages in the last 2 years totaling 29h 5m of downtime — averaging 0.2 incidents per month.
There were 5 Zephyr Scale outages since November 27, 2025 totaling 29h 5m of downtime. Each is summarised below — incident details, duration, and resolution information.
The problem was due to a build minification error when a new import was added, which caused the import to become "undefined" when the test library was opened, causing the main app to crash
We identified an issue when trying to open the Test Cycle edit view.
Our team has since implemented a fix, and the issue has been resolved. Test Cycle edit view access is now functioning normally for all users.
The cause of this incident was an issue in the frontend deployment that affected the ability to access the Test Cycle edit view. This resulted in the view failing to load correctly, though the underlying data and backend systems were not impacted. We want to reassure customers that **no data was lost** during this incident. All Test Cycle data remained safe and intact throughout. During our investigation, we identified the faulty deployment as the root cause and rolled out a fix to restore normal functionality. Test Cycle edit view access has been confirmed as working. **If you are still experiencing issues**, please clear your browser cache and perform a hard reload of the tab, as cached frontend assets may need to be refreshed. While we are working hard to deliver the best experience to our customers, we apologise for any inconvenience that this might have caused.
Some tenants are facing error due to authorization errors, unable to use Zephyr.
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.
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.
All tenants have been updated, and the system is fully operational again.
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.
Zephyr MCP has been shut down to rollback a previous deployed version.
Zephyr MCP is operational again.
The issue has been identified. It is related to a Jira outage, we're working on a workaround to restore the access to the application.
A workaround has been pushed. We're monitoring the app. Incident will be closed once Jira incident will be solved. https://developer.status.atlassian.com/incidents/rlrntm2fw82b
Jira incident is resolved.