Skip to main content
Imperva

[INC-1173] - QRO PoP Connectivity Issue

Major outage Lasted 9h 5m · started · Imperva's page

Level
confirmed
Worst impact
Major outage
Components
Queretaro, Mexico (QRO)

What to do

  • Check whether you use Imperva Queretaro, Mexico (QRO). 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 9h 5m it lasted.

    Anything that failed between 2026-10-29 00:09 UTC and 2026-10-29 09:14 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 7

  1. identified

    We have identified an issue in the 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

    Traffic remains rerouted through alternate PoPs in the region. Customers may experience increased latency while the reroute is in place.

    provider

  3. identified

    Third-party upstream providers in the region are experiencing issues, and our teams remain in close contact with them for updates. Traffic will continue to be rerouted through alternate PoPs in the region while the providers work to resolve the issue.

    provider

  4. identified

    Our upstream providers have confirmed that corrective measures have been implemented and are reporting improvements in network performance. We are also observing improvements, and our teams will continue to closely monitor the situation to ensure sustained stability before reactivating the Queretaro, Mexico (QRO) PoP and restoring normal traffic routing.

    provider

  5. identified

    Our teams continue to monitor network stability and coordinate with upstream providers to confirm full service restoration before reactivating the Queretaro, Mexico (QRO) PoP.

    provider

  6. monitoring

    Following confirmation of resolution from our upstream providers and verification of network stability, the Queretaro, Mexico (QRO) PoP has been reactivated. Our team will continue to monitor performance to ensure ongoing stability.

    provider

  7. resolved

    Monitoring has confirmed that network performance is stable and services are operating normally.

    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-c3e543ca84

Is Imperva still down?

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

How long did it last?

9h 5m, from 2026-10-29 00:09 UTC to 2026-10-29 09:14 UTC, by the times Imperva posted.

What was affected?

Imperva named Queretaro, Mexico (QRO).

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.