[INC-1053] Connectivity issue in EWR

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 17h 52m it lasted.

  Anything that failed between 2026-05-28 18:09 UTC and 2026-05-29 12:01 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 13

1. identifiedMay 28, 2026, 6:09 PM UTC

   We have identified connectivity issues in our New York 2, NY (EWR). traffic is being re-routed to an alternate data-center. Next update will be shared no later then 18:37.

   provider

2. identifiedMay 28, 2026, 6:23 PM UTC

   We have identified connectivity issues affecting our New York 2, NY (EWR) data center. Traffic is currently being re-routed to an alternate data center to minimize customer impact. The next update will be provided no later than 18:53 UTC.

   provider

3. identifiedMay 28, 2026, 6:57 PM UTC

   We have identified intermittent connectivity issues affecting the New York 2, NY (EWR) 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 19:27 UTC.

   provider

4. identifiedMay 28, 2026, 7:30 PM UTC

   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 20:00 UTC.

   provider

5. identifiedMay 28, 2026, 8:17 PM UTC

   As a precautionary measure, the New York 2, NY (EWR) 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

6. identifiedMay 28, 2026, 9:54 PM UTC

   The technical teams have identified an issue affecting the New York 2, NY (EWR) 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

7. monitoringMay 29, 2026, 7:25 AM UTC

   A fix has been implemented, and customer traffic continues to be served normally through the New York 2, NY (EWR) PoP. We will continue to monitor the situation to ensure that service remains 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

8. investigatingMay 29, 2026, 8:41 AM UTC

   During monitoring, the team identified some abnormalities in the network. The engineering team is currently re-investigating the issue, and traffic is being re-routed to an alternate data center. Next update will be shared no later then 09:11 UTC.

   provider

9. investigatingMay 29, 2026, 9:12 AM UTC

   The investigation is ongoing, and technical teams continue to actively troubleshoot and analyze the issue to determine the underlying cause. Next update will be shared no later then 09:42 UTC.

   provider

10. investigatingMay 29, 2026, 9:48 AM UTC

    Investigation is ongoing. Technical teams continue to analyze the issue and validate findings. Customer traffic continues to be served normally through an alternate PoP. Next update will be shared no later then 10:18 UTC.

    provider

11. identifiedMay 29, 2026, 10:16 AM UTC

    The issue has been identified, and technical teams are actively working on remediation. Customer traffic continues to be served normally through an alternate PoP. The next update will be provided no later than 10:46 UTC.

    provider

12. monitoringMay 29, 2026, 10:57 AM UTC

    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 12:00 UTC.

    provider

13. resolvedMay 29, 2026, 12:01 PM UTC

    Service in the data center has been restored to normal.

    provider

Corrections

None so far.

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