Live  /  Imperva  /  Incident

Imperva: Service Degradation Affecting Email Notifications

Imperva · imperva.comMinor incidentResolved2026-08-30 10:57 UTC
Public — what happened

Summary

Imperva reported a minor problem with its email notifications starting at 09:05 UTC on 2026-08-30, saying customers might see notification and confirmation emails arrive late or not at all. By 09:37 UTC the company said it had found a likely source and was checking its findings, though it did not publicly describe what that source was. Imperva said delivery began recovering after it put fixes in place around 10:30 UTC, and it declared the incident resolved at 10:57 UTC, adding that it would review what contributed to the issue.

Affected

CDN and WAF Management

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

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

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