Linode Status: check for Linode outages and issues

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Linode.com

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Linode Manager and API

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Linode Hosted DNS Service

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Linode Longview

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Service Issue - All Services - US-EAST (Newark)

Started 27 Jul 2025 10:08:08 (2 days ago), still ongoing

Minor Incident

Monitoring

US-East (Newark)

US-East (Newark) Block Storage

US-East (Newark) NodeBalancers

US-East (Newark) Backups

US-East (Newark) Object Storage

More...

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.

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.

28 Jul 2025 16:42:22 (21 hours ago)

Identified: 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.

28 Jul 2025 14:51:46 (22 hours ago)

Identified: 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.

28 Jul 2025 10:50:58 (1 day ago)

Identified: 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.

28 Jul 2025 08:50:15 (1 day ago)

Identified: 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.

28 Jul 2025 05:16:56 (1 day ago)

Identified: 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.

28 Jul 2025 02:29:39 (1 day ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 23:54:44 (2 days ago)

Identified: 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.

27 Jul 2025 22:42:57 (2 days ago)

Identified: 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.

27 Jul 2025 21:36:13 (2 days ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 21:00:50 (2 days ago)

Identified: We are continuing to work on a fix for this issue.

27 Jul 2025 19:56:33 (2 days ago)

Identified: We are continuing to work on a fix for this issue.

27 Jul 2025 19:56:02 (2 days ago)

Identified: 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.

27 Jul 2025 19:16:35 (2 days ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 17:37:56 (2 days ago)

Identified: 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.

27 Jul 2025 16:16:11 (2 days ago)

Identified: 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.

27 Jul 2025 14:24:30 (2 days ago)

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.

27 Jul 2025 13:59:56 (2 days ago)

Investigating: 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.

27 Jul 2025 13:29:25 (2 days ago)

Investigating: 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.

27 Jul 2025 12:34:17 (2 days ago)

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.

27 Jul 2025 10:08:08 (2 days ago)

See all updates

Linode Managed Databases

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Linode Metadata Service

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Linode Regions

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-East (Newark)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Service Issue - All Services - US-EAST (Newark)

Started 27 Jul 2025 10:08:08 (2 days ago), still ongoing

Minor Incident

Monitoring

US-East (Newark)

US-East (Newark) Block Storage

US-East (Newark) NodeBalancers

US-East (Newark) Backups

US-East (Newark) Object Storage

More...

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.

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.

28 Jul 2025 16:42:22 (21 hours ago)

Identified: 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.

28 Jul 2025 14:51:46 (22 hours ago)

Identified: 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.

28 Jul 2025 10:50:58 (1 day ago)

Identified: 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.

28 Jul 2025 08:50:15 (1 day ago)

Identified: 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.

28 Jul 2025 05:16:56 (1 day ago)

Identified: 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.

28 Jul 2025 02:29:39 (1 day ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 23:54:44 (2 days ago)

Identified: 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.

27 Jul 2025 22:42:57 (2 days ago)

Identified: 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.

27 Jul 2025 21:36:13 (2 days ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 21:00:50 (2 days ago)

Identified: We are continuing to work on a fix for this issue.

27 Jul 2025 19:56:33 (2 days ago)

Identified: We are continuing to work on a fix for this issue.

27 Jul 2025 19:56:02 (2 days ago)

Identified: 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.

27 Jul 2025 19:16:35 (2 days ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 17:37:56 (2 days ago)

Identified: 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.

27 Jul 2025 16:16:11 (2 days ago)

Identified: 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.

27 Jul 2025 14:24:30 (2 days ago)

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.

27 Jul 2025 13:59:56 (2 days ago)

Investigating: 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.

27 Jul 2025 13:29:25 (2 days ago)

Investigating: 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.

27 Jul 2025 12:34:17 (2 days ago)

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.

27 Jul 2025 10:08:08 (2 days ago)

See all updates

US-Central (Dallas)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-West (Fremont)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-Southeast (Atlanta)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-IAD (Washington)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-ORD (Chicago)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

CA-Central (Toronto)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

EU-West (London)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

EU-Central (Frankfurt)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

FR-PAR (Paris)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AP-South (Singapore)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AP-Northeast-2 (Tokyo 2)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AP-West (Mumbai)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AP-Southeast (Sydney)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

SE-STO (Stockholm)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-SEA (Seattle)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

IT-MIL (Milan)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

JP-OSA (Osaka)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

IN-MAA (Chennai)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

ID-CGK (Jakarta)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

BR-GRU (São Paulo)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

NL-AMS (Amsterdam)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-MIA (Miami)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Connectivity Issue - US-MIA (Miami)

Started 19 Jul 2025 14:09:50 (10 days ago), still ongoing

Minor Incident

Monitoring

US-MIA (Miami)

Our team is investigating an issue affecting connectivity in our US-MIA (Miami) data center. During this time, users may experience intermittent connection timeouts and errors for all services deployed in this data center. We will share additional updates as we have more information.

See all updates

US-LAX (Los Angeles)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Service Issue - Object Storage (LAX)

Started 3 Mar 2025 19:04:58 (5 months ago), still ongoing

Minor Incident

Identified

US-LAX (Los Angeles)

Our team is investigating an issue affecting the Object Storage service in our LAX location. During this time, users may experience connection timeouts and errors with this service.

See all updates

ES-MAD (Madrid)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AU-MEL (Melbourne)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

GB-LON (London 2)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

IN-BOM-2 (Mumbai 2)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

SG-SIN-2 (Singapore 2)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

DE-FRA-2 (Frankfurt 2)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

JP-TYO-3 (Tokyo 3)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

ZA-JNB (Johannesburg)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

NZ-AKL (Auckland)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

CO-BOG (Bogota)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-DEN (Denver)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

DE-HAM (Hamburg)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-HOU (Houston)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

MY-KUL (Kuala Lumpur)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

FR-MRS (Marseille)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

MX-QRO (Queretaro)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

CL-SCL (Santiago)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Linode Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-East (Newark) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Service Issue - All Services - US-EAST (Newark)

Started 27 Jul 2025 10:08:08 (2 days ago), still ongoing

Minor Incident

Monitoring

US-East (Newark)

US-East (Newark) Block Storage

US-East (Newark) NodeBalancers

US-East (Newark) Backups

US-East (Newark) Object Storage

More...

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.

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.

28 Jul 2025 16:42:22 (21 hours ago)

Identified: 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.

28 Jul 2025 14:51:46 (22 hours ago)

Identified: 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.

28 Jul 2025 10:50:58 (1 day ago)

Identified: 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.

28 Jul 2025 08:50:15 (1 day ago)

Identified: 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.

28 Jul 2025 05:16:56 (1 day ago)

Identified: 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.

28 Jul 2025 02:29:39 (1 day ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 23:54:44 (2 days ago)

Identified: 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.

27 Jul 2025 22:42:57 (2 days ago)

Identified: 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.

27 Jul 2025 21:36:13 (2 days ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 21:00:50 (2 days ago)

Identified: We are continuing to work on a fix for this issue.

27 Jul 2025 19:56:33 (2 days ago)

Identified: We are continuing to work on a fix for this issue.

27 Jul 2025 19:56:02 (2 days ago)

Identified: 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.

27 Jul 2025 19:16:35 (2 days ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 17:37:56 (2 days ago)

Identified: 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.

27 Jul 2025 16:16:11 (2 days ago)

Identified: 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.

27 Jul 2025 14:24:30 (2 days ago)

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.

27 Jul 2025 13:59:56 (2 days ago)

Investigating: 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.

27 Jul 2025 13:29:25 (2 days ago)

Investigating: 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.

27 Jul 2025 12:34:17 (2 days ago)

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.

27 Jul 2025 10:08:08 (2 days ago)

See all updates

US-Central (Dallas) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-West (Fremont) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-Southeast (Atlanta) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-IAD (Washington) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-ORD (Chicago) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

CA-Central (Toronto) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

EU-West (London) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

EU-Central (Frankfurt) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

FR-PAR (Paris) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AP-South (Singapore) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AP-Northeast-2 (Tokyo 2) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AP-West (Mumbai) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AP-Southeast (Sydney) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

SE-STO (Stockholm) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-SEA (Seattle) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

JP-OSA (Osaka) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

IN-MAA (Chennai) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

BR-GRU (São Paulo) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

NL-AMS (Amsterdam) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

ES-MAD (Madrid) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

IT-MIL (Milan) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-MIA (Miami) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

ID-CGK (Jakarta) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-LAX (Los Angeles) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

GB-LON (London 2) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AU-MEL (Melbourne) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

IN-BOM-2 (Mumbai 2) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

DE-FRA-2 (Frankfurt 2) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

SG-SIN-2 (Singapore 2) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

JP-TYO-3 (Tokyo) Backups

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Linode Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-East (Newark) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Service Issue - All Services - US-EAST (Newark)

Started 27 Jul 2025 10:08:08 (2 days ago), still ongoing

Minor Incident

Monitoring

US-East (Newark)

US-East (Newark) Block Storage

US-East (Newark) NodeBalancers

US-East (Newark) Backups

US-East (Newark) Object Storage

More...

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.

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.

28 Jul 2025 16:42:22 (21 hours ago)

Identified: 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.

28 Jul 2025 14:51:46 (22 hours ago)

Identified: 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.

28 Jul 2025 10:50:58 (1 day ago)

Identified: 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.

28 Jul 2025 08:50:15 (1 day ago)

Identified: 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.

28 Jul 2025 05:16:56 (1 day ago)

Identified: 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.

28 Jul 2025 02:29:39 (1 day ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 23:54:44 (2 days ago)

Identified: 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.

27 Jul 2025 22:42:57 (2 days ago)

Identified: 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.

27 Jul 2025 21:36:13 (2 days ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 21:00:50 (2 days ago)

Identified: We are continuing to work on a fix for this issue.

27 Jul 2025 19:56:33 (2 days ago)

Identified: We are continuing to work on a fix for this issue.

27 Jul 2025 19:56:02 (2 days ago)

Identified: 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.

27 Jul 2025 19:16:35 (2 days ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 17:37:56 (2 days ago)

Identified: 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.

27 Jul 2025 16:16:11 (2 days ago)

Identified: 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.

27 Jul 2025 14:24:30 (2 days ago)

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.

27 Jul 2025 13:59:56 (2 days ago)

Investigating: 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.

27 Jul 2025 13:29:25 (2 days ago)

Investigating: 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.

27 Jul 2025 12:34:17 (2 days ago)

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.

27 Jul 2025 10:08:08 (2 days ago)

See all updates

US-Central (Dallas) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-West (Fremont) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-Southeast (Atlanta) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-IAD (Washington) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-ORD (Chicago) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

CA-Central (Toronto) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

EU-West (London) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

EU-Central (Frankfurt) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

FR-PAR (Paris) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AP-South (Singapore) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AP-Northeast-2 (Tokyo 2) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AP-West (Mumbai) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AP-Southeast (Sydney) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

SE-STO (Stockholm) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-SEA (Seattle) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

JP-OSA (Osaka) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

IN-MAA (Chennai) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

BR-GRU (São Paulo) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

NL-AMS (Amsterdam) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

ES-MAD (Madrid) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

IT-MIL (Milan) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-MIA (Miami) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

ID-CGK (Jakarta) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-LAX (Los Angeles) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

GB-LON (London 2) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AU-MEL (Melbourne) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

IN-BOM-2 (Mumbai 2) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

DE-FRA-2 (Frankfurt 2) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

SG-SIN-2 (Singapore 2) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

JP-TYO-3 (Tokyo 3) Block Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Linode NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-East (Newark) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Service Issue - All Services - US-EAST (Newark)

Started 27 Jul 2025 10:08:08 (2 days ago), still ongoing

Minor Incident

Monitoring

US-East (Newark)

US-East (Newark) Block Storage

US-East (Newark) NodeBalancers

US-East (Newark) Backups

US-East (Newark) Object Storage

More...

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.

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.

28 Jul 2025 16:42:22 (21 hours ago)

Identified: 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.

28 Jul 2025 14:51:46 (22 hours ago)

Identified: 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.

28 Jul 2025 10:50:58 (1 day ago)

Identified: 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.

28 Jul 2025 08:50:15 (1 day ago)

Identified: 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.

28 Jul 2025 05:16:56 (1 day ago)

Identified: 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.

28 Jul 2025 02:29:39 (1 day ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 23:54:44 (2 days ago)

Identified: 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.

27 Jul 2025 22:42:57 (2 days ago)

Identified: 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.

27 Jul 2025 21:36:13 (2 days ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 21:00:50 (2 days ago)

Identified: We are continuing to work on a fix for this issue.

27 Jul 2025 19:56:33 (2 days ago)

Identified: We are continuing to work on a fix for this issue.

27 Jul 2025 19:56:02 (2 days ago)

Identified: 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.

27 Jul 2025 19:16:35 (2 days ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 17:37:56 (2 days ago)

Identified: 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.

27 Jul 2025 16:16:11 (2 days ago)

Identified: 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.

27 Jul 2025 14:24:30 (2 days ago)

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.

27 Jul 2025 13:59:56 (2 days ago)

Investigating: 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.

27 Jul 2025 13:29:25 (2 days ago)

Investigating: 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.

27 Jul 2025 12:34:17 (2 days ago)

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.

27 Jul 2025 10:08:08 (2 days ago)

See all updates

US-Central (Dallas) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-West (Fremont) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-Southeast (Atlanta) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-IAD (Washington) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-ORD (Chicago) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

CA-Central (Toronto) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

EU-West (London) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

EU-Central (Frankfurt) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

FR-PAR (Paris) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AP-South (Singapore) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AP-Northeast-2 (Tokyo 2) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AP-West (Mumbai) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AP-Southeast (Sydney) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

SE-STO (Stockholm) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-SEA (Seattle) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

JP-OSA (Osaka) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

IN-MAA (Chennai) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

BR-GRU (São Paulo) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

NL-AMS (Amsterdam) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

ES-MAD (Madrid) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

IT-MIL (Milan) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-MIA (Miami) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

ID-CGK (Jakarta) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-LAX (Los Angeles) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

GB-LON (London 2) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AU-MEL (Melbourne) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

IN-BOM-2 (Mumbai 2) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

DE-FRA-2 (Frankfurt 2) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

SG-SIN-2 (Singapore 2) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

JP-TYO-3 (Tokyo 3) NodeBalancers

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Linode Object Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-East (Newark) Object Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Service Issue - All Services - US-EAST (Newark)

Started 27 Jul 2025 10:08:08 (2 days ago), still ongoing

Minor Incident

Monitoring

US-East (Newark)

US-East (Newark) Block Storage

US-East (Newark) NodeBalancers

US-East (Newark) Backups

US-East (Newark) Object Storage

More...

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.

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.

28 Jul 2025 16:42:22 (21 hours ago)

Identified: 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.

28 Jul 2025 14:51:46 (22 hours ago)

Identified: 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.

28 Jul 2025 10:50:58 (1 day ago)

Identified: 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.

28 Jul 2025 08:50:15 (1 day ago)

Identified: 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.

28 Jul 2025 05:16:56 (1 day ago)

Identified: 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.

28 Jul 2025 02:29:39 (1 day ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 23:54:44 (2 days ago)

Identified: 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.

27 Jul 2025 22:42:57 (2 days ago)

Identified: 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.

27 Jul 2025 21:36:13 (2 days ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 21:00:50 (2 days ago)

Identified: We are continuing to work on a fix for this issue.

27 Jul 2025 19:56:33 (2 days ago)

Identified: We are continuing to work on a fix for this issue.

27 Jul 2025 19:56:02 (2 days ago)

Identified: 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.

27 Jul 2025 19:16:35 (2 days ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 17:37:56 (2 days ago)

Identified: 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.

27 Jul 2025 16:16:11 (2 days ago)

Identified: 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.

27 Jul 2025 14:24:30 (2 days ago)

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.

27 Jul 2025 13:59:56 (2 days ago)

Investigating: 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.

27 Jul 2025 13:29:25 (2 days ago)

Investigating: 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.

27 Jul 2025 12:34:17 (2 days ago)

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.

27 Jul 2025 10:08:08 (2 days ago)

See all updates

US-Southeast (Atlanta) Object Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-IAD (Washington) Object Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-ORD (Chicago) Object Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Emerging Service Issue - Object Storage - Chicago

Started 24 Jul 2025 20:25:43 (5 days ago), resolved 24 Jul 2025 20:46:59 (5 days ago)

Minor Incident

Resolved

US-ORD (Chicago) Object Storage

Our team is investigating an emerging service issue affecting Object Storage in Chicago. We will share additional updates as we have more information.

See all updates

EU-Central (Frankfurt) Object Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AP-South (Singapore) Object Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AP-West (Mumbai)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

FR-PAR (Paris) Object Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

EU-West (London)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

SE-STO (Stockholm) Object Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-SEA (Seattle) Object Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

JP-OSA (Osaka) Object Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

IN-MAA (Chennai) Object Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

ID-CGK (Jakarta) Object Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

BR-GRU (Sao Paulo) Object Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

ES-MAD (Madrid) Object Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

GB-LON (London 2)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AU-MEL (Melbourne)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

NL-AMS (Amsterdam) Object Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

IT-MIL (Milan) Object Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-MIA (Miami) Object Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-LAX (Los Angeles) Object Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

GB-LON (London 2) Object Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AU-MEL (Melbourne) Object Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

IN-BOM-2 (Mumbai 2) Object Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

DE-FRA-2 (Frankfurt 2) Object Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

SG-SIN-2 (Singapore 2) Object Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

JP-TYO-3 (Tokyo 3) Object Storage

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-East (Newark) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Service Issue - All Services - US-EAST (Newark)

Started 27 Jul 2025 10:08:08 (2 days ago), still ongoing

Minor Incident

Monitoring

US-East (Newark)

US-East (Newark) Block Storage

US-East (Newark) NodeBalancers

US-East (Newark) Backups

US-East (Newark) Object Storage

More...

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.

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.

28 Jul 2025 16:42:22 (21 hours ago)

Identified: 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.

28 Jul 2025 14:51:46 (22 hours ago)

Identified: 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.

28 Jul 2025 10:50:58 (1 day ago)

Identified: 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.

28 Jul 2025 08:50:15 (1 day ago)

Identified: 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.

28 Jul 2025 05:16:56 (1 day ago)

Identified: 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.

28 Jul 2025 02:29:39 (1 day ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 23:54:44 (2 days ago)

Identified: 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.

27 Jul 2025 22:42:57 (2 days ago)

Identified: 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.

27 Jul 2025 21:36:13 (2 days ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 21:00:50 (2 days ago)

Identified: We are continuing to work on a fix for this issue.

27 Jul 2025 19:56:33 (2 days ago)

Identified: We are continuing to work on a fix for this issue.

27 Jul 2025 19:56:02 (2 days ago)

Identified: 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.

27 Jul 2025 19:16:35 (2 days ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 17:37:56 (2 days ago)

Identified: 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.

27 Jul 2025 16:16:11 (2 days ago)

Identified: 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.

27 Jul 2025 14:24:30 (2 days ago)

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.

27 Jul 2025 13:59:56 (2 days ago)

Investigating: 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.

27 Jul 2025 13:29:25 (2 days ago)

Investigating: 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.

27 Jul 2025 12:34:17 (2 days ago)

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.

27 Jul 2025 10:08:08 (2 days ago)

See all updates

US-Central (Dallas) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Service Issue - All Services - US-EAST (Newark)

Started 27 Jul 2025 10:08:08 (2 days ago), still ongoing

Minor Incident

Monitoring

US-East (Newark)

US-East (Newark) Block Storage

US-East (Newark) NodeBalancers

US-East (Newark) Backups

US-East (Newark) Object Storage

More...

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.

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.

28 Jul 2025 16:42:22 (21 hours ago)

Identified: 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.

28 Jul 2025 14:51:46 (22 hours ago)

Identified: 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.

28 Jul 2025 10:50:58 (1 day ago)

Identified: 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.

28 Jul 2025 08:50:15 (1 day ago)

Identified: 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.

28 Jul 2025 05:16:56 (1 day ago)

Identified: 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.

28 Jul 2025 02:29:39 (1 day ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 23:54:44 (2 days ago)

Identified: 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.

27 Jul 2025 22:42:57 (2 days ago)

Identified: 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.

27 Jul 2025 21:36:13 (2 days ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 21:00:50 (2 days ago)

Identified: We are continuing to work on a fix for this issue.

27 Jul 2025 19:56:33 (2 days ago)

Identified: We are continuing to work on a fix for this issue.

27 Jul 2025 19:56:02 (2 days ago)

Identified: 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.

27 Jul 2025 19:16:35 (2 days ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 17:37:56 (2 days ago)

Identified: 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.

27 Jul 2025 16:16:11 (2 days ago)

Identified: 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.

27 Jul 2025 14:24:30 (2 days ago)

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.

27 Jul 2025 13:59:56 (2 days ago)

Investigating: 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.

27 Jul 2025 13:29:25 (2 days ago)

Investigating: 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.

27 Jul 2025 12:34:17 (2 days ago)

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.

27 Jul 2025 10:08:08 (2 days ago)

See all updates

US-West (Fremont) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Service Issue - All Services - US-EAST (Newark)

Started 27 Jul 2025 10:08:08 (2 days ago), still ongoing

Minor Incident

Monitoring

US-East (Newark)

US-East (Newark) Block Storage

US-East (Newark) NodeBalancers

US-East (Newark) Backups

US-East (Newark) Object Storage

More...

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.

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.

28 Jul 2025 16:42:22 (21 hours ago)

Identified: 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.

28 Jul 2025 14:51:46 (22 hours ago)

Identified: 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.

28 Jul 2025 10:50:58 (1 day ago)

Identified: 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.

28 Jul 2025 08:50:15 (1 day ago)

Identified: 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.

28 Jul 2025 05:16:56 (1 day ago)

Identified: 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.

28 Jul 2025 02:29:39 (1 day ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 23:54:44 (2 days ago)

Identified: 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.

27 Jul 2025 22:42:57 (2 days ago)

Identified: 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.

27 Jul 2025 21:36:13 (2 days ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 21:00:50 (2 days ago)

Identified: We are continuing to work on a fix for this issue.

27 Jul 2025 19:56:33 (2 days ago)

Identified: We are continuing to work on a fix for this issue.

27 Jul 2025 19:56:02 (2 days ago)

Identified: 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.

27 Jul 2025 19:16:35 (2 days ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 17:37:56 (2 days ago)

Identified: 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.

27 Jul 2025 16:16:11 (2 days ago)

Identified: 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.

27 Jul 2025 14:24:30 (2 days ago)

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.

27 Jul 2025 13:59:56 (2 days ago)

Investigating: 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.

27 Jul 2025 13:29:25 (2 days ago)

Investigating: 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.

27 Jul 2025 12:34:17 (2 days ago)

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.

27 Jul 2025 10:08:08 (2 days ago)

See all updates

US-Southeast (Atlanta) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-IAD (Washington) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Service Issue - All Services - US-EAST (Newark)

Started 27 Jul 2025 10:08:08 (2 days ago), still ongoing

Minor Incident

Monitoring

US-East (Newark)

US-East (Newark) Block Storage

US-East (Newark) NodeBalancers

US-East (Newark) Backups

US-East (Newark) Object Storage

More...

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.

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.

28 Jul 2025 16:42:22 (21 hours ago)

Identified: 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.

28 Jul 2025 14:51:46 (22 hours ago)

Identified: 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.

28 Jul 2025 10:50:58 (1 day ago)

Identified: 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.

28 Jul 2025 08:50:15 (1 day ago)

Identified: 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.

28 Jul 2025 05:16:56 (1 day ago)

Identified: 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.

28 Jul 2025 02:29:39 (1 day ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 23:54:44 (2 days ago)

Identified: 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.

27 Jul 2025 22:42:57 (2 days ago)

Identified: 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.

27 Jul 2025 21:36:13 (2 days ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 21:00:50 (2 days ago)

Identified: We are continuing to work on a fix for this issue.

27 Jul 2025 19:56:33 (2 days ago)

Identified: We are continuing to work on a fix for this issue.

27 Jul 2025 19:56:02 (2 days ago)

Identified: 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.

27 Jul 2025 19:16:35 (2 days ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 17:37:56 (2 days ago)

Identified: 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.

27 Jul 2025 16:16:11 (2 days ago)

Identified: 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.

27 Jul 2025 14:24:30 (2 days ago)

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.

27 Jul 2025 13:59:56 (2 days ago)

Investigating: 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.

27 Jul 2025 13:29:25 (2 days ago)

Investigating: 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.

27 Jul 2025 12:34:17 (2 days ago)

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.

27 Jul 2025 10:08:08 (2 days ago)

See all updates

US-ORD (Chicago) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

CA-Central (Toronto) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Service Issue - All Services - US-EAST (Newark)

Started 27 Jul 2025 10:08:08 (2 days ago), still ongoing

Minor Incident

Monitoring

US-East (Newark)

US-East (Newark) Block Storage

US-East (Newark) NodeBalancers

US-East (Newark) Backups

US-East (Newark) Object Storage

More...

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.

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.

28 Jul 2025 16:42:22 (21 hours ago)

Identified: 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.

28 Jul 2025 14:51:46 (22 hours ago)

Identified: 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.

28 Jul 2025 10:50:58 (1 day ago)

Identified: 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.

28 Jul 2025 08:50:15 (1 day ago)

Identified: 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.

28 Jul 2025 05:16:56 (1 day ago)

Identified: 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.

28 Jul 2025 02:29:39 (1 day ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 23:54:44 (2 days ago)

Identified: 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.

27 Jul 2025 22:42:57 (2 days ago)

Identified: 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.

27 Jul 2025 21:36:13 (2 days ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 21:00:50 (2 days ago)

Identified: We are continuing to work on a fix for this issue.

27 Jul 2025 19:56:33 (2 days ago)

Identified: We are continuing to work on a fix for this issue.

27 Jul 2025 19:56:02 (2 days ago)

Identified: 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.

27 Jul 2025 19:16:35 (2 days ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 17:37:56 (2 days ago)

Identified: 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.

27 Jul 2025 16:16:11 (2 days ago)

Identified: 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.

27 Jul 2025 14:24:30 (2 days ago)

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.

27 Jul 2025 13:59:56 (2 days ago)

Investigating: 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.

27 Jul 2025 13:29:25 (2 days ago)

Investigating: 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.

27 Jul 2025 12:34:17 (2 days ago)

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.

27 Jul 2025 10:08:08 (2 days ago)

See all updates

EU-West (London) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

EU-Central (Frankfurt) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

FR-PAR (Paris) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AP-South (Singapore) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AP-Northeast-2 (Tokyo 2) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Service Issue - All Services - US-EAST (Newark)

Started 27 Jul 2025 10:08:08 (2 days ago), still ongoing

Minor Incident

Monitoring

US-East (Newark)

US-East (Newark) Block Storage

US-East (Newark) NodeBalancers

US-East (Newark) Backups

US-East (Newark) Object Storage

More...

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.

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.

28 Jul 2025 16:42:22 (21 hours ago)

Identified: 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.

28 Jul 2025 14:51:46 (22 hours ago)

Identified: 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.

28 Jul 2025 10:50:58 (1 day ago)

Identified: 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.

28 Jul 2025 08:50:15 (1 day ago)

Identified: 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.

28 Jul 2025 05:16:56 (1 day ago)

Identified: 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.

28 Jul 2025 02:29:39 (1 day ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 23:54:44 (2 days ago)

Identified: 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.

27 Jul 2025 22:42:57 (2 days ago)

Identified: 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.

27 Jul 2025 21:36:13 (2 days ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 21:00:50 (2 days ago)

Identified: We are continuing to work on a fix for this issue.

27 Jul 2025 19:56:33 (2 days ago)

Identified: We are continuing to work on a fix for this issue.

27 Jul 2025 19:56:02 (2 days ago)

Identified: 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.

27 Jul 2025 19:16:35 (2 days ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 17:37:56 (2 days ago)

Identified: 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.

27 Jul 2025 16:16:11 (2 days ago)

Identified: 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.

27 Jul 2025 14:24:30 (2 days ago)

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.

27 Jul 2025 13:59:56 (2 days ago)

Investigating: 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.

27 Jul 2025 13:29:25 (2 days ago)

Investigating: 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.

27 Jul 2025 12:34:17 (2 days ago)

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.

27 Jul 2025 10:08:08 (2 days ago)

See all updates

AP-West (Mumbai) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AP-Southeast (Sydney) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Service Issue - All Services - US-EAST (Newark)

Started 27 Jul 2025 10:08:08 (2 days ago), still ongoing

Minor Incident

Monitoring

US-East (Newark)

US-East (Newark) Block Storage

US-East (Newark) NodeBalancers

US-East (Newark) Backups

US-East (Newark) Object Storage

More...

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.

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.

28 Jul 2025 16:42:22 (21 hours ago)

Identified: 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.

28 Jul 2025 14:51:46 (22 hours ago)

Identified: 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.

28 Jul 2025 10:50:58 (1 day ago)

Identified: 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.

28 Jul 2025 08:50:15 (1 day ago)

Identified: 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.

28 Jul 2025 05:16:56 (1 day ago)

Identified: 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.

28 Jul 2025 02:29:39 (1 day ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 23:54:44 (2 days ago)

Identified: 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.

27 Jul 2025 22:42:57 (2 days ago)

Identified: 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.

27 Jul 2025 21:36:13 (2 days ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 21:00:50 (2 days ago)

Identified: We are continuing to work on a fix for this issue.

27 Jul 2025 19:56:33 (2 days ago)

Identified: We are continuing to work on a fix for this issue.

27 Jul 2025 19:56:02 (2 days ago)

Identified: 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.

27 Jul 2025 19:16:35 (2 days ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 17:37:56 (2 days ago)

Identified: 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.

27 Jul 2025 16:16:11 (2 days ago)

Identified: 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.

27 Jul 2025 14:24:30 (2 days ago)

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.

27 Jul 2025 13:59:56 (2 days ago)

Investigating: 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.

27 Jul 2025 13:29:25 (2 days ago)

Investigating: 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.

27 Jul 2025 12:34:17 (2 days ago)

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.

27 Jul 2025 10:08:08 (2 days ago)

See all updates

SE-STO (Stockholm) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-SEA (Seattle) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

JP-OSA (Osaka) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

IN-MAA (Chennai) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

ID-CGK (Jakarta) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

BR-GRU (São Paulo) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

NL-AMS (Amsterdam) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

ES-MAD (Madrid) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

IT-MIL (Milan) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-MIA (Miami) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-LAX (Los Angeles) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

GB-LON (London 2) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AU-MEL (Melbourne) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

IN-BOM-2 (Mumbai 2) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

DE-FRA-2 (Frankfurt 2) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

SG-SIN-2 (Singapore 2) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

JP-TYO-3 (Tokyo 3) Linode Kubernetes Engine

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Linode Metadata Service

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-East (Newark)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Service Issue - All Services - US-EAST (Newark)

Started 27 Jul 2025 10:08:08 (2 days ago), still ongoing

Minor Incident

Monitoring

US-East (Newark)

US-East (Newark) Block Storage

US-East (Newark) NodeBalancers

US-East (Newark) Backups

US-East (Newark) Object Storage

More...

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.

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.

28 Jul 2025 16:42:22 (21 hours ago)

Identified: 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.

28 Jul 2025 14:51:46 (22 hours ago)

Identified: 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.

28 Jul 2025 10:50:58 (1 day ago)

Identified: 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.

28 Jul 2025 08:50:15 (1 day ago)

Identified: 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.

28 Jul 2025 05:16:56 (1 day ago)

Identified: 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.

28 Jul 2025 02:29:39 (1 day ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 23:54:44 (2 days ago)

Identified: 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.

27 Jul 2025 22:42:57 (2 days ago)

Identified: 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.

27 Jul 2025 21:36:13 (2 days ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 21:00:50 (2 days ago)

Identified: We are continuing to work on a fix for this issue.

27 Jul 2025 19:56:33 (2 days ago)

Identified: We are continuing to work on a fix for this issue.

27 Jul 2025 19:56:02 (2 days ago)

Identified: 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.

27 Jul 2025 19:16:35 (2 days ago)

Identified: Our SMEs continue to work bringing our services back online, and we will provide an update as progress is made.

27 Jul 2025 17:37:56 (2 days ago)

Identified: 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.

27 Jul 2025 16:16:11 (2 days ago)

Identified: 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.

27 Jul 2025 14:24:30 (2 days ago)

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.

27 Jul 2025 13:59:56 (2 days ago)

Investigating: 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.

27 Jul 2025 13:29:25 (2 days ago)

Investigating: 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.

27 Jul 2025 12:34:17 (2 days ago)

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.

27 Jul 2025 10:08:08 (2 days ago)

See all updates

US-Central (Dallas)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-West (Fremont)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-Southeast (Atlanta)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-IAD (Washington)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-ORD (Chicago)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

CA-Central (Toronto)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

EU-West (London)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

EU-Central (Frankfurt)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

FR-PAR (Paris)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AP-South (Singapore)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AP-Northeast-2 (Tokyo 2)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AP-West (Mumbai)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AP-Southeast (Sydney)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

SE-STO (Stockholm)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-SEA (Seattle)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

IT-MIL (Milan)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

JP-OSA (Osaka)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

IN-MAA (Chennai)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

ID-CGK (Jakarta)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

BR-GRU (São Paulo)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

NL-AMS (Amsterdam)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-MIA (Miami)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-LAX (Los Angeles)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

ES-MAD (Madrid)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

AU-MEL (Melbourne)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

GB-LON (London 2)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

IN-BOM-2 (Mumbai 2)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

SG-SIN-2 (Singapore 2)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

DE-FRA-2 (Frankfurt 2)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

JP-TYO-3 (Tokyo 3)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

ZA-JNB (Johannesburg)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

NZ-AKL (Auckland)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

CO-BOG (Bogota)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-DEN (Denver)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

DE-HAM (Hamburg)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

US-HOU (Houston)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

MY-KUL (Kuala Lumpur)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

FR-MRS (Marseille)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

MX-QRO (Queretaro)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

CL-SCL (Santiago)

Tue 22

Wed 23

Thu 24

Fri 25

Sat 26

Sun 27

Mon 28

now

Linode Status

Real-time updates of Linode issues and outages

Linode status is Operational

Linode Longview

US-East (Newark)

US-MIA (Miami)

US-LAX (Los Angeles)

US-East (Newark) Backups

US-East (Newark) Block Storage

US-East (Newark) NodeBalancers

Active Incidents

Recently Resolved Incidents

Linode Outage Survival Guide

Linode Components

Linode

Linode.com

Linode Manager and API

Linode Hosted DNS Service

Linode Longview

Linode Managed Databases

Linode Metadata Service

Linode Regions

US-East (Newark)

US-Central (Dallas)

US-West (Fremont)

US-Southeast (Atlanta)

US-IAD (Washington)

US-ORD (Chicago)

CA-Central (Toronto)

EU-West (London)

EU-Central (Frankfurt)

FR-PAR (Paris)

AP-South (Singapore)

AP-Northeast-2 (Tokyo 2)

AP-West (Mumbai)

AP-Southeast (Sydney)

SE-STO (Stockholm)

US-SEA (Seattle)

IT-MIL (Milan)

JP-OSA (Osaka)

IN-MAA (Chennai)

ID-CGK (Jakarta)

BR-GRU (São Paulo)

NL-AMS (Amsterdam)

US-MIA (Miami)

US-LAX (Los Angeles)

ES-MAD (Madrid)

AU-MEL (Melbourne)

GB-LON (London 2)

IN-BOM-2 (Mumbai 2)

SG-SIN-2 (Singapore 2)

DE-FRA-2 (Frankfurt 2)

JP-TYO-3 (Tokyo 3)

ZA-JNB (Johannesburg)

NZ-AKL (Auckland)

CO-BOG (Bogota)

US-DEN (Denver)

DE-HAM (Hamburg)

US-HOU (Houston)

MY-KUL (Kuala Lumpur)

FR-MRS (Marseille)

MX-QRO (Queretaro)

CL-SCL (Santiago)

Linode Backups

US-East (Newark) Backups

US-Central (Dallas) Backups

US-West (Fremont) Backups

US-Southeast (Atlanta) Backups

US-IAD (Washington) Backups

US-ORD (Chicago) Backups

CA-Central (Toronto) Backups

EU-West (London) Backups

EU-Central (Frankfurt) Backups

FR-PAR (Paris) Backups

AP-South (Singapore) Backups

AP-Northeast-2 (Tokyo 2) Backups

AP-West (Mumbai) Backups

AP-Southeast (Sydney) Backups

SE-STO (Stockholm) Backups

US-SEA (Seattle) Backups