Live / Imperva / Incident
Imperva: [INC-1145] Service degradation of multiple PoPs
Imperva · imperva.comMinor incidentResolved2026-09-28 09:56 UTC
Public — what happened
Summary
Imperva said that starting at 07:42 UTC on 2026-09-28, its Singapore network location (PoP) was having problems, with customers possibly seeing slower responses, Error 20 messages, and trouble with GRE tunnel connections. The company reported a fix within minutes, but at 08:26 UTC it said the same symptoms had appeared across multiple network locations. Imperva said traffic and tunnel connections were restored at all affected sites by 08:39 UTC, and it marked the incident resolved at 09:56 UTC. It did not name a cause, saying only that its investigation into the underlying reason was ongoing.
Affected
Singapore (XSP)
Timeline
- Started — 2026-09-28 07:42 UTC
- Investigating — 2026-09-28 07:42 UTC
- Monitoring — 2026-09-28 07:47 UTC
- Identified — 2026-09-28 08:26 UTC (2 updates)
- Monitoring — 2026-09-28 09:11 UTC
- Resolved — 2026-09-28 09:56 UTC · 2h 14m 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.