Live  /  Imperva  /  Incident

Imperva: [INC-1161] Issue Resulting in Unexpected IRA Blocking

Imperva · imperva.comResolved2026-10-13 17:29 UTC
Public — what happened

Summary

Imperva reported on October 13, 2026 at 15:18 UTC that some customers might be seeing IRA blocks applied in error, meaning legitimate activity could be wrongly stopped. By 15:30 UTC the company said it had found the cause, though it did not describe what it was, and it began rolling out fixes shortly after. Imperva said the fixes were in place by 16:28 UTC and appeared to be working, and at 17:29 UTC it declared the issue resolved with service back to normal.

Timeline

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

What SquidGrid measured

SquidGrid measured 28 internet paths into Imperva’s network during this incident. None of them ran meaningfully slower than the same paths the day before.

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 43, 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.