Live / Imperva / Incident
Imperva: [INC-1182] Delay of Cloud Security Management Configuration Changes
Imperva · imperva.comMinor incidentResolved2026-11-05 17:57 UTC
Public — what happened
Summary
Imperva said some customers experienced delays when applying certain configuration changes in its Cloud Security Management service, starting around 15:00 UTC on 4 November 2026. It said not all customers or changes were affected, and it rolled out a phased fix during low-traffic periods, which by late that day left only about 5% of capacity affected. By the next morning, it said remaining delays were limited to its Jakarta, Kuala Lumpur and Manila locations, and it reported the problem mitigated at 16:23 UTC and resolved at 17:57 UTC on 5 November. Imperva did not state a cause in its updates.
Affected
Cloud Security Management Configuration Changes
Timeline
- Started — 2026-11-04 15:00 UTC
- Investigating — 2026-11-04 15:00 UTC (2 updates)
- Identified — 2026-11-04 15:23 UTC (3 updates)
- Monitoring — 2026-11-05 16:23 UTC
- Resolved — 2026-11-05 17:57 UTC · 26h 58m after it started
What SquidGrid measured
SquidGrid measured 45 internet paths into Imperva’s network during this incident. None of them ran meaningfully slower than the same paths the day before.
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 46, 2026, our weekly internet health report.