SolarWinds Observability Outage History

SolarWinds Observability is up right now

There were 9 SolarWinds Observability outages since February 4, 2026 totaling 65h 16m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.cloud.solarwinds.com

Notice April 28, 2026

Degraded Web Interface [NA-01]

Detected by Pingoru
Apr 28, 2026, 02:12 PM UTC
Resolved
Apr 28, 2026, 12:30 PM UTC
Duration
Timeline · 1 update
  1. resolved Apr 28, 2026, 02:12 PM UTC

    Between 12:30 PM UTC and 01:41 PM UTC widgets were intermittently broken for all customers on the NA-01 data cell. The web interface issues have been resolved and services have returned to normal operations.

Read the full incident report →

Critical April 28, 2026

Degraded Alert Notifications [NA-01, NA-02, EU-01, AP-01]

Detected by Pingoru
Apr 28, 2026, 07:22 AM UTC
Resolved
Apr 28, 2026, 09:11 AM UTC
Duration
1h 48m
Affected: Alerting
Timeline · 5 updates
  1. investigating Apr 28, 2026, 07:22 AM UTC

    We’ve identified the cause of the email alert notification issue and are actively working on a fix. Some alerts may have been missed, and email notifications remain degraded. We’ll provide our next update in 1 hour.

  2. investigating Apr 28, 2026, 07:23 AM UTC

    We are continuing to investigate this issue.

  3. identified Apr 28, 2026, 07:37 AM UTC

    Alerts may have been missed, and email notifications remain degraded. We’ll provide our next update in 1 hour.

  4. monitoring Apr 28, 2026, 08:43 AM UTC

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

  5. resolved Apr 28, 2026, 09:11 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 26, 2026

Delayed Data Ingestion [NA-01]

Detected by Pingoru
Mar 26, 2026, 10:08 AM UTC
Resolved
Mar 26, 2026, 10:28 AM UTC
Duration
19m
Affected: Logs
Timeline · 3 updates
  1. identified Mar 26, 2026, 10:08 AM UTC

    We’ve identified the cause of the delay in Logs data ingestion for port based destinations and are working on a fix. New data may not appear in the UI, alerts could be delayed, and some dashboards might show missing or outdated values. We’ll provide an update within the hour.

  2. monitoring Mar 26, 2026, 10:19 AM UTC

    A fix for the Logs data ingestion delay for customers using port based destinations has been deployed, and we’re actively monitoring to ensure full recovery. Some new data may still be missing from the UI, alerts may be delayed, and dashboards could reflect outdated information. We’ll share another update within the hour.

  3. resolved Mar 26, 2026, 10:28 AM UTC

    The ingestion delay issue has been resolved. New data is now processing normally, and alerts and dashboards should reflect up-to-date information.

Read the full incident report →

Notice March 23, 2026

Degraded Web Interface [EU-01]

Detected by Pingoru
Mar 23, 2026, 10:14 AM UTC
Resolved
Mar 23, 2026, 10:41 AM UTC
Duration
26m
Timeline · 3 updates
  1. investigating Mar 23, 2026, 10:14 AM UTC

    We’re currently investigating a degradation in the web interface. Some customers may experience intermittent UI errors, or non-loading monitoring data on the home page. We’ll provide another update within the hour.

  2. monitoring Mar 23, 2026, 10:31 AM UTC

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

  3. resolved Mar 23, 2026, 10:41 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 13, 2026

Degraded Data Ingestion [NA-01]

Detected by Pingoru
Mar 13, 2026, 09:04 PM UTC
Resolved
Mar 13, 2026, 10:54 PM UTC
Duration
1h 50m
Affected: AlertingAPMLogsDatabase ObservabilityNetwork ObservabilityKubernetes ObservabilityInfrastructure Observability
Timeline · 3 updates
  1. identified Mar 13, 2026, 09:04 PM UTC

    We’ve identified the root cause of the degraded Logs, Metrics, and Traces data ingestion and are working on a fix. Affected customers may see gaps in the telemetry data and experience missing alerts. Next update in 1 hour.

  2. identified Mar 13, 2026, 10:02 PM UTC

    We’ve identified the root cause of the degraded Logs, Metrics, and Traces data ingestion and are working on a fix. Affected customers may see gaps in the telemetry data and experience missing alerts. Next update in 1 hour.

  3. resolved Mar 13, 2026, 10:54 PM UTC

    The data ingestion issue has been resolved and systems are stable. Customers using Node.js APM instrumentation libraries may need to restart these applications to see metrics and trace data.

Read the full incident report →

Minor March 9, 2026

Degraded Digital Experience Monitoring [Washington DC AWS]

Detected by Pingoru
Mar 09, 2026, 07:43 PM UTC
Resolved
Mar 09, 2026, 08:04 PM UTC
Duration
20m
Affected: DEM
Timeline · 3 updates
  1. identified Mar 09, 2026, 07:43 PM UTC

    We’ve identified the issue causing degraded Digital Experience Monitoring and are implementing a fix. Customers may experience degradation of synthetic checks & alerts from the affected regions. We’ll provide another update in 1 hour.

  2. monitoring Mar 09, 2026, 07:52 PM UTC

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

  3. resolved Mar 09, 2026, 08:04 PM UTC

    The Digital Experience Monitoring issue has been resolved. Affected probes are now stable and running synthetic checks as expected. Missed synthetic checks during the affected window will not be re-run and may show as missing in the dashboards.

Read the full incident report →

Critical March 3, 2026

Degraded Digital Experience Monitoring [Middle East]

Detected by Pingoru
Mar 03, 2026, 04:27 PM UTC
Resolved
Mar 06, 2026, 12:00 AM UTC
Duration
2d 7h
Affected: AlertingDEM
Timeline · 10 updates
  1. investigating Mar 02, 2026, 08:22 AM UTC

    We’re currently investigating an issue affecting Digital Experience Monitoring. Customers may experience degradation of synthetic checks & alerts from the affected regions. We’ll share another update within the hour.

  2. investigating Mar 02, 2026, 09:07 AM UTC

    Due to the on going conflict in the Middle East, our probes in this region are currently unavailable. Customers may experience degradation of synthetic checks & alerts from the affected regions. To mitigate any impact to tests, customer should pick an alternate region to execute tests from. We'll share another update within in the next 4 hours or sooner.

  3. identified Mar 02, 2026, 01:03 PM UTC

    We are continuously monitoring the situation, however our probes in this region remain unavailable at this time. To mitigate any impact to tests, customer should pick an alternate region to execute tests from. We'll share another update within in the next 4 hours or sooner.

  4. identified Mar 02, 2026, 04:59 PM UTC

    We are continuously monitoring the situation, however our probes in this region remain unavailable at this time. To mitigate any impact to tests, customer should pick an alternate region to execute tests from. We'll share another update within in the next 12 hours or sooner.

  5. identified Mar 03, 2026, 04:43 AM UTC

    We are continuously monitoring the situation, however our probes in this region remain unavailable at this time. To mitigate any impact to tests, customer should pick an alternate region to execute tests from. We'll share another update within in the next 12 hours or sooner.

  6. identified Mar 03, 2026, 04:27 PM UTC

    We are continuously monitoring the situation, however our probes in this region remain unavailable at this time. To mitigate any impact to tests, customers should pick an alternate region to execute tests from. We will share another update within in the next 24 hours or sooner.

  7. identified Mar 04, 2026, 04:49 PM UTC

    We are continuously monitoring the situation, however our probes in this region remain unavailable at this time. To mitigate any impact to tests, customers should pick an alternate region to execute tests from. We will share another update within in the next 24 hours or sooner.

  8. identified Mar 05, 2026, 07:19 PM UTC

    We are continuously monitoring the situation, however our probes in this region remain unavailable at this time. To mitigate any impact to tests, customers should pick an alternate region to execute tests from. We will share another update within in the next 24 hours or sooner.

  9. identified Mar 05, 2026, 11:48 PM UTC

    Due to a regional infrastructure disruption impacting an AWS datacenter in the Middle East -https://health.aws.amazon.com/health/status, the Dubai DEM probes will continue to be unavailable. As a result, Synthetic checks configured to run from this location may not execute as expected. While AWS continues recovery efforts, we recommend customers using this location temporarily update the configuration of their monitoring checks to run from an alternative testing location. Recommended action If you have checks configured to run from the Middle East/United Arab Emirates/Dubai, please update the configuration to use another available location to ensure uninterrupted monitoring. Steps: 1. Navigate to SolarWinds Observability → Digital Experience. 2. Open the affected check configuration. 3. Update the test location from Middle East/United Arab Emirates/Dubai to another available region. 4. Save the updated configuration. This change will help ensure continued test execution while the affected infrastructure is restored. Our teams are monitoring the situation closely and will provide updates as the impacted location becomes available again. If you need assistance identifying affected checks or selecting alternative monitoring locations, please contact SolarWinds Support and our team will be happy to help. Thank you for understanding.

  10. resolved Mar 06, 2026, 12:00 AM UTC

    We will continue to share progress and any new developments via email and in-app messaging.

Read the full incident report →

Critical March 3, 2026

Degraded Data Ingestion NA-01

Detected by Pingoru
Mar 03, 2026, 12:38 AM UTC
Resolved
Mar 03, 2026, 04:35 AM UTC
Duration
3h 57m
Affected: AlertingAPMDEMRUMLogsInfrastructure Observability
Timeline · 5 updates
  1. investigating Mar 03, 2026, 12:38 AM UTC

    We’re currently investigating delay in Logs Metrics and Traces data ingestion. As a result, New data may not appear in the UI, alerts may be delayed, and some dashboards could show missing or outdated values. We’ll provide another update within the hour.

  2. identified Mar 03, 2026, 01:02 AM UTC

    We’ve identified the root cause of the degraded Logs, Metrics and Traces data ingestion and are working on a fix. Affected customers may see gaps in the telemetry data and experience missing alerts. Next update in 1 hour.

  3. identified Mar 03, 2026, 01:55 AM UTC

    We’ve identified the root cause of the degraded Logs, Metrics and Traces data ingestion and are working on a fix. Affected customers may see gaps in the telemetry data and experience missing alerts. Next update in 1 hour.

  4. identified Mar 03, 2026, 02:52 AM UTC

    We’ve identified the root cause of the degraded Heroku metrics data ingestion and are working on a fix. Affected customers may see gaps in the telemetry data and experience missing alerts. All other services for Logs, Metrics and Traces are operating normally. Next update in 1 hour.

  5. resolved Mar 03, 2026, 04:35 AM UTC

    The data ingestion issue has been resolved and systems are stable.

Read the full incident report →

Minor February 4, 2026

Degraded Log Archives [NA-01]

Detected by Pingoru
Feb 04, 2026, 11:14 PM UTC
Resolved
Feb 05, 2026, 12:14 AM UTC
Duration
1h
Affected: Logs
Timeline · 2 updates
  1. investigating Feb 04, 2026, 11:14 PM UTC

    We are currently investigating an issue with log archives. As a result of this issue, log archiving will be delayed. We’ll provide an update within the hour.

  2. resolved Feb 05, 2026, 12:14 AM UTC

    The incident has been resolved. Log archives from February 4, 2026 01:00 to 21:00 UTC should now exist, 00:00 will be created later.

Read the full incident report →

Looking to track SolarWinds Observability downtime and outages?

Pingoru polls SolarWinds Observability's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when SolarWinds Observability reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track SolarWinds Observability alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring SolarWinds Observability for free

5 free monitors · No credit card required