SolarWinds Observability Outage History

SolarWinds Observability is up right now

SolarWinds Observability had 32 outages in the last 2 years totaling 116h 11m of downtime — averaging 1.3 incidents per month.

There were 32 SolarWinds Observability outages since March 18, 2025 totaling 116h 11m of downtime. Each is summarised below — incident details, duration, and resolution information.

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

Minor June 29, 2026

Degraded Web Interface NA-01

Detected by Pingoru
Jun 29, 2026, 11:11 AM UTC
Resolved
Jun 29, 2026, 12:13 PM UTC
Duration
1h 2m
Affected: Network Observability
Timeline · 4 updates
  1. investigating Jun 29, 2026, 11:11 AM UTC

    We’re currently investigating degraded performance in the web interface. Some customers may experience intermittent UI errors, or missing monitoring data on the home page. We’ll provide another update within the hour.

  2. identified Jun 29, 2026, 11:41 AM UTC

    We’ve identified the cause of the web interface degradation and are working on a fix. Intermittent UI errors, and missing monitoring data may still affect some customers. Next update in 1 hour.

  3. monitoring Jun 29, 2026, 12:03 PM UTC

    A fix has been implemented for the web interface issues, and we’re actively monitoring to ensure full recovery. Some customers may still experience intermittent UI or dashboard issues as systems stabilize. We’ll provide an update within the hour.

  4. resolved Jun 29, 2026, 12:13 PM UTC

    The web interface issues have been resolved and services have returned to normal operations.

Read the full incident report →

Major June 27, 2026

Degraded data ingestion: [logs3.papertrailapp.com]

Detected by Pingoru
Jun 27, 2026, 12:18 AM UTC
Resolved
Jun 27, 2026, 01:03 AM UTC
Duration
45m
Affected: Logs
Timeline · 3 updates
  1. investigating Jun 27, 2026, 12:32 AM UTC

    We are currently investigating this issue.

  2. monitoring Jun 27, 2026, 12:52 AM UTC

    A fix has been implemented for the Logs data ingestion issue. We’re actively monitoring system stability and verifying end-to-end delivery across impacted systems. We’ll provide an update within the hour.

  3. resolved Jun 27, 2026, 01:03 AM UTC

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

Read the full incident report →

Minor June 16, 2026

Delayed Data Ingestion [ AP-01 ]

Detected by Pingoru
Jun 16, 2026, 07:52 AM UTC
Resolved
Jun 16, 2026, 11:03 AM UTC
Duration
3h 10m
Affected: AlertingAPM
Timeline · 4 updates
  1. investigating Jun 16, 2026, 07:52 AM UTC

    We are currently investigating an issue with Metrics data ingestion. As a result of this issue, submitting new data through the API might fail temporarily. We’ll provide an update within the hour.

  2. investigating Jun 16, 2026, 09:20 AM UTC

    We are still investigating this issue.

  3. monitoring Jun 16, 2026, 10:30 AM UTC

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

  4. resolved Jun 16, 2026, 11:03 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 12, 2026

Temporarily unavailable web UI in NA-02

Detected by Pingoru
Jun 12, 2026, 12:42 AM UTC
Resolved
Jun 12, 2026, 12:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 12, 2026, 12:42 AM UTC

    There was a short window when the web UI was unavailable. Based on reports from external tests this was due to Azure stability issues and unrelated to SolarWinds services.

Read the full incident report →

Minor June 6, 2026

Delayed Data Ingestion [NA-01]

Detected by Pingoru
Jun 06, 2026, 01:51 AM UTC
Resolved
Jun 06, 2026, 03:04 AM UTC
Duration
1h 13m
Affected: Logs
Timeline · 3 updates
  1. identified Jun 06, 2026, 01:51 AM UTC

    We’ve identified the cause of the delay in Logs data ingestion 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 Jun 06, 2026, 02:31 AM UTC

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

  3. resolved Jun 06, 2026, 03:04 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 4, 2026

Delayed Alert Notifications [NA-01]

Detected by Pingoru
Jun 04, 2026, 01:25 PM UTC
Resolved
Jun 04, 2026, 02:01 PM UTC
Duration
36m
Affected: Alerting
Timeline · 3 updates
  1. identified Jun 04, 2026, 01:25 PM UTC

    Starting at 12:33 UTC we noticed higher than normal latency with alerts, resulting in alert delivery being delayed. We've identified the issue causing delays in alert delivery and are working on a fix. Some alerts may still be delayed in the meantime. Next update in 1 hour.

  2. monitoring Jun 04, 2026, 01:33 PM UTC

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

  3. resolved Jun 04, 2026, 02:01 PM UTC

    The issue impacting alert notifications has been resolved. Alerts are now being sent as expected. Some customers may have delayed delivery of any alerts that would have been triggered during the incident window.

Read the full incident report →

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 →

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 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 →

Notice January 9, 2026

Delayed Data Ingestion [EU-01]

Detected by Pingoru
Jan 09, 2026, 06:00 AM UTC
Resolved
Jan 09, 2026, 04:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jan 09, 2026, 06:00 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 →

Minor December 2, 2025

Degraded Webhook notifications [NA-01, NA-02, EU-01, AP-01]

Detected by Pingoru
Dec 02, 2025, 01:07 PM UTC
Resolved
Dec 02, 2025, 01:42 PM UTC
Duration
35m
Affected: Alerting
Timeline · 4 updates
  1. investigating Dec 02, 2025, 01:07 PM UTC

    We have identified an issue where webhook notifications from the SolarWinds Observability SaaS may contain malformed JSON in notification body. This could impact processing by any third party integrations via webhooks and using default templates. Notifications using custom templates are not affected. Our team is actively working on a resolution and will provide updates as soon as possible.

  2. monitoring Dec 02, 2025, 01:25 PM UTC

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

  3. monitoring Dec 02, 2025, 01:26 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Dec 02, 2025, 01:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 18, 2025

Delayed Data Ingestion [NA-01, EU-01]

Detected by Pingoru
Nov 18, 2025, 03:57 PM UTC
Resolved
Nov 18, 2025, 06:22 PM UTC
Duration
2h 25m
Affected: AlertingLogs
Timeline · 5 updates
  1. investigating Nov 18, 2025, 03:57 PM UTC

    We’re currently investigating delay in Logs 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 Nov 18, 2025, 05:02 PM UTC

    We’ve identified the cause of the delay in Logs data ingestion 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.

  3. identified Nov 18, 2025, 06:04 PM UTC

    We’ve identified the cause of the delay in Logs data ingestion 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.

  4. monitoring Nov 18, 2025, 06:15 PM UTC

    A fix for the Logs data ingestion delay 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.

  5. resolved Nov 18, 2025, 06:22 PM 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 →

Major November 18, 2025

Degraded Performance [NA-01, NA-02, EU-01, AP-01]

Detected by Pingoru
Nov 18, 2025, 11:50 AM UTC
Resolved
Nov 18, 2025, 03:54 PM UTC
Duration
4h 3m
Affected: LoginAlertingAPMDEMRUMLogsDatabase ObservabilityNetwork ObservabilityKubernetes ObservabilityInfrastructure ObservabilityAgent Downloads and UpdatesAIOps Service
Timeline · 7 updates
  1. investigating Nov 18, 2025, 11:50 AM UTC

    We’re currently investigating degraded performance in the web interface. Some customers may experience intermittent failures accessing the web interface. We’ll provide another update within the hour.

  2. investigating Nov 18, 2025, 12:09 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Nov 18, 2025, 12:24 PM UTC

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

  4. investigating Nov 18, 2025, 12:54 PM UTC

    We’re currently observing intermittent degradation in performance of the web interface and issue with delayed ingestion of logs. We’ll provide another update within the hour.

  5. investigating Nov 18, 2025, 01:53 PM UTC

    We are continuing to investigate this issue.

  6. identified Nov 18, 2025, 02:52 PM UTC

    Web Interface is accessible now. We’ve identified the cause of the delay in Logs data ingestion 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.

  7. resolved Nov 18, 2025, 03:54 PM UTC

    The web interface issues have been resolved and services have returned to normal operations.

Read the full incident report →

Minor October 31, 2025

Degraded Data Ingestion [NA-01 and EU-01]

Detected by Pingoru
Oct 31, 2025, 02:26 AM UTC
Resolved
Oct 31, 2025, 03:56 AM UTC
Duration
1h 29m
Affected: AlertingLogs
Timeline · 5 updates
  1. investigating Oct 31, 2025, 02:26 AM UTC

    We are currently investigating an issue with [Logs] data ingestion. As a result of this issue, submitting new data through the API might fail temporarily. We’ll provide an update within the hour.

  2. investigating Oct 31, 2025, 02:46 AM UTC

    We are continuing to investigate this issue.

  3. identified Oct 31, 2025, 03:03 AM UTC

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

  4. monitoring Oct 31, 2025, 03:50 AM UTC

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

  5. resolved Oct 31, 2025, 03:56 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 15, 2025

Delayed Data Ingestion EU-01

Detected by Pingoru
Sep 15, 2025, 01:14 AM UTC
Resolved
Sep 15, 2025, 02:02 AM UTC
Duration
47m
Affected: Logs
Timeline · 3 updates
  1. investigating Sep 15, 2025, 01:14 AM UTC

    We’re currently investigating delay in Logs 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. monitoring Sep 15, 2025, 01:50 AM UTC

    A fix for the Logs data ingestion delay 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 Sep 15, 2025, 02:02 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 5, 2025

Delayed Data Ingestion NA-01

Detected by Pingoru
Sep 05, 2025, 11:31 PM UTC
Resolved
Sep 05, 2025, 11:50 PM UTC
Duration
19m
Affected: APM
Timeline · 4 updates
  1. investigating Sep 05, 2025, 11:31 PM UTC

    We’re currently investigating delay in 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 Sep 05, 2025, 11:42 PM UTC

    We’ve identified the cause of the delay in Traces data ingestion 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.

  3. monitoring Sep 05, 2025, 11:46 PM UTC

    A fix for the Traces data ingestion delay 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.

  4. resolved Sep 05, 2025, 11:50 PM 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 →

Minor August 22, 2025

Delayed Data Ingestion [Na-01]

Detected by Pingoru
Aug 22, 2025, 05:02 AM UTC
Resolved
Aug 22, 2025, 07:56 AM UTC
Duration
2h 54m
Affected: APM
Timeline · 5 updates
  1. investigating Aug 22, 2025, 05:02 AM UTC

    We’ve identified the cause of the delay in traces and metrics data ingestion 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. investigating Aug 22, 2025, 05:56 AM UTC

    we are continuing to investigate this issue.

  3. investigating Aug 22, 2025, 07:07 AM UTC

    We’re currently investigating delay in 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.

  4. monitoring Aug 22, 2025, 07:48 AM UTC

    A fix for the Metrics and Traces data ingestion delay 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.

  5. resolved Aug 22, 2025, 07:56 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 →

Minor July 21, 2025

Degraded Data Ingestion [NA-02]

Detected by Pingoru
Jul 21, 2025, 11:48 PM UTC
Resolved
Jul 22, 2025, 02:34 AM UTC
Duration
2h 45m
Affected: APMLogs
Timeline · 5 updates
  1. investigating Jul 21, 2025, 11:48 PM UTC

    We are currently investigating an issue with Logs/Metrics/Traces data ingestion. As a result of this issue, submitting new data through the API might fail temporarily. We’ll provide an update within the hour.

  2. investigating Jul 22, 2025, 12:44 AM UTC

    We are currently investigating an issue with Logs/Metrics/Traces data ingestion. As a result of this issue, submitting new data through the API might fail temporarily. We’ll provide an update within the hour.

  3. investigating Jul 22, 2025, 01:44 AM UTC

    We are currently investigating an issue with Logs/Metrics/Traces data ingestion. As a result of this issue, submitting new data through the API might fail temporarily. We’ll provide an update within the hour.

  4. monitoring Jul 22, 2025, 02:20 AM UTC

    A fix has been implemented for the Logs/Metrics/Traces data ingestion issue. We’re actively monitoring system stability and verifying end-to-end delivery across impacted systems. We’ll provide an update within the hour.

  5. resolved Jul 22, 2025, 02:34 AM UTC

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

Read the full incident report →

Notice July 8, 2025

Degraded Data Ingestion for Database Observability Instrumentation for PostgreSQL [NA-01]

Detected by Pingoru
Jul 08, 2025, 03:01 PM UTC
Resolved
May 22, 2025, 07:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jul 08, 2025, 03:01 PM UTC

    Between May 22nd and May 27th, we identified an issue affecting Database Observability instrumentation for PostgreSQL databases, which resulted in telemetry events not being captured. As a result, affected customers may notice gaps in their observability data during this period.

Read the full incident report →