Live / Imperva / Incident
Imperva: [INC-1106] Elevated Latency for a Subset of Origin Fetch Traffic in Ashburn, VA (WDC)
Imperva · imperva.comMinor incidentResolved2026-09-02 17:30 UTC
Public — what happened
Summary
Imperva said that starting August 13, 2026, some traffic from its Ashburn, Virginia (WDC) location to customers' own servers was being sent through networks in the Asia-Pacific region rather than the eastern US, slowing down access to some websites. The company attributed this to incorrect location data at a third-party CDN provider and said it offered affected customers a workaround on request while waiting for a permanent fix. Imperva reported delays from the provider along the way, then said on September 2 that the provider's fix was in place, latency was back to normal, and the incident was resolved at 17:30 UTC.
Affected
Ashburn, VA (WDC)
Timeline
- Started — 2026-08-13 16:53 UTC
- Investigating — 2026-08-13 16:53 UTC (3 updates)
- Identified — 2026-08-13 21:12 UTC (2 updates)
- Monitoring — 2026-09-02 13:11 UTC
- Resolved — 2026-09-02 17:30 UTC · 20 days after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Imperva against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Imperva: paths off baseline right now, where on the route conditions change, and its full incident track record.
Included with any paid plan.
Open the Imperva report →
More from Imperva