[INC-1055] New York 2, NY (EWR) Data Center Issue

Update timeline

1. investigating May 29, 2026, 01:24 PM UTC

   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.

2. investigating May 29, 2026, 01:56 PM UTC

   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.

3. investigating May 29, 2026, 02:29 PM UTC

   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.

4. investigating May 29, 2026, 03:27 PM UTC

   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.

5. investigating May 29, 2026, 04:25 PM UTC

   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.

6. investigating May 29, 2026, 05:25 PM UTC

   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.

7. investigating May 29, 2026, 05:28 PM UTC

   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.

8. investigating May 29, 2026, 06:26 PM UTC

   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.

9. investigating May 29, 2026, 07:37 PM UTC

   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.

10. investigating May 29, 2026, 08:20 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 21:20 UTC.

11. investigating May 29, 2026, 09:34 PM UTC

    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.

12. identified May 29, 2026, 10:46 PM UTC

    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.

13. identified May 29, 2026, 11:41 PM UTC

    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.

14. identified May 30, 2026, 03:19 PM UTC

    The EWR PoP has remained stable during this monitoring period, and is currently scheduled for activation during the local off-peak period on 07-Jun-2026 04:00 UTC. Until that time, customer traffic will continue to be serviced by alternative PoPs.