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)

As listed on Imperva’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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.

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 see
Customers 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.

The full archive is on the Imperva status & history page.

Related: Imperva status & history. SquidGrid is not affiliated with Imperva.