Live / Imperva / Incident
Imperva: [INC-1135] Service Degradation Causing Intermittent DNS Resolution Issues
Imperva · imperva.comMinor incidentResolved2026-09-18 00:09 UTC
Public — what happened
Summary
Imperva reported a minor problem starting at 18:57 UTC on September 17, 2026, in which some customers' DNS lookups (the step that turns web addresses into locations computers can reach) would occasionally fail. The company described the failures as sporadic and affecting only a small share of requests. Imperva said at 19:50 UTC that it had pinpointed the cause, though it did not describe it publicly, and then rolled out a fix gradually across the affected systems, reporting the work finished at 22:04 UTC. After a period of monitoring, Imperva marked the incident resolved at 00:09 UTC on September 18.
Affected
CDN and WAF Management
Timeline
- Started — 2026-09-17 18:57 UTC
- Investigating — 2026-09-17 18:57 UTC (2 updates)
- Identified — 2026-09-17 19:50 UTC (4 updates)
- Monitoring — 2026-09-17 22:04 UTC
- Resolved — 2026-09-18 00:09 UTC · 5h 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 39, 2026, our weekly internet health report.