Zephyr Scale Outage History

Zephyr Scale had 3 outages in the last 2 years totaling 8h 15m of downtime — averaging 0.1 incidents per month.

There were 3 Zephyr Scale outages since July 15, 2025 totaling 8h 15m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://zephyr-scale.status.smartbear.com

Critical February 6, 2026

Zephyr is not accessible

Detected by Pingoru: Feb 06, 2026, 09:33 AM UTC
Resolved: Feb 06, 2026, 02:53 PM UTC
Duration: 5h 19m

Affected: Zephyr Cloud (US)Zephyr Cloud REST API(US)Zephyr Cloud (EU)Zephyr Cloud REST API(EU)

Timeline · 3 updates

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.
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
resolved Feb 06, 2026, 02:53 PM UTC

Jira incident is resolved.

Read the full incident report →

Notice July 18, 2025

API calls time out

Detected by Pingoru: Jul 18, 2025, 08:02 AM UTC
Resolved: Jul 17, 2025, 05:00 AM UTC
Duration: —

Timeline · 1 update

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.

Detected by Pingoru: Jul 15, 2025, 07:05 AM UTC
Resolved: Jul 15, 2025, 10:01 AM UTC
Duration: 2h 56m

Affected: Zephyr Cloud REST API(US)

Timeline · 2 updates

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.
resolved Jul 15, 2025, 10:01 AM UTC

This incident has been resolved.

Read the full incident report →