checked Sep 11, 2026 10:53 AM UTC · Imperva's official status page
Imperva is under maintenance.
Statusfield watches Imperva alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
Email only. No password. Free.
13 reports published by Imperva in the last 30 days
When Imperva breaks, it is typically resolved in 4h 9m — median across 15 resolved incidents over 90 days.
resolvedSep 11 · 01:50 UTC
The issue affecting user management has been resolved. Based on successful testing and continued stability, we have confirmed that the service is operating as expected, and the incident is considered resolved.
Reported by Imperva on their status page.
resolvedSep 10 · 22:31 UTC
Service levels have been restored and the Imperva Management Portal has returned to normal functionality. At this time this incident is being considered resolved. We apologize for any inconvenience this issue may have caused.
Reported by Imperva on their status page.
resolvedSep 9 · 22:29 UTC
Monitoring has confirmed that the environment remains stable, with no further issues observed. The incident is now confirmed as resolved, and normal service has been restored.
Reported by Imperva on their status page.
resolvedSep 8 · 05:37 UTC
Technical team implemented the necessary fixes, completed validation activities, and confirmed service stability through continuous monitoring. All services are operating normally. PoP is fully operational and ready for service.
Reported by Imperva on their status page.
resolvedSep 3 · 00:33 UTC
Monitoring has shown stable performance following the mitigation measures implemented earlier. This incident is considered resolved at this time. We will continue to monitor the environment as part of our standard operational practices to ensure ongoing service stability.
Reported by Imperva on their status page.
resolvedSep 2 · 17:30 UTC
The third-party CDN provider has completed the remediation for the routing issue. We have confirmed through our observations and log data that traffic continues to route as expected, with origin fetch traffic operating normally and latency within expected ranges. The service has remained stable throughout the monitoring period, and the incident is now considered resolved. We appreciate your patience and understanding while we worked with our third-party provider to resolve this issue.
Reported by Imperva on their status page.
resolvedSep 2 · 07:16 UTC
Technical team implemented the necessary fixes, completed validation activities, and confirmed service stability through continuous monitoring. All services are operating normally. PoP is fully operational and ready for service.
Reported by Imperva on their status page.
resolvedAug 30 · 10:57 UTC
We have implemented corrective actions and confirmed that the affected functionality has been restored. Monitoring has shown normal service operation, and validation efforts indicate that requests are being processed successfully. Our teams will continue to review the incident to better understand the contributing factors and help prevent similar issues in the future. This incident has been resolved.
Reported by Imperva on their status page.
resolvedAug 21 · 22:42 UTC
Monitoring has confirmed that the PoP is stable and operating normally. The incident has been resolved.
Reported by Imperva on their status page.
resolvedAug 20 · 11:16 UTC
The issue affecting connectivity through the QRO PoP has been resolved. Following confirmation of stable network conditions, traffic has been restored to the QRO PoP and the bypass has been removed. We have continued to monitor service following the restoration and are no longer observing any impact. This incident is now resolved. We thank you for your patience while we worked to restore normal operations.
Reported by Imperva on their status page.
resolvedAug 19 · 03:55 UTC
Technical team implemented the necessary fixes, completed validation activities, and confirmed service stability through continuous monitoring. All services are operating normally. PoP is fully operational and ready for service. We appreciate your patience and understanding throughout this incident.
Reported by Imperva on their status page.
resolvedAug 17 · 13:17 UTC
The issue affecting the YUL (Montreal, Canada) PoP has been resolved, and the PoP has been successfully returned to normal operation. Traffic is once again being served through the YUL PoP, and validation and monitoring have confirmed that services are operating as expected. We will continue to monitor the environment to ensure ongoing stability. Thank you for your patience while we worked to restore full service.
Reported by Imperva on their status page.
resolvedAug 13 · 10:14 UTC
The incident has been resolved and normal service levels have been restored for propagation of changes in the Imperva Management Portal. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.
Reported by Imperva on their status page.
