Zephyr Scale Outage History

Zephyr Scale is up right now

Pingoru has recorded 29 incidents for Zephyr Scale: 6 in the last 12 months and 1 in the last 90 days.

Source: zephyr-scale.status.smartbear.com

29incidents recorded
6last 12 months
1last 90 days
5 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Zephyr Scale in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202629 of 720 (1%)
July 202615 of 744 (1%)
August 202600 of 744 (0%)
September 2026112 of 720 (2%)
October 202600 of 509 (0%)

Incidents, newest first

Notice September 8, 2026 Frontend downtime 12h 15m

Started Sep 08, 2026, 11:30 PM UTC· resolved Sep 09, 2026, 11:45 AM UTC

  1. resolved Sep 09, 2026, 02:15 PM UTC

    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

Read the full incident report →

Major July 7, 2026 Issue accessing the Test Cycle edit view 4h 52m Zephyr Cloud (US), Zephyr Cloud (EU)

Started Jul 07, 2026, 09:00 AM UTC· resolved Jul 07, 2026, 01:53 PM UTC

  1. identified Jul 07, 2026, 02:07 PM UTC

    We identified an issue when trying to open the Test Cycle edit view.

  2. resolved Jul 07, 2026, 02:10 PM UTC

    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.

  3. postmortem Jul 07, 2026, 02:24 PM UTC

    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.

Read the full incident report →

Major June 10, 2026 Authorization error with Atlassian 7h 30m Zephyr Cloud (US), Zephyr Cloud REST API (US), Zephyr Cloud (EU), Zephyr Cloud REST API (EU) and 1 more

Started Jun 10, 2026, 04:30 AM UTC· resolved Jun 10, 2026, 12:00 PM UTC

  1. investigating Jun 10, 2026, 03:16 PM UTC

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

  2. 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.

  3. 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.

  4. resolved Jun 10, 2026, 03:21 PM UTC

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

  5. 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.

Read the full incident report →

Critical June 8, 2026 Zephyr MCP is down 1h 18m Zephyr Remote MCP

Started Jun 08, 2026, 09:56 AM UTC· resolved Jun 08, 2026, 11:15 AM UTC

  1. investigating Jun 08, 2026, 01:47 PM UTC

    Zephyr MCP has been shut down to rollback a previous deployed version.

  2. resolved Jun 08, 2026, 01:48 PM UTC

    Zephyr MCP is operational again.

Read the full incident report →

Critical February 6, 2026 Zephyr is not accessible 5h 19m Zephyr Cloud (US), Zephyr Cloud REST API (US), Zephyr Cloud (EU), Zephyr Cloud REST API (EU)

Started Feb 06, 2026, 09:33 AM UTC· resolved Feb 06, 2026, 02:53 PM UTC

  1. identified Feb 06, 2026, 09:33 AM UTC

    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.

  2. monitoring Feb 06, 2026, 10:24 AM UTC

    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

  3. resolved Feb 06, 2026, 02:53 PM UTC

    Jira incident is resolved.

Read the full incident report →

Notice July 17, 2025 API calls time out –

Started Jul 17, 2025, 05:00 AM UTC· resolved Jul 17, 2025, 05:00 AM UTC

  1. resolved Jul 18, 2025, 08:02 AM UTC

    Impact: Various API calls were timing out. Resolution: Our engineering team has identified the bottleneck API endpoint that was impacting other endpoints as well. The fix was deployed.

Read the full incident report →

Minor July 15, 2025 We are experiencing degraded performance of the Zephyr API module. 2h 56m Zephyr Cloud REST API (US)

Started Jul 15, 2025, 07:05 AM UTC· resolved Jul 15, 2025, 10:01 AM UTC

  1. investigating Jul 15, 2025, 07:05 AM UTC

    Impact: API calls may be slower than usual or occasionally time out. Current status Our engineering team has identified the bottleneck in the API tier and is deploying optimisations now. Logs and metrics are under close review. Next update: We will update this message as soon as further information is available.

  2. resolved Jul 15, 2025, 10:01 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 31, 2025 Some styling might be missing in some regions 2h 4m Zephyr Cloud (US), Zephyr Cloud REST API (US)

Started Mar 31, 2025, 11:11 AM UTC· resolved Mar 31, 2025, 01:16 PM UTC

  1. identified Mar 31, 2025, 11:11 AM UTC

    Zephyr Scale is being impacted by an outage in some regions of unpkg.com. Some Atlassian CSS hosted in this service are not being loaded on the page in some regions, causing parts of the application to not render properly. Although this doesn't impact the operation of the app, users might notice degraded user experience.

  2. resolved Mar 31, 2025, 01:16 PM UTC

    unpkg.com is operational again and all issues have been resolved.

Read the full incident report →

Notice February 21, 2025 Zephyr Scale Intermittent Issues 2h 19m

Started Feb 21, 2025, 04:30 PM UTC· resolved Feb 21, 2025, 06:50 PM UTC

  1. resolved Feb 21, 2025, 04:30 PM UTC

    Hi All, We want to make you aware that Zephyr Scale application faced intermittent issues from 1:50 pm UTC to 2:24 pm UTC. The problem has been identified, and we are now seeing stability with no further issues reported. We will continue to monitor the situation and apologize for any inconvenience caused.

Read the full incident report →

Minor October 22, 2024 Test automation is broken 1h Zephyr Cloud (US), Zephyr Cloud REST API (US), Zephyr Support Site

Started Oct 22, 2024, 08:11 AM UTC· resolved Oct 22, 2024, 09:11 AM UTC

  1. investigating Oct 22, 2024, 08:11 AM UTC

    We are currently providing a fix

  2. identified Oct 22, 2024, 08:11 AM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Oct 22, 2024, 09:11 AM UTC

    Incident is resolved

Read the full incident report →