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

Aug 26 Incident Follow-up: Feature Gate Exposure Data Delayed for Some Warehouse-Native (WHN) Customers

Reported by Statsig · Data & Analytics · source last read 3 min ago

Official source (opens in a new tab)
Vendor start
Aug 28, 2026, 22:40 UTC
Vendor's clock
Resolved
Aug 31, 2026, 16:17 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
2 d 17 h
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: "Aug 26 Incident Follow-up: Feature Gate Exposure Data Delayed for Some Warehouse-Native (WHN) Customers".[E1, E2]
  • The vendor marked it resolved at 2026-08-31 16:17 UTC.[E3, E7]

Affected products and regions

  • Components: 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-08-31 16:17 UTC · summary s1, evidence fda08762547c25fb

Evidence (7)
  1. E1Statsig reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Aug 26 Incident Follow-up: Feature Gate Exposure Data Delayed for Some Warehouse-Native (WHN) Customers". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-08-28 22:40 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Event Forwarding Pipeline (Warehouse Native). (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-08-31 16:17 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: 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. Aug 28, 2026, 22:40 UTCVendor-reported startVendor time
  2. Aug 31, 2026, 16:17 UTCVendor-reported resolutionVendor time

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