SolarWinds Observability Outage History

We’ve identified the cause of the delay in Logs, Metrics and 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.

The ingestion delay has fully recovered, and the latest data should now be visible in the UI. Alerting has also returned to real-time processing. There will be data gaps in the UI between 9:40 UTC and 14:40 UTC while we complete the backfill. We are actively replaying the missing data, and the backfill is expected to take approximately 24–48 hours to complete. Next update within 8 hours.

The backfill is making progess, however, some customers may still see data gaps in the UI between 9:40 UTC and 14:40 UTC while it completes. We are still actively replaying the missing data, and the backfill is expected to take approximately an hour to complete. Next update within 1 hour.

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

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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