- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Johannesburg, South Africa (QRA)
What to do
Check whether you use Imperva Johannesburg, South Africa (QRA). 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 9m it lasted.
Anything that failed between 2026-03-27 12:23 UTC and 2026-03-27 13:32 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 3
- investigating
Technical teams are investigating a potential issue in the Johannesburg, South Africa (QRA) data center. 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
- monitoring
A fix has been implemented, and the issue has been mitigated. We are continuing to monitor in order to ensure that service has returned to normal. 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
Some customer traffic being processed in Johannesburg, South Africa (QRA) PoP may have experienced higher than expected latency and packet loss due to an upstream provider issue, outside of the Thales Imperva Network. Engineers bypassed two impacted circuits in order to remove them from production, resulting in stabilized traffic. Services are now stable. Additional details will be provided following a completed root cause analysis.
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-d66dcc4aa3
Is Imperva still down?
No, this incident was resolved 2026-03-27 13:32 UTC. For Imperva's live state, see https://down.guide/imperva.
How long did it last?
1h 9m, from 2026-03-27 12:23 UTC to 2026-03-27 13:32 UTC, by the times Imperva posted.
What was affected?
Imperva named Johannesburg, South Africa (QRA).
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.