Is SolarWinds Observability down?
Last checked 2m agoNo incidents right now.
SolarWinds Observability is operational right now. Last checked 2m ago; the most recent incident resolved 3d ago.
Real-time SolarWinds Observability status, recent outages, and incident history: pulled directly from SolarWinds Observability's official status page at status.cloud.solarwinds.com every 5 minutes. Pingoru tracks 12 SolarWinds Observability services and has captured 5 incidents in the last 90 days (97.96% uptime). Get email, Slack, Discord, or webhook alerts the moment SolarWinds Observability reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days- Logs
Timeline · 3 updates
- identified · Oct 28, 2026, 02:02 AM UTC
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.
- identified · Oct 28, 2026, 02:27 AM UTC
We are continuing to work on a fix for this issue.
- resolved · Oct 28, 2026, 02:28 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.
Latest: The ingestion delay issue has been resolved. New data is now processing normally, and alerts and dashboards should reflect up-to-date information.
-
- AlertingLogs
Timeline · 7 updates
- investigating · Oct 06, 2026, 12:06 PM UTC
We are currently investigating an issue affecting log ingestion for a subset of customers. Customers using former Papertrail log ingestion endpoints may experience delayed processing or failed ingestion of new log data. Services not utilizing the affected ingestion path remain operational. We will provide an update within the hour.
- investigating · Oct 06, 2026, 01:11 PM UTC
We continue to investigate an issue affecting log ingestion for a subset of customers. Customers using former Papertrail log-ingestion endpoints may experience delayed processing or failed ingestion of new log data. Services not using the affected ingestion path remain operational. We will provide an update within the hour.
- identified · Oct 06, 2026, 01:43 PM UTC
We’ve identified the root cause of the degraded Logs data ingestion and are working on a fix. Customers using former Papertrail log ingestion endpoints may experience delayed processing or failed ingestion of new log data. Services not utilizing the affected ingestion path remain operational. Affected customers may see gaps in the telemetry data and experience missing alerts. We will provide an update within the hour.
- identified · Oct 06, 2026, 02:42 PM UTC
We’ve identified the root cause of the degraded Logs data ingestion and are still working on a fix. Customers using former Papertrail log ingestion endpoints may experience delayed processing or failed ingestion of new log data. Services not utilizing the affected ingestion path remain operational. Affected customers may see gaps in the telemetry data and experience missing alerts. We will provide an update within the hour.
- identified · Oct 06, 2026, 03:38 PM UTC
We’ve identified the root cause of the degraded Logs data ingestion and are still working on a fix. Customers using former Papertrail log ingestion endpoints may experience delayed processing or failed ingestion of new log data. Services not utilizing the affected ingestion path remain operational. Affected customers may see gaps in the telemetry data and experience missing alerts. We will provide an update within the hour.
- monitoring · Oct 06, 2026, 04:03 PM UTC
A fix has been implemented for the Logs data ingestion issue and the backlog is being processed. Customers using former Papertrail log ingestion endpoints may continue to experience delayed processing of new log data. Services not utilizing the affected ingestion path remain operational. Affected customers may see gaps in the telemetry data and experience missing alerts. We will provide an update within the hour.
- resolved · Oct 06, 2026, 04:24 PM UTC
The data ingestion issue has been resolved and data has been completely processed. Systems are now stable and operating as normal.
Latest: The data ingestion issue has been resolved and data has been completely processed. Systems are now stable and operating as normal.
-
- AlertingAPMDEMRUMLogsDatabase ObservabilityNetwork ObservabilityKubernetes ObservabilityInfrastructure ObservabilityAgent Downloads and Updates
Timeline · 5 updates
- investigating · Aug 20, 2026, 02:13 PM UTC
We’ve identified the cause of the delay in Logs, Metrics & 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.
- identified · Aug 20, 2026, 02:49 PM UTC
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.
- identified · Aug 20, 2026, 03:51 PM UTC
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.
- identified · Aug 20, 2026, 11:40 PM UTC
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.
- resolved · Aug 21, 2026, 12:41 AM UTC
The backfill is now complete. All data has been restored. New data is now processing normally, and alerts and dashboards should reflect up-to-date information.
Latest: The backfill is now complete. All data has been restored. New data is now processing normally, and alerts and dashboards should reflect up-to-date information.
-
Incident record
Since April 2026 · Statuspage by Atlassian · 12 components checked every 5 minutesThe longest incident in the last year, Degraded Digital Experience Monitoring [Middle East] on March 2, 2026, ran for 4 days. 15 maintenance windows announced in the same period.
Most affected components, last 12 months
- Alerting21
- Logs20
- APM6
- DEM6
- Infrastructure Observability5
Latest incidents
- Delayed Data Ingestion [EU-01]
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…
- Degraded Data Ingestion [NA-01, EU-01]
We are currently investigating an issue affecting log ingestion for a subset of customers. Customers using former Papertrail log ingestion endpoints may…
- Delayed Data Ingestion [EU-01]
We’ve identified the cause of the delay in Logs, Metrics & Traces data ingestion and are working on a fix. New data may not appear in the UI, alerts could be…
- Delayed Data Ingestion [EU-01] ResolvedStarted Oct 28, 2026, 02:02 AM UTC · Resolved Oct 28, 2026, 02:28 AM UTC · 25m
- Started Oct 06, 2026, 12:06 PM UTC · Resolved Oct 06, 2026, 04:24 PM UTC · 4h 17m
- Delayed Data Ingestion [EU-01] ResolvedStarted Aug 20, 2026, 02:13 PM UTC · Resolved Aug 21, 2026, 12:41 AM UTC · 10h 28m