[INC-1152] IPv6 connectivity degradation across multiple PoPs

What to do

• Check whether you use Imperva Atlanta, GA (ATL), Detroit, MI (DET), Singapore (XSP), Tokyo, Japan (NRT) and 1 more in apac, jp. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 17h 7m it lasted.

  Anything that failed between 2026-10-05 08:41 UTC and 2026-10-06 01:48 UTC may need a replay.

• Subscribe to Imperva's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=imperva works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Imperva 12

1. investigatingOct 5, 2026, 8:41 AM UTC

   We are investigating an issue affecting network connectivity for customers using IPv6 addresses at multiple locations. Customers using IPv4 connectivity are not impacted. Our teams are actively investigating the issue and working to identify the appropriate remediation. We will provide further updates as more information becomes available.

   provider

2. investigatingOct 5, 2026, 9:07 AM UTC

   Our investigation remains ongoing, and our teams are actively working to identify the cause and implement the appropriate remediation. The next update will be provided no later than 09:40 UTC.

   provider

3. investigatingOct 5, 2026, 9:32 AM UTC

   We are continuing to address the IPv6 connectivity issue across our network. Service for Atlanta, GA (ATL) and Tokyo, Japan (NRT) is operating normally. Our teams are actively investigating the root cause and working on a permanent resolution. The next update will be provided by 10:00 UTC.

   provider

4. investigatingOct 5, 2026, 9:57 AM UTC

   We are continuing to address the IPv6 connectivity issue across our network. Service for Singapore (XSP), Tokyo (NRT), and Atlanta (ATL) is operating normally. Our teams are actively investigating the root cause and working to restore full connectivity for the remaining affected locations (WAR). The next update will be provided by 10:30 UTC.

   provider

5. investigatingOct 5, 2026, 10:26 AM UTC

   We are observing a recurrence of the IPv6 connectivity issues affecting Singapore (XSP). Service in Tokyo (NRT) and Atlanta (ATL) remains fully operational. Our engineering team is actively investigating the cause of this regression and working to restore stability to XSP, as well as resolving the ongoing impact in Warsaw (WAR). The next update will be provided by 11:00 UTC

   provider

6. investigatingOct 5, 2026, 11:02 AM UTC

   We are observing a recurrence of IPv6 connectivity issues affecting Singapore (XSP) and Atlanta (ATL). Service in Tokyo (NRT) remains fully operational. Additionally, IPv4 issues were observed for Warsaw (WAR). Traffic for WAR has been bypassed to restore service stability while our engineering teams actively investigate the root cause for XSP and the underlying issue at WAR. The next update will be provided by 11:30am UTC

   provider

7. investigatingOct 5, 2026, 11:34 AM UTC

   Our investigation is ongoing, and our teams are actively working to identify the cause and implement the appropriate remediation. The next update will be provided by 12:05 UTC.

   provider

8. investigatingOct 5, 2026, 11:45 AM UTC

   We are observing IPv6 connectivity issues affecting Detroit, MI (DET). Our teams are actively investigating the issue and working to implement remediation. The next update will be provided by 13:15 UTC.

   provider

9. monitoringOct 5, 2026, 12:11 PM UTC

   Service for Singapore (XSP), Atlanta (ATL), Detroit (DET), and Tokyo (NRT) has been fully restored and is operating normally. Traffic for Warsaw (WAR) remains bypassed while our engineering teams complete final validation and plan to bring the PoP back online during scheduled off-peak maintenance hours. . We are actively monitoring the system, and the next update will be provided by 13:00 UTC

   provider

10. monitoringOct 5, 2026, 1:06 PM UTC

    Network traffic across all core points of presence—including Singapore (XSP), Atlanta (ATL), Detroit (DET), and Tokyo (NRT)—remains stable and fully operational following our earlier remediation efforts. Our engineering teams are keeping a close watch on system performance, and we will share a follow-up update as soon as the Warsaw (WAR) PoP is successfully brought back online.

    provider

11. monitoringOct 6, 2026, 12:42 AM UTC

    The Warsaw (WAR) PoP has been successfully activated and is now operational. Network traffic across all core Points of Presence—including Singapore (XSP), Atlanta (ATL), Detroit (DET), Tokyo (NRT), and Warsaw (WAR)—remains stable and fully operational following our remediation efforts. Our engineering teams will continue to closely monitor system performance.

    provider

12. resolvedOct 6, 2026, 1:48 AM UTC

    Traffic across all affected PoPs is stable, and services are operating normally with no further impact observed.

    provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.