Live / Imperva / Incident
Imperva: [INC-1146] Service degradation of MAD (Madrid) PoP
Imperva · imperva.comMajor incidentResolved2026-09-29 02:05 UTC
Public — what happened
Summary
Imperva said it found a connectivity problem at its Madrid (MAD) point of presence on 28 September 2026 at 09:53 UTC, and that some customers could see intermittent slowness or degraded connections. The company said it shifted traffic to other locations to limit the impact while it investigated, and reported that services stayed stable during that time. By 16:22 UTC Imperva said the problem had been fixed, though it did not describe a cause, and it planned to bring the Madrid site back online during a quieter period. The site was reactivated by 01:01 UTC on 29 September, and Imperva marked the incident resolved at 02:05 UTC.
Affected
Madrid, Spain (MAD)
Timeline
- Started — 2026-09-28 09:53 UTC
- Identified — 2026-09-28 09:53 UTC
- Investigating — 2026-09-28 10:06 UTC
- Identified — 2026-09-28 16:22 UTC (2 updates)
- Monitoring — 2026-09-29 01:01 UTC
- Resolved — 2026-09-29 02:05 UTC · 16h 12m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Imperva against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Imperva: paths off baseline right now, where on the route conditions change, and its full incident track record.
Included with any paid plan.
Open the Imperva report →
More from Imperva
Covered in The Squid’s Ink, Week 41, 2026, our weekly internet health report.