Live / Imperva / Incident
Imperva: [INC-1165] Service Degradation Affecting Newly Onboarded Sites
Imperva · imperva.comResolved2026-10-19 22:47 UTC
Public — what happened
Summary
Imperva said some newly onboarded sites were affected by a service degradation involving site resolution, which it began investigating at 17:38 UTC on 2026-10-19. The company said it identified the problem at 19:27 UTC, tested mitigation measures, and reported by 21:29 UTC that normal service had been restored. After a period of monitoring, Imperva confirmed at 22:47 UTC that the issue was resolved. It did not describe the underlying cause in its updates.
Timeline
- Started — 2026-10-19 17:38 UTC
- Investigating — 2026-10-19 17:38 UTC (3 updates)
- Identified — 2026-10-19 19:27 UTC (3 updates)
- Monitoring — 2026-10-19 21:35 UTC
- Resolved — 2026-10-19 22:47 UTC · 5h 10m after it started
What SquidGrid measured
SquidGrid measured 42 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 44, 2026, our weekly internet health report.