SolarWinds Observability Outage History

SolarWinds Observability is up right now

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

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

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

Minor May 19, 2025

Delayed Ingestion [NA-01]

Detected by Pingoru
May 19, 2025, 11:58 PM UTC
Resolved
May 20, 2025, 01:05 AM UTC
Duration
1h 7m
Affected: AlertingLogs
Timeline · 4 updates
  1. investigating May 19, 2025, 11:58 PM UTC

    We are investigating

  2. identified May 20, 2025, 12:18 AM UTC

    We've identified the cause of the delay in data ingestion and are working on a fix. New log data may not appear in the UI, log alerts could be delayed, and some dashboards might show missing or outdated values. This is impacting all customers sending logs. We'll provide an update within the hour.

  3. monitoring May 20, 2025, 12:55 AM UTC

    A fix for the ingestion delays has been deployed, and we're actively monitoring to ensure full recovery. Some new log data may still be missing from the UI, log alerts may be delayed, and dashboards could reflect outdated information. This is impacting all customers sending logs. We'll share another update within the hour.

  4. resolved May 20, 2025, 01:05 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. This incident impacted all customers sending logs but systems are now fully recovered.

Read the full incident report →

Minor May 7, 2025

Degraded Web Interface [NA-02, EU-01, AP-01]

Detected by Pingoru
May 07, 2025, 12:42 AM UTC
Resolved
May 07, 2025, 05:20 AM UTC
Duration
4h 37m
Affected: AlertingAPMDEMRUMLogsDatabase ObservabilityNetwork ObservabilityKubernetes ObservabilityInfrastructure Observability
Timeline · 5 updates
  1. investigating May 06, 2025, 07:45 PM UTC

    We are investigating

  2. identified May 07, 2025, 12:42 AM UTC

    The issue has been identified and a fix is being implemented. Next update in 3 hours.

  3. identified May 07, 2025, 02:11 AM UTC

    We are continuing to work on fixing the issue. The next update will be provided in 3 hours.

  4. monitoring May 07, 2025, 05:13 AM UTC

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

  5. resolved May 07, 2025, 05:20 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 16, 2025

Degraded Ingestion [NA-01]

Detected by Pingoru
Apr 16, 2025, 11:29 PM UTC
Resolved
Apr 16, 2025, 11:44 PM UTC
Duration
15m
Affected: AlertingAPMDEMRUMLogsDatabase ObservabilityNetwork ObservabilityKubernetes ObservabilityInfrastructure Observability
Timeline · 3 updates
  1. investigating Apr 16, 2025, 11:29 PM UTC

    We are investigating

  2. identified Apr 16, 2025, 11:31 PM UTC

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

  3. resolved Apr 16, 2025, 11:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 15, 2025

Delayed Metrics Ingestion [NA-01]

Detected by Pingoru
Apr 15, 2025, 07:51 AM UTC
Resolved
Apr 15, 2025, 09:41 AM UTC
Duration
1h 50m
Affected: AlertingAPMDEMRUMDatabase ObservabilityNetwork ObservabilityKubernetes ObservabilityInfrastructure Observability
Timeline · 5 updates
  1. investigating Apr 15, 2025, 07:51 AM UTC

    We are currently investigating this issue.

  2. investigating Apr 15, 2025, 08:39 AM UTC

    We are continuing to investigate this issue.

  3. identified Apr 15, 2025, 09:13 AM UTC

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

  4. monitoring Apr 15, 2025, 09:27 AM UTC

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

  5. resolved Apr 15, 2025, 09:41 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 10, 2025

Degraded Logs Alerting [NA-01, EU-01]

Detected by Pingoru
Apr 10, 2025, 03:58 PM UTC
Resolved
Apr 09, 2025, 06:30 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Apr 10, 2025, 03:58 PM UTC

    Between April 9, 08:30 AM (UTC) and April 10:06 AM (UTC), some customers experienced an elevated volume of false log-based alerts. We apologize for any disruption this may have caused, and we are implementing safeguards to prevent similar issues in the future.

Read the full incident report →

Minor March 18, 2025

Delayed Ingestion [NA-01, EU-01]

Detected by Pingoru
Mar 18, 2025, 09:33 PM UTC
Resolved
Mar 18, 2025, 11:15 PM UTC
Duration
1h 42m
Affected: AlertingLogs
Timeline · 3 updates
  1. investigating Mar 18, 2025, 09:33 PM UTC

    We are investigating

  2. identified Mar 18, 2025, 10:38 PM UTC

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

  3. resolved Mar 18, 2025, 11:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 18, 2025

Delayed Ingestion [NA-02]

Detected by Pingoru
Mar 18, 2025, 02:25 PM UTC
Resolved
Mar 18, 2025, 05:13 PM UTC
Duration
2h 48m
Affected: AlertingAPMDEMRUMLogsDatabase ObservabilityNetwork ObservabilityKubernetes ObservabilityInfrastructure ObservabilityAIOps Service
Timeline · 5 updates
  1. investigating Mar 18, 2025, 02:25 PM UTC

    We are investigating

  2. investigating Mar 18, 2025, 03:21 PM UTC

    We are continuing to investigate this issue.

  3. investigating Mar 18, 2025, 04:17 PM UTC

    We are continuing to investigate this issue.

  4. identified Mar 18, 2025, 05:01 PM UTC

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

  5. resolved Mar 18, 2025, 05:13 PM UTC

    This incident has been resolved.

Read the full incident report →