Skip to main content
Imperva

[INC-1120 ] Service Degradation affecting a subset of customers in North America region

Degraded Lasted 4h 12m · started · Imperva's page

Level
confirmed
Worst impact
Degraded
Components
Chicago 1, IL (CHI), Detroit, MI (DET), Houston, TX (HOU), Los Angeles, CA (SNA), Miami, FL (FLL), Montreal, Canada (YUL), New York 2, NY (EWR)
Regions
ca, us

What to do

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

    Anything that failed between 2026-09-02 20:21 UTC and 2026-09-03 00:33 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 3

  1. investigating

    Imperva has been alerted to the fact that there have been two major fiber cuts in North America. These fiber cuts are within the network of a major upstream carrier. A subset of customer traffic coming to or going from the Imperva network may transit this infrastructure and as a result of this issue, customers may experience connectivity issues, increased latency, or service degradation. We will provide further updates as more information becomes available. The next update will be before 20:50 UTC

    provider

  2. monitoring

    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. resolved

    Monitoring has shown stable performance following the mitigation measures implemented earlier. This incident is considered resolved at this time. We will continue to monitor the environment as part of our standard operational practices to ensure ongoing service stability.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-726c50fdf1

Is Imperva still down?

No, this incident was resolved 2026-09-03 00:33 UTC. For Imperva's live state, see https://down.guide/imperva.

How long did it last?

4h 12m, from 2026-09-02 20:21 UTC to 2026-09-03 00:33 UTC, by the times Imperva posted.

What was affected?

Imperva named Chicago 1, IL (CHI), Detroit, MI (DET), Houston, TX (HOU), Los Angeles, CA (SNA) and 3 more in ca, us.

What caused it?

Imperva hasn't published a root cause. If it does, it shows here.

Where does this come from?

Imperva's official status page, https://status.imperva.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.