Vendor reports: degradedResolved · vendor status “resolved”Official status API

Delayed Data Ingestion [NA-01]

Reported by SolarWinds · Observability & Incident · source last read 3 min ago

Official source (opens in a new tab)
Vendor start
Jun 24, 2025, 16:25 UTC
Vendor's clock
Resolved
Jun 24, 2025, 23:08 UTC
Vendor's clock
First seen by Statuswall
Nov 11, 2026, 02:12 UTC
Statuswall's clock
Duration
6 h 44 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • SolarWinds reports degraded: "Delayed Data Ingestion [NA-01]".[E1, E2]
  • The vendor marked it resolved at 2025-06-24 23:08 UTC.[E3, E7]

Affected products and regions

  • Components: Alerting, APM, DEM, RUM, Logs, Database Observability, Network Observability, Kubernetes Observability, Infrastructure Observability.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-11-11 02:12 UTC · summary s1, evidence 54e9091e3bf29010

Evidence (8)
  1. E1SolarWinds reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Delayed Data Ingestion [NA-01]". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2025-06-24 16:25 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Alerting, APM, DEM, RUM, Logs, Database Observability, Network Observability, Kubernetes Observability, Infrastructure Observability. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2025-06-24 23:08 UTC. (vendor) source (opens in a new tab)
  8. E8First seen by Statuswall: 2026-11-11 02:12 UTC. (Statuswall)

Affected scope

Not stated by the vendor

Components: Alerting, APM, DEM, RUM, Logs, Database Observability, Network Observability, Kubernetes Observability, Infrastructure Observability

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

SolarWinds is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Jun 24, 2025, 16:25 UTCVendor-reported startVendor time
  2. Jun 24, 2025, 23:08 UTCVendor-reported resolutionVendor time
  3. Nov 11, 2026, 02:12 UTCFirst seen by Statuswall (vendor status: resolved)Seen by Statuswall