Is Zephyr Scale down?

Last checked 8m ago
Current status
Zephyr Scale is up

No incidents right now.

Official status page: https://zephyr-scale.status.smartbear.com · Polled every 5 minutes · 35 components tracked

Zephyr Scale is operational right now. Last checked 8m ago; the most recent incident resolved 24d ago.

Real-time Zephyr Scale status, recent outages, and incident history — pulled directly from Zephyr Scale's official status page at https://zephyr-scale.status.smartbear.com every 5 minutes. Pingoru tracks 35 Zephyr Scale services and has captured 3 incidents in the last 90 days (99.60% uptime). Get email, Slack, Discord, or webhook alerts the moment Zephyr Scale reports a new incident — free for 5 monitors, no credit card.

Users who monitor Zephyr Scale also follow these DevOps services: GitHub Confluence Circle CI OpsGenie JFrog Papertrail Airbrake Splunk OnCall Datadog EU RubyGems View all 6,000+ providers
Zephyr Scale uptime 99.60% uptime · past 90 days
Mon Wed Fri
MayJunJul
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 4h 52m
    Started Jul 07, 2026, 09:00 AM UTC · Resolved Jul 07, 2026, 01:53 PM UTC
    Zephyr Cloud (US)Zephyr Cloud (EU)
    Timeline · 3 updates
    • identified · Jul 07, 2026, 02:07 PM UTC

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

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

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

    Latest: 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…

  2. Resolved 7h 30m
    Started Jun 10, 2026, 04:30 AM UTC · Resolved Jun 10, 2026, 12:00 PM UTC
    Zephyr Cloud (US)Zephyr Cloud REST API (US)Zephyr Cloud (EU)Zephyr Cloud REST API (EU)Zephyr Remote MCP
    Timeline · 5 updates
    • 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.

    Latest: 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://…

  3. Resolved 1h 18m
    Started Jun 08, 2026, 09:56 AM UTC · Resolved Jun 08, 2026, 11:15 AM UTC
    Zephyr Remote MCP
    Timeline · 2 updates
    • investigating · Jun 08, 2026, 01:47 PM UTC

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

    • resolved · Jun 08, 2026, 01:48 PM UTC

      Zephyr MCP is operational again.

    Latest: Zephyr MCP is operational again.

Outage history

Past 90 days · 3 incidents View full outage history →