Current answer
Imperva experienced a minor incident: [INC-1148] Imperva Management API Degradation. ServiceAlert observed recovery on Oct 1, 2026.
Looking for an update now? Check the current status, or follow Imperva for future changes.
Incident Lifecycle
Affected Components
SIEM Logs
Incident Timeline
Monitoring
A fix has been implemented and we are monitoring the results.
Oct 1, 2026 at 11:40 AM UTC
Investigating
We have identified a service degradation affecting the Imperva API. As a result, some customers attempting to download SIEM logs via the API may receive HTTP 502 errors. Our teams are actively investigating the issue and working to restore normal service as quickly as possible.
All customer websites remain fully protected at this time. Technical teams are investigating. Further updates to follow.
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.
All customer websites remain fully protected at this time. Technical teams are investigating. Further updates to follow.
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.
Oct 1, 2026 at 11:27 AM UTC
Was your business affected by this Imperva outage?
Follow Imperva and route available status alerts to email or a team channel.