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

As listed on Imperva’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the Imperva status & history page.

Related: Imperva status & history. SquidGrid is not affiliated with Imperva.