- Level
- confirmed
- Worst impact
- Partial outage
- Components
- New York 2, NY (EWR)
- Down Index
- 33of 100
What to do
Check whether you use Imperva New York 2, NY (EWR). 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 5d 13h it lasted.
Anything that failed between 2026-05-29 17:25 UTC and 2026-06-04 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 19
- investigating
We are investigating an issue in the New York 2, NY (EWR) 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 next update on the incident will be shared no later than 13:55 UTC.
provider
- investigating
We continue to investigate the issue affecting the data center. Traffic remains rerouted through an alternate data center in the region while troubleshooting efforts are ongoing. The next update on the incident will be shared no later than 14:25 UTC.
provider
- investigating
Investigation remains ongoing, with multiple technical teams actively engaged in troubleshooting and analysis efforts. Teams are also investigating a recent increase in anomalous traffic to determine whether it is contributing to the observed behavior. Traffic continues to be rerouted through an alternate data center in the region to minimize customer impact while the root cause is being identified. The next update on the incident will be shared no later than 15:28 UTC.
provider
- investigating
The investigation remains ongoing, with multiple technical teams actively engaged in troubleshooting. Customer traffic continues to be served through an alternate PoP in the region to minimize impact while investigation and mitigation efforts continue. The next update on the incident will be shared no later than 16:27 UTC.
provider
- investigating
The investigation remains ongoing, with multiple technical teams continuing to analyze the available data and evaluate potential contributing factors. Customer traffic continues to be served through alternate PoPs in the region to maintain service continuity while troubleshooting efforts and root cause analysis proceed. The next update on the incident will be shared no later than 17:25 UTC.
provider
- investigating
Investigation remains ongoing, with multiple technical teams continuing to analyze the available data and assess potential contributing factors. At this time, there are no significant changes to report, and troubleshooting efforts remain active. Customer traffic continues to be served through alternate PoPs in the region to help maintain service continuity while root cause and mitigation activities proceed. Technical teams are actively working to identify the underlying cause of the issue. Further updates will be provided as additional information becomes available. The next update on the incident will be shared no later than 18:25 UTC.
provider
- investigating
Investigation remains ongoing, with multiple technical teams continuing to analyze the available data and assess potential contributing factors. At this time, there are no significant changes to report, and troubleshooting efforts remain active. Customer traffic continues to be served through alternate PoPs in the region to help maintain service continuity while root cause and mitigation activities proceed. Technical teams are actively working to identify the underlying cause of the issue. Further updates will be provided as additional information becomes available. The next update on the incident will be shared no later than 18:25 UTC.
provider
- investigating
The investigation is still ongoing, with multiple technical teams actively reviewing available data and evaluating possible contributing factors. At this stage, there are no major developments to report, and troubleshooting activities continue. Customer traffic remains routed through alternate regional PoPs to maintain service continuity while mitigation efforts and root cause analysis are in progress. Next update will be shared no later then 19:26 UTC.
provider
- investigating
We are still investigating an issue affecting one of our points of presence (EWR), which may cause intermittent connectivity or latency. Traffic has been rerouted through alternate locations to maintain service continuity while our teams continue working toward resolution. Next update will be shared no later then 20:07 UTC.
provider
- investigating
Our Network Engineers continue to work on resolving the connectivity issues affecting the New York 2, NY (EWR) data center. The next update will be provided no later than 21:20 UTC.
provider
- investigating
Our Network Engineering teams remain actively engaged in investigating and mitigating the connectivity issues impacting the New York 2, NY (EWR) data center. The next update will be provided no later than 22:34 UTC.
provider
- identified
The technical teams have localized the problem and addressed it. The EWR PoP will remain bypassed until a scheduled maintenance window of 0400 to 0800 UTC on 1 June 2026. The next update will be provided following the reactivation of the EWR PoP.
provider
- identified
Technical teams have identified and remediated the underlying issue. As a precautionary measure, the EWR PoP will remain bypassed while monitoring continues. An estimated timeline for reactivation will be provided shortly.
provider
- identified
The EWR PoP has remained stable during this monitoring period, and is currently scheduled for activation during the local off-peak period on 04-Jun-2026 04:00 UTC. Until that time, customer traffic will continue to be serviced by alternative PoPs.
provider
- identified
The EWR PoP has remained stable during this monitoring period, and is currently scheduled for activation during the local off-peak period on 04-Jun-2026 04:00 UTC. Until that time, customer traffic will continue to be serviced by alternative PoPs.
provider
- identified
A fix has been implemented, and traffic has been restored to the data center. We are continuing to monitor to ensure that service has returned to normal. The next update will be provided no later than 05:01 UTC.
provider
- monitoring
Technical team has successfully activated the PoP, and traffic has been restored to the EWR data center. Verification testing and continuous monitoring are currently underway to validate stability and confirm the PoP is fully operational and ready for service. The next Status Update on this Incident will be provided no later than 06:01 UTC.
provider
- monitoring
The technical team identified and resolved an unexpected issue affecting range advertisements. Continuous monitoring is underway to validate service stability and will confirm full operational readiness of the PoP. The PoP is now active, and traffic has been restored to the EWR data center. The next Status Update on this Incident will be provided no later than 06:31 UTC.
provider
- resolved
The technical team implemented the necessary fixes, completed validation activities, and confirmed service stability through continuous monitoring. All services are operating normally. The PoP is fully operational and ready for service. We appreciate your patience and understanding throughout this incident.
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-fc8f78c311
Is Imperva still down?
No, this incident was resolved 2026-06-04 06:30 UTC. For Imperva's live state, see https://down.guide/imperva.
How long did it last?
5d 13h, from 2026-05-29 17:25 UTC to 2026-06-04 06:30 UTC, by the times Imperva posted.
What was affected?
Imperva named New York 2, NY (EWR).
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.