Live / Incidents / Imperva
Imperva: [INC-1106] Elevated Latency for a Subset of Origin Fetch Traffic in Ashburn, VA (WDC)
Imperva · imperva.comImpact: minorResolved2026-09-02 17:30 UTC
Public — what happened
Summary
The third-party CDN provider has completed the remediation for the routing issue. We have confirmed through our observations and log data that traffic continues to route as expected, with origin fetch traffic operating normally and latency within expected ranges.
The service has remained stable throughout the monitoring period, and the incident is now considered resolved.
We appreciate your patience and understanding while we worked with our third-party provider to resolve this issue.
Timeline
- Started — 2026-08-13 16:53 UTC
- Last update — 2026-09-02 17:30 UTC
- Resolved — 2026-09-02 17:30 UTC
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 →