Live / Imperva / Incident
Imperva: [INC-1160] Degradation of Imperva Generated Certificate Issuance
Imperva · imperva.comMinor incidentResolved2026-10-13 17:44 UTC
Public — what happened
Summary
Imperva reported a minor problem with issuing its own Imperva-generated certificates starting at 13:29 UTC on October 13, 2026, which could interfere with customers adding new websites using those certificates or renewing existing ones. The company stated that customer sites stayed protected throughout. By 15:38 UTC, Imperva said the trouble stemmed from a degraded third-party service and that certificate issuance was working again. After a period of monitoring, it declared the incident resolved at 17:44 UTC.
Affected
Cloud Security Management Platform
Timeline
- Started — 2026-10-13 13:29 UTC
- Identified — 2026-10-13 13:29 UTC (2 updates)
- Monitoring — 2026-10-13 15:38 UTC
- Resolved — 2026-10-13 17:44 UTC · 4h 16m after it started
What SquidGrid measured
SquidGrid measured 41 internet paths into Imperva’s network during this incident. None of them ran meaningfully slower than the same paths the day before.
With SquidGrid — where it starts on the route
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 seeCustomers 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.