SolarWinds Observability incident

Degraded Data Ingestion [NA-01]

Minor Resolved View vendor source →
Started
Mar 13, 2026, 09:04 PM UTC
Resolved
Mar 13, 2026, 10:54 PM UTC
Duration
1h 50m
Detected by Pingoru
Mar 13, 2026, 09:04 PM UTC

Affected components

AlertingAPMLogsDatabase ObservabilityNetwork ObservabilityKubernetes ObservabilityInfrastructure Observability

Update timeline

  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.

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