Skip to main content
Imperva

[INC-1146] Service degradation of MAD (Madrid) PoP

Partial outage Lasted 16h 12m · started · Imperva's page

Level
confirmed
Worst impact
Partial outage
Components
Madrid, Spain (MAD)

What to do

  • Check whether you use Imperva Madrid, Spain (MAD). 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 16h 12m it lasted.

    Anything that failed between 2026-09-28 09:53 UTC and 2026-09-29 02:05 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 6

  1. identified

    We have identified a connectivity issue affecting the Madrid (MAD) PoP. As a mitigation measure, traffic is being rerouted through alternate locations to reduce customer impact while our teams investigate. Some customers may experience intermittent latency or connectivity degradation. We are actively working to resolve the issue and will provide updates as more information becomes available.

    provider

  2. investigating

    We continue to investigate the connectivity issue affecting the Madrid (MAD) PoP. Traffic remains rerouted through alternate PoPs as a mitigation measure while investigations continue. Current monitoring indicates network services remain stable and traffic is being successfully handled through alternate locations. The MAD PoP will be returned to service once investigation and validation activities have been completed. We will continue to provide updates as more information becomes available.

    provider

  3. identified

    The connectivity issue has been identified and resolved by our technical teams, and the system will continue to be monitored for stability. The MAD (Madrid) PoP will be returned to service during the low traffic period for this PoP. This is scheduled for around 0001UTC Tuesday 29th September. A further update will be posted once this process has been completed.

    provider

  4. identified

    The team is preparing to begin the PoP activation shortly. We will closely monitor the PoP throughout the activation and provide further updates as the process progresses. The next update on this incident will be provided no later than 01:00 UTC on 29 September 2026.

    provider

  5. monitoring

    The MAD (Madrid) PoP has been successfully activated and returned to service. Our technical teams will continue to closely monitor the PoP to ensure stability and performance.

    provider

  6. resolved

    Service in the data center has been restored to normal. This incident has been resolved.

    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-6d4529701f

Is Imperva still down?

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

How long did it last?

16h 12m, from 2026-09-28 09:53 UTC to 2026-09-29 02:05 UTC, by the times Imperva posted.

What was affected?

Imperva named Madrid, Spain (MAD).

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.