[INC-1142] Network Connectivity Degradation Across Multiple PoPs Due to an Upstream Provider Issue

What to do

• Check whether you use Imperva Chicago 1, IL (CHI), Detroit, MI (DET), Houston, TX (HOU), Los Angeles, CA (SNA) and 6 more in ca. 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 20h 28m it lasted.

  Anything that failed between 2026-09-22 11:29 UTC and 2026-09-23 07:57 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 5

1. investigatingSep 22, 2026, 11:29 AM UTC

   One of our upstream providers is currently experiencing a major outage. We are contacting the provider to gather more information about the issue. As a mitigation, we have rerouted traffic away from the affected carrier at the impacted PoPs, which has mitigated customer impact. We will continue to closely monitor the environment to ensure ongoing service stability. Further updates will be provided as more information becomes available.

   provider

2. monitoringSep 22, 2026, 11:38 AM UTC

   We have rerouted traffic away from the affected carrier in the impacted PoPs, mitigating customer impact. We will continue to closely monitor the environment to ensure ongoing service stability.

   provider

3. monitoringSep 22, 2026, 2:45 PM UTC

   To maintain service stability, the impacted upstream provider remains bypassed. Our teams continue to closely monitor the environment and are working with the upstream provider to gather further information. Additional updates will be provided as more details become available.

   provider

4. monitoringSep 23, 2026, 7:57 AM UTC

   The affected network path remains bypassed as a precautionary measure to ensure continued service stability across the Imperva network. Following the mitigation actions implemented, service has been restored to normal and no further customer impact has been observed. Our teams continue to closely monitor the environment to ensure ongoing stability. At this time, the bypass remains in place while the external network issue is being addressed. Additional updates will be provided as more information becomes available.

   provider

5. resolvedSep 23, 2026, 7:57 AM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

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