SolarWinds Observability incident

Degraded Data Ingestion in NA-01 from Heroku platform

Notice Resolved View vendor source →

SolarWinds Observability experienced a notice incident on June 10, 2025 affecting Alerting, lasting 17h 8m. The incident has been resolved; the full update timeline is below.

Started
Jun 10, 2025, 08:50 AM UTC
Resolved
Jun 11, 2025, 01:59 AM UTC
Duration
17h 8m
Detected by Pingoru
Jun 10, 2025, 08:50 AM UTC

Affected components

Alerting

Update timeline

  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.