Skip to main content
Imperva

[INC-988] Chicago 2, IL (CHI) Data Center Issue

Degraded Lasted 7h 28m · started · Imperva's page

Level
confirmed
Worst impact
Degraded
Components
Chicago 1, IL (CHI)

What to do

  • Check whether you use Imperva Chicago 1, IL (CHI). 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 7h 28m it lasted.

    Anything that failed between 2026-03-05 22:30 UTC and 2026-03-06 05:58 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. investigating

    Technical teams are investigating a potential issue in the Chicago 2, IL (CHI) data center. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

    provider

  2. identified

    We have identified an issue in the data center. Traffic continues to be rerouted through an alternate data center in the region. Customers may experience some latency while the reroute remains in place. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

    provider

  3. identified

    To maintain service stability, the Chicago 2, IL (CHI) data center will remain in bypass mode until off-site hours. During this time, customer traffic will continue to be served by alternate data centers in the region. Further updates will be shared as the situation progresses. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

    provider

  4. monitoring

    A fix has been implemented and traffic has been restored to the data center. We are continuing to monitor in order to ensure that service has returned to normal. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

    provider

  5. resolved

    Service in the data center has been restored to normal. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

    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-1d45c4e6f5

Is Imperva still down?

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

How long did it last?

7h 28m, from 2026-03-05 22:30 UTC to 2026-03-06 05:58 UTC, by the times Imperva posted.

What was affected?

Imperva named Chicago 1, IL (CHI).

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.