SolarWinds Observability Outage History

SolarWinds Observability experienced delayed data ingestion in their Logs component, causing new data to not appear in the UI, delayed alerts, and dashboards showing missing or outdated values. The team identified the root cause and implemented a fix. The incident was resolved after 1.3 hours of monitoring to ensure the fix was effective.

SolarWinds Observability experienced delayed alert notifications for 39 minutes starting at 12:33 UTC due to higher than normal latency in the alerting system. The issue affected alert delivery timing, causing notifications to be delayed rather than sent immediately when triggered. The problem was identified, fixed, and resolved by 14:01 UTC, with alert notifications returning to normal delivery speeds.

SolarWinds Observability experienced degraded email alert notifications across multiple regions (NA-01, NA-02, EU-01, AP-01) for 1.8 hours, with some alerts being missed entirely. The team identified the root cause and implemented a fix, followed by monitoring to ensure resolution. The incident was fully resolved after the fix was confirmed to be working properly.

SolarWinds Observability experienced a 20-minute delay in Logs data ingestion specifically affecting customers using port-based destinations. During the incident, new log data did not appear in the UI, alerts were delayed, and dashboards displayed missing or outdated information. The issue was identified, fixed, and fully resolved with normal data processing restored.

SolarWinds Observability experienced a degradation in their EU-01 web interface, causing customers to encounter intermittent UI errors and monitoring data that failed to load on the home page. The engineering team implemented a fix and monitored the results before fully resolving the incident after 27 minutes.

SolarWinds Observability experienced degraded data ingestion for logs, metrics, and traces over 1.9 hours, causing gaps in telemetry data and missing alerts across all observability components including APM, Infrastructure, Network, Kubernetes, Database, and Alerting services. The root cause was identified and a fix was implemented, with systems returning to stable operation.

SolarWinds Observability experienced degraded Digital Experience Monitoring in the Washington DC AWS region for 24 minutes, causing synthetic checks and alerts to fail or perform poorly. The issue was identified and a fix was implemented, with affected probes returning to stable operation. Synthetic checks that were missed during the incident will not be re-run and may appear as missing data in customer dashboards.

SolarWinds Observability experienced a 4-hour data ingestion issue affecting logs, metrics, and traces across multiple components including Alerting, APM, DEM, RUM, and Infrastructure Observability. Users experienced gaps in telemetry data, delayed or missing alerts, and dashboards showing outdated values as new data failed to appear in the UI. The root cause was identified and resolved, with systems returning to stable operation.

SolarWinds Observability experienced a major outage lasting 87.7 hours that affected Digital Experience Monitoring in the Middle East region, specifically Dubai probes. The incident was caused by ongoing regional conflict and AWS datacenter infrastructure disruption, preventing synthetic checks and alerts from executing properly in that location. The issue was resolved by recommending customers reconfigure their monitoring checks to use alternative testing regions while the affected infrastructure remained unavailable.