SmartBear Outage History

SmartBear degraded · 4 active incidents View live status →

SmartBear had 14 outages in the last 2 years totaling 408h 8m of downtime — averaging 0.6 incidents per month.

There were 14 SmartBear outages since April 24, 2026 totaling 408h 8m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.smartbear.com

Critical June 13, 2026

AlertSite: Zurich, Switzerland - Monitoring Location Outage

Detected by Pingoru
Jun 13, 2026, 01:09 PM UTC
Resolved
Jun 15, 2026, 03:14 PM UTC
Duration
2d 2h
Affected: Zurich, Switzerland
Timeline · 1 update
  1. identified Jun 13, 2026, 01:09 PM UTC

    We are experiencing an outage with our monitoring nodes in Zurich, Switzerland since 10AM EST. We are working to resolve this issue as soon as possible. If you wish to create a case with Customer Care, please visit https://support.smartbear.com/message/?prod=Alertsite.

Read the full incident report →

Critical June 12, 2026

Bitbar Testing Cloud: BitBar service unavailability

Detected by Pingoru
Jun 12, 2026, 04:31 AM UTC
Resolved
Jun 12, 2026, 09:49 AM UTC
Duration
5h 18m
Affected: Cloud UIAPI Access
Timeline · 2 updates
  1. identified Jun 12, 2026, 04:31 AM UTC

    We are currently experiencing BitBar service unavailability. Several services are affected, and access to BitBar is limited.

  2. monitoring Jun 12, 2026, 08:05 AM UTC

    A fix has been implemented and we are monitoring the results.

Read the full incident report →

Major June 10, 2026

Zephyr Cloud: Authorization error with Atlassian

Detected by Pingoru
Jun 10, 2026, 04:30 AM UTC
Resolved
Jun 10, 2026, 03:29 PM UTC
Duration
10h 59m
Affected: Zephyr Cloud (US)Zephyr Cloud REST API(US)Zephyr Cloud (EU)Zephyr Cloud REST API(EU)Zephyr Remote MCP
Timeline · 2 updates
  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.

Read the full incident report →

Major June 10, 2026

CucumberStudio: Test run functionality affected

Detected by Pingoru
Jun 10, 2026, 03:19 AM UTC
Resolved
Jun 10, 2026, 04:35 AM UTC
Duration
1h 15m
Affected: CucumberStudio Application
Timeline · 3 updates
  1. investigating Jun 10, 2026, 03:19 AM UTC

    We are currently working on a fix for the issue that has reoccurred affecting the test run functionality. All other functionalities are working as expected. Please reach out to support if you have further queries. Apologies for the inconvenience caused.

  2. identified Jun 10, 2026, 03:20 AM UTC

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

  3. monitoring Jun 10, 2026, 04:13 AM UTC

    A fix has been implemented and we are monitoring the results.

Read the full incident report →

Notice June 9, 2026

CucumberStudio: Test run functionality not working properly

Detected by Pingoru
Jun 09, 2026, 11:22 AM UTC
Resolved
Jun 09, 2026, 03:48 PM UTC
Duration
4h 26m
Affected: CucumberStudio Application
Timeline · 2 updates
  1. investigating Jun 09, 2026, 11:22 AM UTC

    We are currently investigating an issue that has affected the test run functionality. All other functionalities are working as expected. Please reach out to support if you have further queries.

  2. identified Jun 09, 2026, 03:05 PM UTC

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

Read the full incident report →

Critical May 28, 2026

AlertSite: AlertSite UXM Dashboard Unavailability

Detected by Pingoru
May 28, 2026, 10:38 AM UTC
Resolved
May 28, 2026, 05:06 PM UTC
Duration
6h 27m
Affected: UXM DashboardUXM Document ManagerUXM Account Summary
Timeline · 4 updates
  1. investigating May 28, 2026, 10:38 AM UTC

    We are currently experiencing an issue affecting AlertSite UXM dashboard availability. Our team is actively investigating. We will provide updates as the situation progresses

  2. identified May 28, 2026, 12:25 PM UTC

    The issue has been identified and the team is working through recovery efforts.

  3. identified May 28, 2026, 02:00 PM UTC

    Recovery efforts are still proceeding and making good progress. Monitoring and alerting remain operational.

  4. monitoring May 28, 2026, 04:27 PM UTC

    We have fixed the issue and monitoring data is available now. We are continuously monitoring the application. If you wish to create a case with Customer Care, please visit https://support.smartbear.com/message/?prod=Alertsite. We sincerely apologize for the inconvenience and appreciate your patience and understanding while we work to resolve this matter.

Read the full incident report →

Major May 25, 2026

Stoplight: Stoplight Infrastructure Maintenance Window

Detected by Pingoru
May 25, 2026, 04:51 PM UTC
Resolved
May 25, 2026, 05:26 PM UTC
Duration
34m
Affected: Stoplight PlatformElementsAPI Docs (api-docs.io)
Timeline · 1 update
  1. investigating May 25, 2026, 04:51 PM UTC

    We are currently experiencing a outage in the Stoplight production environment. Our team is actively working on a resolution and will provide an update once the issue has been resolved.

Read the full incident report →

Critical May 25, 2026

QMetry: QMetry Outage - US Instance

Detected by Pingoru
May 25, 2026, 08:25 AM UTC
Resolved
May 25, 2026, 12:27 PM UTC
Duration
4h 1m
Affected: QTM APP USQTM REPORT US
Timeline · 4 updates
  1. investigating May 25, 2026, 08:25 AM UTC

    The US QMetry instance is experiencing a system disruption, and we are investigating the issue.

  2. monitoring May 25, 2026, 08:34 AM UTC

    US QMetry is accessible again, we will continue to monitor for any issues.

  3. investigating May 25, 2026, 09:39 AM UTC

    The US QMetry instance is experiencing a system disruption, and we are investigating the issue.

  4. monitoring May 25, 2026, 10:23 AM UTC

    US QMetry is accessible again, we will continue to monitor for any issues.

Read the full incident report →

Critical May 12, 2026

AlertSite: Fort Lauderdale, FL Monitoring Location Outage

Detected by Pingoru
May 12, 2026, 06:25 PM UTC
Resolved
May 12, 2026, 07:44 PM UTC
Duration
1h 19m
Affected: Fort Lauderdale, FL
Timeline · 1 update
  1. identified May 12, 2026, 06:25 PM UTC

    We are experiencing an outage with our monitoring nodes in Fort Lauderdale, FL since 12:30 PM EST. We are working to resolve this issue as soon as possible. If you wish to create a case with Customer Care, please visit https://support.smartbear.com/message/?prod=Alertsite. Monitoring Locations - North America - Las Vegas, NV

Read the full incident report →

Major May 8, 2026

AlertSite: Dashboard Data Availability Issue

Detected by Pingoru
May 08, 2026, 03:09 AM UTC
Resolved
May 11, 2026, 06:31 AM UTC
Duration
3d 3h
Affected: UXM Dashboard
Timeline · 2 updates
  1. investigating May 08, 2026, 03:09 AM UTC

    We are currently experiencing an issue affecting dashboard data availability due to an outage on our end. Our team is actively investigating and working to restore full functionality as quickly as possible. Please note that alerting and monitoring services remain fully operational and are not impacted by this issue. If you wish to create a case with Customer Care, please visit https://support.smartbear.com/message/?prod=Alertsite We sincerely apologize for the inconvenience and appreciate your patience and understanding while we work to resolve this matter.

  2. identified May 08, 2026, 07:43 AM UTC

    Services have been partially restored, and data processing has resumed. We are currently monitoring the system and will provide another update once the issue is fully resolved. If you wish to create a case with Customer Care, please visit https://support.smartbear.com/message/?prod=Alertsite We sincerely apologize for the inconvenience and appreciate your patience and understanding while we work to resolve this matter.

Read the full incident report →

Minor May 7, 2026

AlertSite: Some Monitors Currently Experiencing Failures

Detected by Pingoru
May 07, 2026, 01:31 PM UTC
Resolved
May 07, 2026, 08:09 PM UTC
Duration
6h 38m
Affected: Atlanta, GABuenos Aires, ArgentinaAmsterdam - The NederlandsAtlanta, GA - ATT WirelessSao Paulo, BrazilAtlanta, GA - Sprint 4G MobileBeijing, ChinaAustin, TXBrussels, BelgiumAuckland, New ZealandBoston, MACopenhagen, DenmarkBoston, MA - ExpedientDublin, IrelandCalgary, AlbertaFrankfurt, GermanyChicago, IL - TataHong KongCharlotte, NCKuala Lumpur, MalaysiaChicago, IL - LeaseWebLondon, UK - AboveNetBrisbane, AustraliaCincinnati, OHLondon, UK - DocklandsCleveland, OHMadrid, SpainDallas, TXManchester, UKDallas, TX - LeaseWebMilan, ItalyDenver, COCape Town, South AfricaDetroit, MIMumbai, IndiaFort Lauderdale, FLMunich, GermanyFort Lauderdale, FL - ATT WirelessNew Delhi, IndiaFort Lauderdale, FL - Sprint 3G MobileParis, FranceFremont, CASiauliai, LithuaniaKansas City, KSSeoul, South KoreaLas Vegas, NVShanghai, ChinaLos Angeles, CA - Level3SingaporeLos Angeles, CA - NextLinkStockholm, SwedenHouston, TXTel Aviv, IsraelMemphis, TNTokyo, JapanMinneapolis, MNZurich, SwitzerlandNew York, NY - Peer1New York, NY - MicroHelsinki, FinlandMontreal, QuebecMiami, FLNewark, NJ - NLayerNew York, NY - LeaseWebPhiladelphia, PA - AboveNetPhiladelphia, PA - XOPittsburgh, PAPhoenix, AZPortland, ORSalt Lake City, UTSan Diego, CASan Francisco, CASan Jose, CA - MicroSeattle, WASt. Louis, MOTampa, FLToronto, OntarioVancouver, British ColumbiaWashington, D.C.Worcester, MAPerth, AustraliaSydney, AustraliaSydney, Australia - Equinix
Timeline · 1 update
  1. investigating May 07, 2026, 01:31 PM UTC

    We are currently experiencing an issue that is causing some of the monitors to fail. Our team is actively investigating and working towards a resolution, and the Root Cause Analysis (RCA) is in progress. We sincerely apologize for any inconvenience caused and appreciate your patience as we work to restore normal service at the earliest. If you wish to create a case with Customer Care, please visit https://support.smartbear.com/message/?prod=Alertsite. We appreciate your patience and will provide updates as more information becomes available.

Read the full incident report →

Critical April 30, 2026

AlertSite: Las Vegas, NV - Monitoring Location Outage

Detected by Pingoru
Apr 30, 2026, 06:37 AM UTC
Resolved
May 07, 2026, 03:58 AM UTC
Duration
6d 21h
Affected: Las Vegas, NV
Timeline · 2 updates
  1. investigating Apr 30, 2026, 06:37 AM UTC

    We are experiencing an outage with our monitoring nodes in Las Vegas, NV. We are working to resolve this issue as soon as possible. If you wish to create a case with Customer Care, please visit https://support.smartbear.com/message/?prod=Alertsite.

  2. investigating May 06, 2026, 09:57 AM UTC

    We are currently experiencing degraded performance with our monitoring nodes in Las Vegas, NV. Our team is actively investigating the issue and working to restore full service as quickly as possible. Some monitoring checks may be delayed or intermittently impacted during this time. If you wish to create a case with Customer Care, please visit https://support.smartbear.com/message/?prod=Alertsite. We appreciate your patience and will provide updates as more information becomes available.

Read the full incident report →

Major April 24, 2026

AlertSite: Network Fluctuation at Minneapolis, MN

Detected by Pingoru
Apr 24, 2026, 10:30 AM UTC
Resolved
Apr 24, 2026, 04:43 PM UTC
Duration
6h 12m
Affected: Minneapolis, MN
Timeline · 2 updates
  1. investigating Apr 24, 2026, 10:30 AM UTC

    Dear Customer, We are currently experiencing network fluctuations at one of our servers in Minneapolis, MN. As a result, some customer monitors are being skipped or are not receiving the required profiles to run, and overall network traffic has increased. Our team is actively working to resolve the issue as quickly as possible. We sincerely appreciate your understanding and patience during this time. We will keep you updated with any significant developments.

  2. monitoring Apr 24, 2026, 12:26 PM UTC

    The issue has been resolved, and we are currently monitoring the situation.

Read the full incident report →