Monitoring
At this time we have been able to correct the issues affecting all services in our Newark, NJ (us-east) data center. This included Linode Kubernetes Engine (LKE), Linode compute instances, Block and Object Storage, and additional services. Some downstream impact was observed in other data centers due to interdependencies with Newark, and those services have also been fully restored. We will be monitoring this closely to ensure continued stability. If you continue to experience problems, please open a Support ticket for assistance.
Update
We are continuing to work on restoring full functionality to Linode Kubernetes Engine (LKE) and Linode compute instances in our Newark (us-east) data center. Our teams are actively engaged in recovery efforts and closely monitoring progress.
We appreciate your continued patience as we work to fully resolve this incident.
We appreciate your continued patience as we work to fully resolve this incident.
Update
Mitigation efforts are continuing with our subject matter experts actively working to restore the remaining services. We will continue to provide updates as progress is made.
Update
Mitigation efforts are continuing with our subject matter experts actively working to restore the remaining services. We will continue to provide updates as progress is made.
Update
Mitigation efforts are continuing with our subject matter experts actively working to restore the remaining services. We will continue to provide updates as progress is made.
Update
Our SMEs are working towards bringing up the remaining services online. The situation is improving. We will provide further updates as further progress is made.
Update
Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.
Update
Our SMEs continue to work bringing our services back online. We have been able to correct the issues impacting LKE in our Dallas, Fremont, Sydney, Tokyo 2, Toronto and Washington data centers. Issues impacting Block Storage, Object Storage, and Nodebalancers in Newark were also restored per previous updates . We are still working to mitigate impact to LKE and individual Linode instances in Newark and will provide updates as progress is made.
Update
At this time we have been able to correct the issues affecting Nodebalancer as of 19:00 UTC. We will be monitoring this to ensure that it remains stable.
Efforts to bring our services back continue, we will provide updates as progress is made.
Efforts to bring our services back continue, we will provide updates as progress is made.
Update
Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.
Update
We are continuing to work on a fix for this issue.
Update
We are continuing to work on a fix for this issue.
Update
At this time we have been able to correct the issues affecting LKE in our Dallas, Fremont, Sydney, Tokyo 2, Toronto and Washington data centers. Issues in Newark are still being worked at this moment.
We can also confirm Block Storage has recovered as of 14:13 UTC, as well as Object Storage at 17:52 UTC. We will be monitoring this to ensure that it remains stable.
Efforts to bring our services back continue, we will provide updates as progress is made.
We can also confirm Block Storage has recovered as of 14:13 UTC, as well as Object Storage at 17:52 UTC. We will be monitoring this to ensure that it remains stable.
Efforts to bring our services back continue, we will provide updates as progress is made.
Update
Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.
Update
In regards of the LKE impact caused in the identified data centers due to this issue, customers would have inability to provision new clusters and degraded ability to recover from control plane failures for already running clusters while this issue is active. Autoscaling of existing node pools is not impacted except for Newark data center. We continue to work bringing our services back online, and we will provide an update as soon as progress is made.
Update
Impact to LKE services has been confirmed to have also extended to our data centers in Dallas, Fremont, Sydney, Tokyo 2, Toronto and Washington due to the interaction with our data center in Newark. We continue to work bringing our services back online, and we will provide an update as soon as progress is made.
Identified
Our team has identified the issue affecting connectivity in our US-EAST (Newark) data center. The issue is related to heating/cooling complications in the data center due to a power outage . The power outage has been fixed and we are working quickly to bring our services back online, and we will provide an update as soon as the solution is in place.
Update
Our team continues investigating an issue affecting connectivity in our US-EAST (Newark) data center. During this time, users may experience unavailability issues for all services deployed in this data center. We will share additional updates as we have more information.
Update
Our team is investigating an issue affecting connectivity in our US-EAST (Newark) data center. During this time, users may experience unavailability issues for all services deployed in this data center. We will share additional updates as we have more information.
Investigating
Our team is investigating an emerging service issue affecting All Services in US-EAST (Newark). We will share additional updates as we have more information.
This incident affects: Regions (US-East (Newark)), Block Storage (US-East (Newark) Block Storage), NodeBalancers (US-East (Newark) NodeBalancers), Backups (US-East (Newark) Backups), Object Storage (US-East (Newark) Object Storage), Linode Kubernetes Engine (US-East (Newark) Linode Kubernetes Engine, US-Central (Dallas) Linode Kubernetes Engine, US-West (Fremont) Linode Kubernetes Engine, US-IAD (Washington) Linode Kubernetes Engine, CA-Central (Toronto) Linode Kubernetes Engine, AP-Northeast-2 (Tokyo 2) Linode Kubernetes Engine, AP-Southeast (Sydney) Linode Kubernetes Engine), Metadata Service (US-East (Newark)), and Longview.