SolarWinds Observability Outage History

SolarWinds Observability is up right now

Pingoru has recorded 50 incidents for SolarWinds Observability: 32 in the last 12 months and 2 in the last 90 days.

Source: status.cloud.solarwinds.com

50incidents recorded
32last 12 months
2last 90 days
6 hourstypical duration
Incidents per month
036AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct1%
Pingoru began tracking SolarWinds Observability in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202623 of 720 (0%)
May 202600 of 744 (0%)
June 202667 of 720 (1%)
July 202622 of 744 (0%)
August 2026111 of 744 (1%)
September 202600 of 720 (0%)
October 202614 of 587 (1%)

Incidents, newest first

Notice June 10, 2025 Degraded Data Ingestion in NA-01 from Heroku platform 17h 8m Alerting

Started Jun 10, 2025, 08:50 AM UTC· resolved Jun 11, 2025, 01:59 AM UTC

  1. identified Jun 10, 2025, 08:50 AM UTC

    We are observing an incident with log delivery from Heroku to SolarWinds Observability SaaS due to an ongoing Heroku incident. This may affect a subset of customers using the Heroku plug-in to send logs to SolarWinds Observability SaaS. More details on the Heroku incident are available at https://status.heroku.com/incidents/2822. Affected customers may see gaps in the Logs data and experience missing alerts. Next update in one hour or as events warrant.

  2. identified Jun 10, 2025, 10:05 AM UTC

    We continuing to monitor an incident with log delivery from Heroku to SolarWinds Observability SaaS due to an ongoing Heroku incident. More details on the Heroku incident are available at https://status.heroku.com/incidents/2822. Next update in one hour or as events warrant.

  3. identified Jun 10, 2025, 11:06 AM UTC

    We continuing to monitor an incident with log delivery from Heroku to SolarWinds Observability SaaS due to an ongoing Heroku incident. More details on the Heroku incident are available at https://status.heroku.com/incidents/2822. Next update after two hours or sooner as events warrant.

  4. identified Jun 10, 2025, 02:14 PM UTC

    We continuing to monitor an incident with log delivery from Heroku to SolarWinds Observability SaaS due to an ongoing Heroku incident. More details on the Heroku incident are available at https://status.heroku.com/incidents/2822. Next update after two hours or sooner as events warrant.

  5. identified Jun 10, 2025, 04:41 PM UTC

    We continuing to monitor an incident with log delivery from Heroku to SolarWinds Observability SaaS due to an ongoing Heroku incident. More details on the Heroku incident are available at https://status.heroku.com/incidents/2822. Next update after two hours or sooner as events warrant.

  6. monitoring Jun 10, 2025, 06:53 PM UTC

    The Heroku incident is not yet resolved but we are seeing significant improvement with regards to log delivery from Heroku to SolarWinds Observability SaaS. We will continue to monitor the progress of the log delivery from Heroku as well as the ongoing Heroku incident. More details on the Heroku incident are available at https://status.heroku.com/incidents/2822. Next update after two hours or sooner as events warrant.

  7. monitoring Jun 10, 2025, 09:33 PM UTC

    The Heroku incident is not yet resolved but we are seeing significant improvement with regards to log delivery from Heroku to SolarWinds Observability SaaS. We will continue to monitor the progress of the log delivery from Heroku as well as the ongoing Heroku incident. More details on the Heroku incident are available at https://status.heroku.com/incidents/2822. Next update after two hours or sooner as events warrant.

  8. monitoring Jun 10, 2025, 11:40 PM UTC

    The Heroku incident is not yet resolved but we are seeing significant improvement with regards to log delivery from Heroku to SolarWinds Observability SaaS. We will continue to monitor the progress of the log delivery from Heroku as well as the ongoing Heroku incident.

  9. resolved Jun 11, 2025, 01:59 AM UTC

    Log delivery from Heroku to SolarWinds Observability SaaS has returned to normal. If it appears that Heroku isn't sending logs to your SolarWinds Observability SaaS account please follow the instructions at https://status.heroku.com/incidents/2822 and/or contact Heroku support.

Read the full incident report →

Notice May 22, 2025 Degraded Data Ingestion for Database Observability Instrumentation for PostgreSQL [NA-01] –

Started May 22, 2025, 07:00 PM UTC· resolved May 22, 2025, 07:00 PM UTC

  1. resolved Jul 08, 2025, 03:01 PM UTC

    Between May 22nd and May 27th, we identified an issue affecting Database Observability instrumentation for PostgreSQL databases, which resulted in telemetry events not being captured. As a result, affected customers may notice gaps in their observability data during this period.

Read the full incident report →

Minor May 19, 2025 Delayed Ingestion [NA-01] 1h 7m Alerting, Logs

Started May 19, 2025, 11:58 PM UTC· resolved May 20, 2025, 01:05 AM UTC

  1. investigating May 19, 2025, 11:58 PM UTC

    We are investigating

  2. identified May 20, 2025, 12:18 AM UTC

    We've identified the cause of the delay in data ingestion and are working on a fix. New log data may not appear in the UI, log alerts could be delayed, and some dashboards might show missing or outdated values. This is impacting all customers sending logs. We'll provide an update within the hour.

  3. monitoring May 20, 2025, 12:55 AM UTC

    A fix for the ingestion delays has been deployed, and we're actively monitoring to ensure full recovery. Some new log data may still be missing from the UI, log alerts may be delayed, and dashboards could reflect outdated information. This is impacting all customers sending logs. We'll share another update within the hour.

  4. resolved May 20, 2025, 01:05 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. This incident impacted all customers sending logs but systems are now fully recovered.

Read the full incident report →

Minor May 6, 2025 Degraded Web Interface [NA-02, EU-01, AP-01] 9h 34m Alerting, APM, DEM, RUM and 5 more

Started May 06, 2025, 07:45 PM UTC· resolved May 07, 2025, 05:20 AM UTC

  1. investigating May 06, 2025, 07:45 PM UTC

    We are investigating

  2. identified May 07, 2025, 12:42 AM UTC

    The issue has been identified and a fix is being implemented. Next update in 3 hours.

  3. identified May 07, 2025, 02:11 AM UTC

    We are continuing to work on fixing the issue. The next update will be provided in 3 hours.

  4. monitoring May 07, 2025, 05:13 AM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved May 07, 2025, 05:20 AM UTC

    This incident has been resolved.

Read the full incident report →