Linode Outage History

Linode is up right now

Linode had 83 outages in the last 2 years totaling 530h 11m of downtime — averaging 3.4 incidents per month.

There were 83 Linode outages since November 8, 2025 totaling 530h 11m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.linode.com

Notice July 28, 2026

Service Issue - Host Job Performance Degradation - Several Regions

Detected by Pingoru
Jul 28, 2026, 06:14 PM UTC
Resolved
Jul 29, 2026, 12:27 PM UTC
Duration
18h 13m
Affected: US-East (Newark) Block StorageUS-Central (Dallas) Block StorageUS-West (Fremont) Block StorageUS-Southeast (Atlanta) Block StorageUS-IAD (Washington) Block StorageUS-ORD (Chicago) Block StorageCA-Central (Toronto) Block StorageEU-West (London) Block StorageEU-Central (Frankfurt) Block StorageFR-PAR (Paris) Block StorageAP-South (Singapore) Block StorageAP-Northeast-2 (Tokyo 2) Block StorageAP-West (Mumbai) Block StorageAP-Southeast (Sydney) Block StorageSE-STO (Stockholm) Block StorageUS-SEA (Seattle) Block StorageJP-OSA (Osaka) Block StorageIN-MAA (Chennai) Block StorageBR-GRU (São Paulo) Block StorageNL-AMS (Amsterdam) Block StorageES-MAD (Madrid) Block StorageIT-MIL (Milan) Block StorageUS-MIA (Miami) Block StorageID-CGK (Jakarta) Block StorageUS-LAX (Los Angeles) Block StorageGB-LON (London 2) Block StorageAU-MEL (Melbourne) Block StorageIN-BOM-2 (Mumbai 2) Block StorageDE-FRA-2 (Frankfurt 2) Block StorageSG-SIN-2 (Singapore 2) Block StorageJP-TYO-3 (Tokyo 3) Block Storage
Timeline · 6 updates

Read the full incident report →

Minor July 18, 2026

Service Issue - Object Storage

Detected by Pingoru
Jul 18, 2026, 03:34 AM UTC
Resolved
Jul 18, 2026, 04:36 AM UTC
Duration
1h 1m
Affected: US-IAD (Washington) Object StorageUS-ORD (Chicago) Object StorageFR-PAR (Paris) Object StorageUS-SEA (Seattle) Object StorageUS-LAX (Los Angeles) Object Storage
Timeline · 4 updates

Read the full incident report →

Notice July 16, 2026

Connectivity Issue - US-MIA (Miami

Detected by Pingoru
Jul 16, 2026, 01:24 AM UTC
Resolved
Jul 16, 2026, 01:24 AM UTC
Duration
—
Affected: US-MIA (Miami)
Timeline · 1 update
  1. resolved Jul 16, 2026, 01:24 AM UTC

    Our team investigated an issue that affected connectivity in our US-MIA (Miami) data center between 21:20 UTC and approximately 23:28 UTC on July 15, 2026. During this window, users may have experienced degraded networking performance and packet loss for Compute services deployed in this region. The issue was resolved after we implemented a fix. We are continuing to work with our third-party service provider to confirm the root cause, as initial evidence points to a campus cross-connect (dark fiber) outage on their infrastructure.

Read the full incident report →

Minor July 14, 2026

Service Issue - Linode API/CLI

Detected by Pingoru
Jul 14, 2026, 12:21 PM UTC
Resolved
Jul 14, 2026, 07:26 PM UTC
Duration
7h 5m
Affected: US-East (Newark)Cloud Manager and APIUS-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)FR-PAR-2 (Paris 2)US-IAD-2 (Washington 2)
Timeline · 7 updates

Read the full incident report →

Notice July 13, 2026

Service Issue - Host Jobs - All Regions

Detected by Pingoru
Jul 13, 2026, 06:29 PM UTC
Resolved
Jul 13, 2026, 07:54 PM UTC
Duration
1h 24m
Timeline · 2 updates
  1. identified Jul 13, 2026, 06:29 PM UTC

    Our team has identified an emerging service issue affecting host jobs for some hosts across all regions. Linode connectivity is *not impacted*, but some host-level jobs, such as backups or attempts to power on or off your services may be delayed. We will share additional updates as we have more information.

  2. resolved Jul 13, 2026, 07:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 9, 2026

Emerging Service Issue - Cloud Manager

Detected by Pingoru
Jul 09, 2026, 04:57 PM UTC
Resolved
Jul 09, 2026, 06:21 PM UTC
Duration
1h 23m
Affected: Cloud Manager and API
Timeline · 5 updates
  1. investigating Jul 09, 2026, 04:57 PM UTC

    Our team is investigating an emerging service issue affecting Cloud Manager logins. We will share additional updates as we have more information.

  2. investigating Jul 09, 2026, 05:24 PM UTC

    We are continuing to investigate this issue. We will provide an update within the next 30 minutes.

  3. monitoring Jul 09, 2026, 05:49 PM UTC

    At this time we have been able to correct the issue affecting the Cloud Manager logins. We will be monitoring this to ensure that the service remains stable. If you are still experiencing issues and unable to open a Support ticket, please call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected].

  4. resolved Jul 09, 2026, 06:21 PM UTC

    We haven't observed any additional issues with the Cloud Manager logins and will now consider this incident resolved. If you continue to experience issues, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected] for assistance.

  5. postmortem Jul 10, 2026, 12:30 PM UTC

    On July 9, 2026, at 15:43 UTC, customers were unable to login to [cloud.linode.com](http://cloud.linode.com) using username and password. Customers were getting "wrong password" error message. Investigation revealed that the issue was due to an internal certificate issue. To mitigate the impact, we fixed the certificate issue on the impacted servers at 17:24 UTC on July 9, 2026. After monitoring our systems for some time, we confirmed the issue was fully resolved. Akamai will deploy a permanent fix to prevent a recurrence of the issue.

Read the full incident report →

Notice July 6, 2026

Emerging Service Issue - Managed Databases - All Regions

Detected by Pingoru
Jul 06, 2026, 06:04 PM UTC
Resolved
Jul 07, 2026, 03:31 PM UTC
Duration
21h 27m
Affected: US-East (Newark)US-Central (Dallas)US-West (Fremont)US-Southeast (Atlanta)Managed DatabasesUS-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)FR-PAR-2 (Paris 2)US-IAD-2 (Washington 2)
Timeline · 2 updates
  1. investigating Jul 06, 2026, 06:04 PM UTC

    Our team is investigating an emerging service issue affecting Managed Databases across all regions. Customers may experience latency when provisioning new databases or deleting existing ones. There is no observed impact to the performance or availability of active, running databases at this time. We will provide updates as more information becomes available.

  2. resolved Jul 07, 2026, 03:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 1, 2026

Service Issue - Linode Automated Networking

Detected by Pingoru
Jul 01, 2026, 05:21 PM UTC
Resolved
Jul 01, 2026, 06:28 PM UTC
Duration
1h 6m
Affected: Cloud Manager and API
Timeline · 3 updates
  1. identified Jul 01, 2026, 05:21 PM UTC

    Our team is investigating a service issue that affects the auto configuration of networking on Linodes by Network Helper to fail. During that time, some users may have Linodes provision but appear to have no connectivity. This also can impact Linodes created by the Linode Kubernetes Engine and impact autoscaling or provisioning of clusters. Customers can still manually configure networking via the LISH console to mitigate this issue. Please see our guide on manual network configuration on a Compute Instance. We will share additional updates as we have more information.

  2. monitoring Jul 01, 2026, 06:09 PM UTC

    A fix has been implemented to resolve the automated network configuration issue on Linodes using Network Helper. We recommend rebooting your Linode to restore full network functionality. We are actively monitoring the results to ensure continued stability.

  3. resolved Jul 01, 2026, 06:28 PM UTC

    We haven’t observed any additional issues with the Linode Automated Networking service, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Read the full incident report →

Minor June 26, 2026

Service Issue - ACLP Metrics

Detected by Pingoru
Jun 26, 2026, 05:35 PM UTC
Resolved
Jul 08, 2026, 12:26 PM UTC
Duration
11d 18h
Affected: Akamai Cloud Pulse (ACLP) - Metrics
Timeline · 7 updates
  1. investigating Jun 26, 2026, 05:35 PM UTC

    Our team is investigating an issue affecting the Cloud Pulse Logs (ACLP Logs). The issue appears to be intermittent. We will share additional updates as we have more information.

  2. investigating Jun 26, 2026, 06:19 PM UTC

    We are continuing to investigate this issue. We will share additional updates as we have more information.

  3. investigating Jun 26, 2026, 07:08 PM UTC

    We are continuing to investigate this issue. We will provide further updates as we have more information.

  4. investigating Jun 26, 2026, 08:04 PM UTC

    We are continuing to investigate this issue.

  5. monitoring Jun 26, 2026, 09:13 PM UTC

    We have not observed a recurrence of the issue affecting the Cloud Pulse Metrics (ACLP Metrics) for several hours. Our team will continue to monitor the service closely while we investigate the underlying cause. If you continue to experience problems, please open a Support ticket for assistance.

  6. monitoring Jun 30, 2026, 12:02 AM UTC

    We are continuing to monitor for any further issues.

  7. resolved Jul 08, 2026, 12:26 PM UTC

    We haven’t observed any additional issues with the Cloud Pulse Metrics (ACLP Metrics) service, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Read the full incident report →

Notice June 26, 2026

Connectivity Issue - US-IAD

Detected by Pingoru
Jun 26, 2026, 05:14 PM UTC
Resolved
Jun 26, 2026, 07:33 PM UTC
Duration
2h 18m
Affected: US-IAD (Washington)
Timeline · 2 updates
  1. investigating Jun 26, 2026, 05:14 PM UTC

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

  2. resolved Jun 26, 2026, 07:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 25, 2026

Emerging Service Issue - Migrations

Detected by Pingoru
Jun 25, 2026, 02:33 PM UTC
Resolved
Jun 25, 2026, 06:42 PM UTC
Duration
4h 8m
Affected: 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)FR-PAR-2 (Paris 2)US-IAD-2 (Washington 2)
Timeline · 3 updates
  1. investigating Jun 25, 2026, 02:33 PM UTC

    Our team is investigating an emerging service issue affecting migrations and resizes in all regions. At this time, Linode migrations and plan resizes may be delayed. We will share additional updates as we have more information.

  2. monitoring Jun 25, 2026, 02:50 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jun 25, 2026, 06:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 24, 2026

Emerging Service Issue - GPU Instances - All Regions

Detected by Pingoru
Jun 24, 2026, 06:53 PM UTC
Resolved
Jun 25, 2026, 07:29 PM UTC
Duration
1d
Affected: 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)FR-PAR-2 (Paris 2)US-IAD-2 (Washington 2)
Timeline · 5 updates

Read the full incident report →

Notice June 16, 2026

Emerging Service Issue - Linode Migrations

Detected by Pingoru
Jun 16, 2026, 03:44 AM UTC
Resolved
Jun 16, 2026, 06:06 AM UTC
Duration
2h 22m
Timeline · 3 updates
  1. identified Jun 16, 2026, 03:44 AM UTC

    Our team is investigating an emerging service issue affecting Linode Migrations in all regions. Migrations might be slow or pending for long time. We will share additional updates as we have more information.

  2. monitoring Jun 16, 2026, 05:14 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jun 16, 2026, 06:06 AM UTC

    The issue affecting Linode Migrations has been resolved. Resize and Migration operations should be operating as normal now.

Read the full incident report →

Notice June 5, 2026

Emerging Service Issue - LKE Enterprise - All Regions

Detected by Pingoru
Jun 05, 2026, 02:23 PM UTC
Resolved
Jun 05, 2026, 02:58 PM UTC
Duration
35m
Affected: US-East (Newark) Linode Kubernetes EngineUS-Central (Dallas) Linode Kubernetes EngineUS-West (Fremont) Linode Kubernetes EngineUS-Southeast (Atlanta) Linode Kubernetes EngineUS-IAD (Washington) Linode Kubernetes EngineUS-ORD (Chicago) Linode Kubernetes EngineCA-Central (Toronto) Linode Kubernetes EngineEU-West (London) Linode Kubernetes EngineEU-Central (Frankfurt) Linode Kubernetes EngineFR-PAR (Paris) Linode Kubernetes EngineAP-South (Singapore) Linode Kubernetes EngineAP-Northeast (Tokyo 2) Linode Kubernetes EngineAP-West (Mumbai) Linode Kubernetes EngineAP-Southeast (Sydney) Linode Kubernetes EngineSE-STO (Stockholm) Linode Kubernetes EngineUS-SEA (Seattle) Linode Kubernetes EngineJP-OSA (Osaka) Linode Kubernetes EngineIN-MAA (Chennai) Linode Kubernetes EngineID-CGK (Jakarta) Linode Kubernetes EngineBR-GRU (São Paulo) Linode Kubernetes EngineNL-AMS (Amsterdam) Linode Kubernetes EngineES-MAD (Madrid) Linode Kubernetes EngineIT-MIL (Milan) Linode Kubernetes EngineUS-MIA (Miami) Linode Kubernetes EngineUS-LAX (Los Angeles) Linode Kubernetes EngineGB-LON (London 2) Linode Kubernetes EngineAU-MEL (Melbourne) Linode Kubernetes EngineIN-BOM-2 (Mumbai 2) Linode Kubernetes EngineDE-FRA-2 (Frankfurt 2) Linode Kubernetes EngineSG-SIN-2 (Singapore 2) Linode Kubernetes EngineJP-TYO-3 (Tokyo 3) Linode Kubernetes Engine
Timeline · 2 updates
  1. investigating Jun 05, 2026, 02:23 PM UTC

    We are currently investigating an emerging service issue affecting LKE Enterprise clusters across all regions. During this time, users may experience failures when deploying new clusters or upgrading existing ones. Our team is working to resolve this, and we will provide updates here as they become available.

  2. resolved Jun 05, 2026, 02:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 3, 2026

Emerging Service Issue - Support Phone Line

Detected by Pingoru
Jun 03, 2026, 02:22 PM UTC
Resolved
Jun 04, 2026, 03:51 PM UTC
Duration
1d 1h
Timeline · 3 updates
  1. investigating Jun 03, 2026, 02:22 PM UTC

    Our team is investigating an upstream emerging service issue affecting our Support phone line due to problems with an upstream provider. We will share additional updates as we have more information. If you are having difficulty reaching us over the phone during this time, please reach us through a ticket.

  2. investigating Jun 03, 2026, 06:33 PM UTC

    Our team is continuing to investigate an upstream service issue affecting our Support phone line. While stability of the service has improved, we have not yet identified the cause of the issue. We will share additional updates as we have more information. If you are having difficulty reaching us over the phone during this time, please open a Support ticket from the Cloud Manager.

  3. resolved Jun 04, 2026, 03:51 PM UTC

    The upstream issue has been resolved, and our Support phone line should now be fully functional again.

Read the full incident report →

Minor June 3, 2026

Service Issue - Block Storage Newark, US

Detected by Pingoru
Jun 03, 2026, 08:58 AM UTC
Resolved
Jun 04, 2026, 09:11 AM UTC
Duration
1d
Affected: US-East (Newark) Block Storage
Timeline · 7 updates
  1. investigating Jun 03, 2026, 08:58 AM UTC

    Our team is investigating an issue affecting the Block Storage service in our Newark, US data center. During this time, users may experience connection timeouts, latency and errors with this service. We will share additional updates as we have more information.

  2. investigating Jun 03, 2026, 10:53 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Jun 03, 2026, 11:25 AM UTC

    At this time we have been able to correct the issues affecting the Block Storage service. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.

  4. investigating Jun 03, 2026, 12:55 PM UTC

    Our team is investigating an issue affecting the Block Storage service in our Newark, US data center. During this time, users may experience connection timeouts, latency and errors with this service. We will share additional updates as we have more information.

  5. monitoring Jun 03, 2026, 03:44 PM UTC

    At this time we have been able to correct the issues affecting the Block Storage service. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.

  6. resolved Jun 04, 2026, 09:11 AM UTC

    We haven’t observed any additional issues with the Block Storage service in Newark, US, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

  7. postmortem Jun 04, 2026, 12:55 PM UTC

    Between 22:50 UTC on June 2, 2026 and 19:00 UTC on June 3, 2026, some customers experienced intermittent performance degradation and long access times when interacting with the Compute Block Storage cluster in Newark, US. During this period, intermittent component instability triggered intensive background recovery operations. This elevated system load resulted in a temporary degradation of data redundancy, higher read/write latency, and reduced throughput for the affected volumes. To mitigate the impact, Akamai successfully restored the affected storage drives to operation, stabilizing the cluster and eliminating active customer impact. Following this, additional actions aim to fully restore standard system redundancy. This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.

Read the full incident report →

Notice May 16, 2026

Service Issue - [Linodes and Linode Kubernetes Engine (LKE)] - [All Regions]

Detected by Pingoru
May 16, 2026, 12:42 AM UTC
Resolved
May 16, 2026, 01:43 AM UTC
Duration
1h 1m
Affected: US-East (Newark)US-East (Newark) Linode Kubernetes EngineUS-Central (Dallas)US-Central (Dallas) Linode Kubernetes EngineUS-West (Fremont)US-West (Fremont) Linode Kubernetes EngineUS-Southeast (Atlanta)US-Southeast (Atlanta) Linode Kubernetes EngineUS-IAD (Washington)US-IAD (Washington) Linode Kubernetes EngineUS-ORD (Chicago)US-ORD (Chicago) Linode Kubernetes EngineCA-Central (Toronto)CA-Central (Toronto) Linode Kubernetes EngineEU-West (London)EU-West (London) Linode Kubernetes EngineEU-Central (Frankfurt)EU-Central (Frankfurt) Linode Kubernetes EngineFR-PAR (Paris)FR-PAR (Paris) Linode Kubernetes EngineAP-South (Singapore)AP-South (Singapore) Linode Kubernetes EngineAP-Northeast-2 (Tokyo 2)AP-Northeast (Tokyo 2) Linode Kubernetes EngineAP-West (Mumbai)AP-West (Mumbai) Linode Kubernetes EngineAP-Southeast (Sydney)AP-Southeast (Sydney) Linode Kubernetes EngineSE-STO (Stockholm)SE-STO (Stockholm) Linode Kubernetes EngineUS-SEA (Seattle)US-SEA (Seattle) Linode Kubernetes EngineIT-MIL (Milan)JP-OSA (Osaka) Linode Kubernetes EngineJP-OSA (Osaka)IN-MAA (Chennai) Linode Kubernetes EngineIN-MAA (Chennai)ID-CGK (Jakarta) Linode Kubernetes EngineID-CGK (Jakarta)BR-GRU (São Paulo) Linode Kubernetes EngineBR-GRU (São Paulo)NL-AMS (Amsterdam) Linode Kubernetes EngineNL-AMS (Amsterdam)ES-MAD (Madrid) Linode Kubernetes EngineUS-MIA (Miami)IT-MIL (Milan) Linode Kubernetes EngineUS-LAX (Los Angeles)US-MIA (Miami) Linode Kubernetes EngineES-MAD (Madrid)US-LAX (Los Angeles) Linode Kubernetes EngineAU-MEL (Melbourne)GB-LON (London 2) Linode Kubernetes EngineGB-LON (London 2)AU-MEL (Melbourne) Linode Kubernetes EngineIN-BOM-2 (Mumbai 2)IN-BOM-2 (Mumbai 2) Linode Kubernetes EngineSG-SIN-2 (Singapore 2)DE-FRA-2 (Frankfurt 2) Linode Kubernetes EngineDE-FRA-2 (Frankfurt 2)SG-SIN-2 (Singapore 2) Linode Kubernetes EngineJP-TYO-3 (Tokyo 3)JP-TYO-3 (Tokyo 3) Linode Kubernetes EngineZA-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)FR-PAR-2 (Paris 2)US-IAD-2 (Washington 2)
Timeline · 5 updates

Read the full incident report →