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

Data ingestion delayed

Reported by Statsig · Data & Analytics · source last read just now

Official source (opens in a new tab)
Vendor start
Jun 20, 2026, 03:22 UTC
Vendor's clock
Resolved
Jun 20, 2026, 11:00 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
7 h 38 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

  • Statsig reports degraded: "Data ingestion delayed".[E1, E2]
  • The vendor marked it resolved at 2026-06-20 11:00 UTC.[E3, E7]

Affected products and regions

  • Components: Experiment Results (Cloud), Experiment Results (Warehouse Native), Event Forwarding Pipeline (Warehouse Native).[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-06-20 11:00 UTC · summary s1, evidence f4be855f9fed7d50

Evidence (7)
  1. E1Statsig reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Data ingestion delayed". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-06-20 03:22 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Experiment Results (Cloud), Experiment Results (Warehouse Native), Event Forwarding Pipeline (Warehouse Native). (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-06-20 11:00 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Experiment Results (Cloud), Experiment Results (Warehouse Native), Event Forwarding Pipeline (Warehouse Native)

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

Statsig 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 20, 2026, 03:22 UTCVendor-reported startVendor time
  2. Jun 20, 2026, 11:00 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.