Live / Imperva / Incident
Imperva: INC-1163 SIEM log investigation
Imperva · imperva.comResolved2026-10-15 23:05 UTC
Public — what happened
Summary
Imperva said it was looking into a problem with SIEM log data that could make the information shown to some customers inaccurate, starting at 21:49 UTC on 2026-10-15. By 22:36 UTC the company said it had found the source of the problem and was working on steps to restore normal service. At 23:05 UTC Imperva reported that it had put those steps in place and confirmed the accuracy of the environment, and the incident was marked resolved.
Timeline
- Started — 2026-10-15 21:49 UTC
- Investigating — 2026-10-15 21:49 UTC
- Identified — 2026-10-15 22:36 UTC
- Resolved — 2026-10-15 23:05 UTC · 1h 16m after it started
What SquidGrid measured
SquidGrid measured 19 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 43, 2026, our weekly internet health report.