- Level
- confirmed
- Worst impact
- Degraded
- Components
- Vancouver, Canada (VAN)
- Regions
- ca
- Down Index
- 27of 100
What to do
Check whether you use Imperva Vancouver, Canada (VAN) in ca. 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 15h 57m it lasted.
Anything that failed between 2026-05-28 19:08 UTC and 2026-05-29 11:05 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 7
- identified
We have identified connectivity issues affecting our Vancouver, Canada (VAN) data center. The next update will be provided no later than 19:38 UTC.
provider
- identified
We have identified connectivity issues in our Vancouver, Canada (VAN) data center. Traffic is being re-routed to an alternate data center. The next update will be provided no later than 19:54 UTC.
provider
- identified
We have identified intermittent connectivity issues affecting the Vancouver, Canada (VAN) data center. Our Network Engineering team is actively working on remediation efforts. In the meantime, network traffic has been redirected to an alternate regional data center. The next update will be provided no later than 20:24 UTC.
provider
- identified
As a precautionary measure, the Vancouver, Canada (VAN) data center will remain bypassed. Customer traffic continues to be served normally through an alternate PoP, and no customer action is required at this time. Engineering teams will continue investigating the issue, and additional updates will be provided as changes occur or once the PoP is restored to normal operation.
provider
- identified
The technical teams have identified an issue affecting the Vancouver, Canada (VAN) data center. As a precautionary measure, the PoP will remain bypassed to ensure service stability and is planned to be reactivated during off-peak hours. Customer traffic continues to be served normally through an alternate PoP. Engineering teams remain engaged in the investigation, and further updates will be shared as new information becomes available or once the PoP has been restored to normal operation.
provider
- monitoring
A fix has been implemented and traffic has been restored to the data center. We are continuing to monitor in order to ensure that service has returned to normal. The next update will be provided no later than 11:18 UTC.
provider
- resolved
Service in the data center has been restored to normal.
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-e14fc4105d
Is Imperva still down?
No, this incident was resolved 2026-05-29 11:05 UTC. For Imperva's live state, see https://down.guide/imperva.
How long did it last?
15h 57m, from 2026-05-28 19:08 UTC to 2026-05-29 11:05 UTC, by the times Imperva posted.
What was affected?
Imperva named Vancouver, Canada (VAN) in ca.
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.