- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Rio de Janeiro, Brazil (RIO)
- Regions
- latam
What to do
Check whether you use Imperva Rio de Janeiro, Brazil (RIO) in latam. 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 1d 1h it lasted.
Anything that failed between 2026-07-17 05:06 UTC and 2026-07-18 06:30 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 9
- identified
We have identified an issue in the Rio de Janeiro, Brazi data center. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place. 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
- identified
The team is continuing to work on resolving the issue. To maintain service availability, traffic is being rerouted through an alternate data center in the region. During this time, customers may experience increased latency while the reroute remains in effect. Next update on the issue will be shared no later than 6:35 UTC. 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
- identified
Our team is actively working to resolve the issue. To maintain service availability, traffic has been rerouted through an alternate data center in the region. Customers may experience increased latency while this temporary routing remains in place. Next update on the issue will be shared no later than 7:10 UTC. 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
- identified
Our team is actively investigating and working to resolve the issue. To maintain service availability, traffic has been temporarily rerouted through an alternate data center in the region. During this time, customers may experience increased latency. We will provide the next update no later than 7:45 UTC. 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
- identified
Our team has identified a hardware issue within the routing infrastructure and is actively working with the vendor to troubleshoot and resolve the issue. To maintain service availability, traffic continues to be temporarily rerouted through an alternate data center in the region. Customers may continue to experience increased latency while this temporary routing remains in place. Next update on the issue will be shared no later than 8:15 UTC. 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
- identified
We are actively working with Hardware vendor to resolve the issue. To maintain service availability, traffic is being rerouted through an alternate data center in the region. During this time, customers may experience increased latency while the reroute remains in effect. The next update can be expected around 16:00 UTC. 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
- identified
We have worked with the hardware vendor to address the underlying issue. Based on the current assessment and successful health checks, the team has scheduled the affected PoP to be reactivated at 03:00 UTC on 18 July 2026. To maintain service availability, traffic continues to be rerouted through an alternate data center in the region. During this time, customers may experience increased latency while the reroute remains in effect. The next update on this incident will be provided no later than 03:15 UTC on 18 July 2026.
provider
- monitoring
Technical team has successfully activated the PoP, and traffic has been restored to the Rio de Janeiro, Brazil (RIO) PoP. Verification testing and continuous monitoring are currently underway to validate stability and confirm the PoP is fully operational and ready for service. Next Status Update on this Incident will be provided no later than 6:03 UTC. 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
- resolved
The technical team has implemented the required fixes, completed validation activities, and confirmed service stability through continuous monitoring. All services are operating normally, and the PoP has been fully restored to normal operation. We appreciate your patience and understanding throughout this incident. 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
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-8042a1d6de
Is Imperva still down?
No, this incident was resolved 2026-07-18 06:30 UTC. For Imperva's live state, see https://down.guide/imperva.
How long did it last?
1d 1h, from 2026-07-17 05:06 UTC to 2026-07-18 06:30 UTC, by the times Imperva posted.
What was affected?
Imperva named Rio de Janeiro, Brazil (RIO) in latam.
What caused it?
Imperva hasn't published a root cause. If it does, it shows here.
Where does this come from?
Imperva's official status page, https://status.imperva.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.