Live / Imperva / Incident
Imperva: [INC-1136] Service Degradation Affecting SIEM Log Ingestion
Imperva · imperva.comMinor incidentResolved2026-09-18 01:30 UTC
Public — what happened
Summary
Imperva reported a minor problem starting at 23:11 UTC on September 17, 2026, in which some customers were getting their SIEM security logs sent from IP addresses the company no longer expected to be active. By 23:52 UTC Imperva said it had pinpointed the source, though it did not describe what that source was, and began applying fixes to limit the impact. The company said the fixes were in place and things were working normally by 00:59 UTC on September 18, and it declared the incident resolved at 01:30 UTC after a period of monitoring.
Affected
SIEM Logs
Timeline
- Started — 2026-09-17 23:11 UTC
- Investigating — 2026-09-17 23:11 UTC (2 updates)
- Identified — 2026-09-18 00:25 UTC
- Monitoring — 2026-09-18 00:59 UTC
- Resolved — 2026-09-18 01:30 UTC · 2h 18m 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.