Live  /  Providers  /  Imperva

Imperva

imperva.comNo open incidents

Independent assessment — SquidGrid is not affiliated with Imperva. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

CDN & edge · SquidGrid tracks Imperva’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what Imperva is reporting

Current & recent incidents

Resolved

[INC-1146] Service degradation of MAD (Madrid) PoP

Major impact · 2026-09-29 02:05 UTC

Resolved

[INC-1147] Service degradation of LCY (London) PoP

None impact · 2026-09-28 11:42 UTC

Resolved

[INC-1145] Service degradation of multiple PoPs

Minor impact · 2026-09-28 09:56 UTC

Resolved

[INC-1143] ABP Service issue

Minor impact · 2026-09-23 06:00 UTC

Resolved

[INC-1143] ABP Service issue

Minor impact · 2026-09-23 04:42 UTC

Resolved

[INC-1136] Service Degradation Affecting SIEM Log Ingestion

Minor impact · 2026-09-18 01:30 UTC

Mirrored from the provider’s own published status. Times in UTC.

Independent path health

A status page tells you what Imperva has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

SquidGrid’s own measurement fleet is watching 942 internet paths that cross Imperva’s network, observed from 35 countries. At last check (02:45 UTC), every measured path within its usual range. Signed-in customers see which paths, the carrier on each side, and the added latency.

SquidGrid is not affiliated with Imperva.