Connectivity Issue - Newark
Incident
Report for Linode
Postmortem
On February 24, 2023, at 05:12 UTC, configuration changes to networking hardware in the Newark data center triggered a routing failure. The routing failure impacted a subset of hosts, and delayed any commands issued through the Cloud Manager or the Linode API until connectivity was restored. At 05:42 UTC connectivity between the legacy network and API was restored, and we considered this incident resolved as of 08:59 UTC.
Upon review of this incident, the issue was related to a human error when making the configuration changes as we retire the legacy network. We plan to review and refine our change management policies to ensure such a human error does not occur in the future.
Resolved
The connectivity issue for our Newark data center has been resolved.
Monitoring
At this time we have been able to correct the issues affecting connectivity in our Newark data center. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues with creating or modifying services in Newark, please open a Support ticket for assistance.
Identified
Our team has identified the issue affecting connectivity in our Newark data center. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Investigating
Our team is investigating an issue affecting connectivity in our Newark data center. During this time, users may experience problems issuing jobs to all services deployed in this data center. We will share additional updates as we have more information.
This incident affected: Regions (US-East (Newark)).