[INC -1026] Issue in FP on browser classification

What to do

• Check whether you use Imperva Cloud WAF Protection. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1h 36m it lasted.

  Anything that failed between 2026-05-08 19:37 UTC and 2026-05-08 21:13 UTC may need a replay.

• Subscribe to Imperva's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=imperva works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Imperva 5

1. identifiedMay 8, 2026, 7:37 PM UTC

   We have discovered a potential issue affecting FP on browser classification. 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.

   provider

2. identifiedMay 8, 2026, 7:42 PM UTC

   The issue has been identified and a fix is being implemented. The next Status Update on this Incident will be provided no later than 20:10 UTC. 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.

   provider

3. identifiedMay 8, 2026, 8:16 PM UTC

   The issue has been identified, and remediation efforts are currently underway. The next Status Update on this Incident will be provided no later than 20:45 UTC. 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.

   provider

4. monitoringMay 8, 2026, 9:01 PM UTC

   A fix has been implemented and we are monitoring the results. The next Status Update on this Incident will be provided no later than 21:30 UTC. 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.

   provider

5. resolvedMay 8, 2026, 9:13 PM UTC

   The incident has been successfully resolved, and all services are operating normally. 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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.