Authorization error with Atlassian

Incident Report for Zephyr Cloud

Postmortem

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

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.

Posted Jun 10, 2026 - 15:25 UTC

Resolved

All tenants have been updated, and the system is fully operational again.

Posted Jun 10, 2026 - 12:00 UTC

Monitoring

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.

Posted Jun 10, 2026 - 06:15 UTC

Identified

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.

Posted Jun 10, 2026 - 04:45 UTC

Investigating

Some tenants are facing error due to authorization errors, unable to use Zephyr.

Posted Jun 10, 2026 - 04:30 UTC

This incident affected: Zephyr Cloud (US), Zephyr Cloud REST API(US), Zephyr Cloud (EU), Zephyr Cloud REST API(EU), and Zephyr Remote MCP.