Jun 29, 12:13 UTC
Resolved - The web interface issues have been resolved and services have returned to normal operations.

Jun 29, 12:03 UTC
Monitoring - 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.

Jun 29, 11:41 UTC
Identified - 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.

Jun 29, 11:11 UTC
Investigating - 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.

Jun 27, 01:03 UTC
Resolved - The data ingestion issue has been resolved and systems are stable.

Jun 27, 00:48 UTC
Monitoring - 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.

Jun 27, 00:18 UTC
Investigating - We’ve identified the root cause of the degraded Logs 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.

Jun 16, 11:03 UTC
Resolved - This incident has been resolved.

Jun 16, 10:30 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Jun 16, 09:20 UTC
Update - We are still investigating this issue.

Jun 16, 07:52 UTC
Investigating - We’ve identified the cause of the delay in 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.

Jun 12, 00:00 UTC
Resolved - 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.