Live  /  Imperva  /  Incident

Imperva: [INC-1166] Service Degradation Affecting Newly Onboarded Sites

Imperva · imperva.comMinor incidentResolved2026-10-20 16:21 UTC
Public — what happened

Summary

Imperva said some newly onboarded sites were affected by a service degradation involving resolution, which it began investigating at 08:43 UTC on 2026-10-20. By 09:04 UTC the company said its teams had identified the problem, and over the next several hours it reported ongoing work to reduce the impact, including configuration changes. Imperva said a fix was put in place and being monitored at 16:12 UTC, and it marked the incident resolved at 16:21 UTC. The company rated it as minor and did not state a cause.

Affected

Cloud Security Management Platform

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.

What SquidGrid measured

SquidGrid measured 54 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 44, 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.