Live / Imperva / Incident
Imperva: [INC-1152] IPv6 connectivity degradation across multiple PoPs
Imperva · imperva.comMinor incidentResolved2026-10-06 01:48 UTC
Public — what happened
Summary
Imperva said that starting at 08:41 UTC on October 5, 2026, customers connecting over IPv6 had network problems at several of its locations, while IPv4 users were initially unaffected. Over the morning the trouble moved around, with Singapore and Atlanta recovering and then seeing it return, Detroit becoming affected, and Warsaw also showing IPv4 issues, so Imperva routed Warsaw traffic elsewhere. By 12:11 UTC the company reported Singapore, Atlanta, Detroit and Tokyo back to normal, and it brought Warsaw back online at 00:42 UTC on October 6 without publicly naming a cause. Imperva marked the incident resolved at 01:48 UTC on October 6.
Affected
Atlanta, GA (ATL), Detroit, MI (DET), Singapore (XSP), Tokyo, Japan (NRT), Warsaw, Poland (WAR)
Timeline
- Started — 2026-10-05 08:41 UTC
- Investigating — 2026-10-05 08:41 UTC (8 updates)
- Monitoring — 2026-10-05 12:11 UTC (3 updates)
- Resolved — 2026-10-06 01:48 UTC · 17h 07m after it started
What SquidGrid measured
SquidGrid measured 49 internet paths into Imperva’s network during this incident. None of them ran meaningfully slower than the same paths the day before.
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
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.