Service Issue - Block Storage (BR-GRU)
Monitoring - A fix has been implemented and we are monitoring the results.
Oct 28, 2026 - 20:18 UTC
Investigating - Our team is investigating an issue affecting the Block Storage service in our BR-GRU (São Paulo) data center. During this time, Block Storage volume creation, deletion and cloning may fail. We will share additional updates as we have more information.
Oct 28, 2026 - 20:17 UTC
Connectivity Issue between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2)
Update - We are continuing to monitor for any further issues.
Oct 25, 2026 - 16:13 UTC
Monitoring - At this time, we have been able to correct the issues affecting connectivity between our ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2) data centers. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.
Oct 25, 2026 - 16:12 UTC
Update - We are continuing to investigate this issue. We will share additional updates as we have more information.
Oct 25, 2026 - 14:52 UTC
Investigating - Our team is investigating an issue affecting connectivity between our ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2) data centers. 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.
Oct 25, 2026 - 13:54 UTC
Customer Security Advisory: Critical F5/NGINX Out-of-Band Vulnerabilities
Investigating - Akamai is aware of the recently published F5/NGINX vulnerabilities (CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479), and our teams are actively investigating their potential impact across our platform and infrastructure.

F5 has released out-of-band security patches addressing three critical severity vulnerabilities in NGINX Open Source and NGINX Plus. These vulnerabilities may allow unauthenticated attackers to trigger heap buffer overflows, which could cause a denial of service or potential remote code execution if ASLR is bypassed.

If you are running a vulnerable version of NGINX Open Source or NGINX Plus on a Linode instance, we recommend following guidance from F5/NGINX and applying available patches.

We will provide updates as additional information becomes available.
Oct 22, 2026 - 20:08 UTC
(PwnEscape) Guest-to-Host KVM Escape [CVE-2026-99999]
Update - Akamai has completed patching Compute hypervisors for the known vulnerabilities related to CVE-2026-99999, also referred to as “PwnEscape”, and we have not identified any exploitation on the Akamai platform.

We recommend that customers upgrade Linode guest VMs using kernels from upstream OS vendors as those become available, especially for cases where less trusted workloads are being run within containers or nested virtualization. We are in the process of preparing images containing fixes from upstream vendors.
Oct 17, 2026 - 05:07 UTC
Update - We have not identified any exploitation on the Akamai platform so far. As of now, our subject matter experts are continuing to work on patching server sets in phases across the Akamai platform. We are actively monitoring our platform while we perform the mitigation actions.
Oct 16, 2026 - 08:53 UTC
Identified - Akamai is aware of the recently published Guest-to-Host KVM Escape (CVE-2026-99999) vulnerability. Our teams have proactively identified its potential impact and are actively applying mitigations across our platform and infrastructure. There is potential for customer workload impact as a part of our platform response to this vulnerability. At this time, we have not observed evidence of this vulnerability being actively exploited on our platform. We will provide updates as additional information becomes available.
Oct 15, 2026 - 17:27 UTC
Linode.com Operational
Cloud Manager and API Operational
Hosted DNS Service Operational
Longview Operational
Managed Databases Operational
Regions Operational
US-East (Newark) Operational
US-Central (Dallas) Operational
US-West (Fremont) Operational
US-Southeast (Atlanta) Operational
US-IAD (Washington) Operational
US-ORD (Chicago) Operational
CA-Central (Toronto) Operational
EU-West (London) Operational
EU-Central (Frankfurt) Operational
FR-PAR (Paris) Operational
AP-South (Singapore) Operational
AP-Northeast-2 (Tokyo 2) Operational
AP-West (Mumbai) Operational
AP-Southeast (Sydney) Operational
SE-STO (Stockholm) Operational
US-SEA (Seattle) Operational
IT-MIL (Milan) Operational
JP-OSA (Osaka) Operational
IN-MAA (Chennai) Operational
ID-CGK (Jakarta) Operational
BR-GRU (São Paulo) Operational
NL-AMS (Amsterdam) Operational
US-MIA (Miami) Operational
US-LAX (Los Angeles) Operational
ES-MAD (Madrid) Operational
AU-MEL (Melbourne) Operational
GB-LON (London 2) Operational
IN-BOM-2 (Mumbai 2) Operational
SG-SIN-2 (Singapore 2) Operational
DE-FRA-2 (Frankfurt 2) Operational
JP-TYO-3 (Tokyo 3) Operational
ZA-JNB (Johannesburg) Operational
NZ-AKL (Auckland) Operational
CO-BOG (Bogota) Operational
US-DEN (Denver) Operational
DE-HAM (Hamburg) Operational
US-HOU (Houston) Operational
MY-KUL (Kuala Lumpur) Operational
FR-MRS (Marseille) Operational
MX-QRO (Queretaro) Operational
CL-SCL (Santiago) Operational
FR-PAR-2 (Paris 2) Operational
US-IAD-2 (Washington 2) Operational
Backups Operational
US-East (Newark) Backups Operational
US-Central (Dallas) Backups Operational
US-West (Fremont) Backups Operational
US-Southeast (Atlanta) Backups Operational
US-IAD (Washington) Backups Operational
US-ORD (Chicago) Backups Operational
CA-Central (Toronto) Backups Operational
EU-West (London) Backups Operational
EU-Central (Frankfurt) Backups Operational
FR-PAR (Paris) Backups Operational
AP-South (Singapore) Backups Operational
AP-Northeast-2 (Tokyo 2) Backups Operational
AP-West (Mumbai) Backups Operational
AP-Southeast (Sydney) Backups Operational
SE-STO (Stockholm) Backups Operational
US-SEA (Seattle) Backups Operational
JP-OSA (Osaka) Backups Operational
IN-MAA (Chennai) Backups Operational
BR-GRU (São Paulo) Backups Operational
NL-AMS (Amsterdam) Backups Operational
ES-MAD (Madrid) Backups Operational
IT-MIL (Milan) Backups Operational
US-MIA (Miami) Backups Operational
ID-CGK (Jakarta) Backups Operational
US-LAX (Los Angeles) Backups Operational
GB-LON (London 2) Backups Operational
AU-MEL (Melbourne) Backups Operational
IN-BOM-2 (Mumbai 2) Backups Operational
DE-FRA-2 (Frankfurt 2) Backups Operational
SG-SIN-2 (Singapore 2) Backups Operational
JP-TYO-3 (Tokyo) Backups Operational
Block Storage Operational
US-East (Newark) Block Storage Operational
US-Central (Dallas) Block Storage Operational
US-West (Fremont) Block Storage Operational
US-Southeast (Atlanta) Block Storage Operational
US-IAD (Washington) Block Storage Operational
US-ORD (Chicago) Block Storage Operational
CA-Central (Toronto) Block Storage Operational
EU-West (London) Block Storage Operational
EU-Central (Frankfurt) Block Storage Operational
FR-PAR (Paris) Block Storage Operational
AP-South (Singapore) Block Storage Operational
AP-Northeast-2 (Tokyo 2) Block Storage Operational
AP-West (Mumbai) Block Storage Operational
AP-Southeast (Sydney) Block Storage Operational
SE-STO (Stockholm) Block Storage Operational
US-SEA (Seattle) Block Storage Operational
JP-OSA (Osaka) Block Storage Operational
IN-MAA (Chennai) Block Storage Operational
BR-GRU (São Paulo) Block Storage Operational
NL-AMS (Amsterdam) Block Storage Operational
ES-MAD (Madrid) Block Storage Operational
IT-MIL (Milan) Block Storage Operational
US-MIA (Miami) Block Storage Operational
ID-CGK (Jakarta) Block Storage Operational
US-LAX (Los Angeles) Block Storage Operational
GB-LON (London 2) Block Storage Operational
AU-MEL (Melbourne) Block Storage Operational
IN-BOM-2 (Mumbai 2) Block Storage Operational
DE-FRA-2 (Frankfurt 2) Block Storage Operational
SG-SIN-2 (Singapore 2) Block Storage Operational
JP-TYO-3 (Tokyo 3) Block Storage Operational
NodeBalancers Operational
US-East (Newark) NodeBalancers Operational
US-Central (Dallas) NodeBalancers Operational
US-West (Fremont) NodeBalancers Operational
US-Southeast (Atlanta) NodeBalancers Operational
US-IAD (Washington) NodeBalancers Operational
US-ORD (Chicago) NodeBalancers Operational
CA-Central (Toronto) NodeBalancers Operational
EU-West (London) NodeBalancers Operational
EU-Central (Frankfurt) NodeBalancers Operational
FR-PAR (Paris) NodeBalancers Operational
AP-South (Singapore) NodeBalancers Operational
AP-Northeast-2 (Tokyo 2) NodeBalancers Operational
AP-West (Mumbai) NodeBalancers Operational
AP-Southeast (Sydney) NodeBalancers Operational
SE-STO (Stockholm) NodeBalancers Operational
US-SEA (Seattle) NodeBalancers Operational
JP-OSA (Osaka) NodeBalancers Operational
IN-MAA (Chennai) NodeBalancers Operational
BR-GRU (São Paulo) NodeBalancers Operational
NL-AMS (Amsterdam) NodeBalancers Operational
ES-MAD (Madrid) NodeBalancers Operational
IT-MIL (Milan) NodeBalancers Operational
US-MIA (Miami) NodeBalancers Operational
ID-CGK (Jakarta) NodeBalancers Operational
US-LAX (Los Angeles) NodeBalancers Operational
GB-LON (London 2) NodeBalancers Operational
AU-MEL (Melbourne) NodeBalancers Operational
IN-BOM-2 (Mumbai 2) NodeBalancers Operational
DE-FRA-2 (Frankfurt 2) NodeBalancers Operational
SG-SIN-2 (Singapore 2) NodeBalancers Operational
JP-TYO-3 (Tokyo 3) NodeBalancers Operational
Object Storage Operational
US-East (Newark) Object Storage Operational
US-Southeast (Atlanta) Object Storage Operational
US-IAD (Washington) Object Storage Operational
US-ORD (Chicago) Object Storage Operational
EU-Central (Frankfurt) Object Storage Operational
AP-South (Singapore) Object Storage Operational
FR-PAR (Paris) Object Storage Operational
SE-STO (Stockholm) Object Storage Operational
US-SEA (Seattle) Object Storage Operational
JP-OSA (Osaka) Object Storage Operational
IN-MAA (Chennai) Object Storage Operational
ID-CGK (Jakarta) Object Storage Operational
BR-GRU (Sao Paulo) Object Storage Operational
ES-MAD (Madrid) Object Storage Operational
GB-LON (London 2) Operational
AU-MEL (Melbourne) Operational
NL-AMS (Amsterdam) Object Storage Operational
IT-MIL (Milan) Object Storage Operational
US-MIA (Miami) Object Storage Operational
US-LAX (Los Angeles) Object Storage Operational
GB-LON (London 2) Object Storage Operational
AU-MEL (Melbourne) Object Storage Operational
IN-BOM-2 (Mumbai 2) Object Storage Operational
DE-FRA-2 (Frankfurt 2) Object Storage Operational
SG-SIN-2 (Singapore 2) Object Storage Operational
JP-TYO-3 (Tokyo 3) Object Storage Operational
Linode Kubernetes Engine Operational
US-East (Newark) Linode Kubernetes Engine Operational
US-Central (Dallas) Linode Kubernetes Engine Operational
US-West (Fremont) Linode Kubernetes Engine Operational
US-Southeast (Atlanta) Linode Kubernetes Engine Operational
US-IAD (Washington) Linode Kubernetes Engine Operational
US-ORD (Chicago) Linode Kubernetes Engine Operational
CA-Central (Toronto) Linode Kubernetes Engine Operational
EU-West (London) Linode Kubernetes Engine Operational
EU-Central (Frankfurt) Linode Kubernetes Engine Operational
FR-PAR (Paris) Linode Kubernetes Engine Operational
AP-South (Singapore) Linode Kubernetes Engine Operational
AP-Northeast (Tokyo 2) Linode Kubernetes Engine Operational
AP-West (Mumbai) Linode Kubernetes Engine Operational
AP-Southeast (Sydney) Linode Kubernetes Engine Operational
SE-STO (Stockholm) Linode Kubernetes Engine Operational
US-SEA (Seattle) Linode Kubernetes Engine Operational
JP-OSA (Osaka) Linode Kubernetes Engine Operational
IN-MAA (Chennai) Linode Kubernetes Engine Operational
ID-CGK (Jakarta) Linode Kubernetes Engine Operational
BR-GRU (São Paulo) Linode Kubernetes Engine Operational
NL-AMS (Amsterdam) Linode Kubernetes Engine Operational
ES-MAD (Madrid) Linode Kubernetes Engine Operational
IT-MIL (Milan) Linode Kubernetes Engine Operational
US-MIA (Miami) Linode Kubernetes Engine Operational
US-LAX (Los Angeles) Linode Kubernetes Engine Operational
GB-LON (London 2) Linode Kubernetes Engine Operational
AU-MEL (Melbourne) Linode Kubernetes Engine Operational
IN-BOM-2 (Mumbai 2) Linode Kubernetes Engine Operational
DE-FRA-2 (Frankfurt 2) Linode Kubernetes Engine Operational
SG-SIN-2 (Singapore 2) Linode Kubernetes Engine Operational
JP-TYO-3 (Tokyo 3) Linode Kubernetes Engine Operational
Metadata Service Operational
US-East (Newark) Operational
US-Central (Dallas) Operational
US-West (Fremont) Operational
US-Southeast (Atlanta) Operational
US-IAD (Washington) Operational
US-ORD (Chicago) Operational
CA-Central (Toronto) Operational
EU-West (London) Operational
EU-Central (Frankfurt) Operational
FR-PAR (Paris) Operational
AP-South (Singapore) Operational
AP-Northeast-2 (Tokyo 2) Operational
AP-West (Mumbai) Operational
AP-Southeast (Sydney) Operational
SE-STO (Stockholm) Operational
US-SEA (Seattle) Operational
IT-MIL (Milan) Operational
JP-OSA (Osaka) Operational
IN-MAA (Chennai) Operational
ID-CGK (Jakarta) Operational
BR-GRU (São Paulo) Operational
NL-AMS (Amsterdam) Operational
US-MIA (Miami) Operational
US-LAX (Los Angeles) Operational
ES-MAD (Madrid) Operational
AU-MEL (Melbourne) Operational
GB-LON (London 2) Operational
IN-BOM-2 (Mumbai 2) Operational
SG-SIN-2 (Singapore 2) Operational
DE-FRA-2 (Frankfurt 2) Operational
JP-TYO-3 (Tokyo 3) Operational
ZA-JNB (Johannesburg) Operational
NZ-AKL (Auckland) Operational
CO-BOG (Bogota) Operational
US-DEN (Denver) Operational
DE-HAM (Hamburg) Operational
US-HOU (Houston) Operational
MY-KUL (Kuala Lumpur) Operational
FR-MRS (Marseille) Operational
MX-QRO (Queretaro) Operational
CL-SCL (Santiago) Operational
Observability Operational
Akamai Cloud Pulse (ACLP) - Alerts Operational
Akamai Cloud Pulse (ACLP) - Logs Operational
Akamai Cloud Pulse (ACLP) - Metrics Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

Scheduled Longview Maintenance - US-Central (Dallas) Oct 29, 2026 05:30-11:30 UTC

As part of addressing security vulnerabilities, we will be upgrading Longview servers in Dallas region.

Existing graphs will remain available, but graph updates may be slightly delayed during individual server upgrades.

The Maintenance period is expected to be from October 27 through November 3, 2026, with activities scheduled between 5:30 AM and 11:30 AM UTC.
Posted on Oct 23, 2026 - 13:16 UTC

Scheduled Longview Maintenance - US-Central (Dallas) Oct 30, 2026 05:30-11:30 UTC

As part of addressing security vulnerabilities, we will be upgrading Longview servers in Dallas region.

Existing graphs will remain available, but graph updates may be slightly delayed during individual server upgrades.

The Maintenance period is expected to be from October 27 through November 3, 2026, with activities scheduled between 5:30 AM and 11:30 AM UTC.
Posted on Oct 23, 2026 - 13:17 UTC

Scheduled Longview Maintenance - US-Central (Dallas) Oct 31, 2026 05:30-11:30 UTC

As part of addressing security vulnerabilities, we will be upgrading Longview servers in Dallas region.

Existing graphs will remain available, but graph updates may be slightly delayed during individual server upgrades.

The Maintenance period is expected to be from October 27 through November 3, 2026, with activities scheduled between 5:30 AM and 11:30 AM UTC.
Posted on Oct 23, 2026 - 13:17 UTC

Scheduled Longview Maintenance - US-Central (Dallas) Nov 1, 2026 05:30-11:30 UTC

As part of addressing security vulnerabilities, we will be upgrading Longview servers in Dallas region.

Existing graphs will remain available, but graph updates may be slightly delayed during individual server upgrades.

The Maintenance period is expected to be from October 27 through November 3, 2026, with activities scheduled between 5:30 AM and 11:30 AM UTC.
Posted on Oct 23, 2026 - 13:18 UTC

Scheduled Longview Maintenance - US-Central (Dallas) Nov 2, 2026 05:30-11:30 UTC

As part of addressing security vulnerabilities, we will be upgrading Longview servers in Dallas region.

Existing graphs will remain available, but graph updates may be slightly delayed during individual server upgrades.

The Maintenance period is expected to be from October 27 through November 3, 2026, with activities scheduled between 5:30 AM and 11:30 AM UTC.
Posted on Oct 23, 2026 - 13:18 UTC

Scheduled Longview Maintenance - US-Central (Dallas) Nov 3, 2026 05:30-11:30 UTC

As part of addressing security vulnerabilities, we will be upgrading Longview servers in Dallas region.

Existing graphs will remain available, but graph updates may be slightly delayed during individual server upgrades.

The Maintenance period is expected to be from October 27 through November 3, 2026, with activities scheduled between 5:30 AM and 11:30 AM UTC.
Posted on Oct 23, 2026 - 13:19 UTC

Oct 28, 2026

Scheduled Longview Maintenance - US-Central (Dallas)
Completed - The scheduled maintenance has been completed.
Oct 28, 11:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 28, 05:32 UTC
Scheduled - As part of addressing security vulnerabilities, we will be upgrading Longview servers in Dallas region.

Existing graphs will remain available, but graph updates may be slightly delayed during individual server upgrades.

The Maintenance period is expected to be from October 27 through November 3, 2026, with activities scheduled between 5:30 AM and 11:30 AM UTC.
Oct 23, 13:15 UTC
Scheduled Maintenance for Linode Cloud Manager, API, CLI
Completed - The scheduled maintenance has been completed.
Oct 28, 05:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 28, 04:00 UTC
Scheduled - The Linode Cloud Manager, API, and CLI will be offline for scheduled maintenance between 04:00 UTC and 05:30 UTC on October 28, 2026. During this window, running Linodes and related services will not be disrupted, but account management access and Support tickets will be unavailable.

Please ensure that you complete critical or important jobs in the Cloud Manager or API before the maintenance window. We will update this status page once this event is complete and Linode customers have full access to all Linode services.

Customers who need assistance from Linode Support during this time will need to call 855-454-6633 (+1-609-380-7100 outside of the United States) to contact our Support team. Please note that our Support team will not be able to assist with issues related to the Cloud Manager or API, authenticate users to their accounts, or respond to Support tickets for the duration of the maintenance window. As soon as our Support team regains access, we will answer tickets in the order they are received.

Impacts on Current Linode Customers:
Current Linode customers will not be able to log in to the Cloud Manager, interact with the API, or perform any administrative or management functions. This includes Create, Remove, Boot, Migrate, Back Up, Shut Down, etc.

The scheduled maintenance will impact the Kubernetes API. Dynamic aspects of LKE that rely on the Linode API will also be impacted, to include items such as autoscaling, recycling, rebooting, attaching/detaching PVCs, Node Balancer provisioning, as well as the ability to create new clusters. Cluster nodes and running workloads will not be affected.

Impacts on Users Trying to Create Linode Accounts / Awaiting Account Authentication:
While the Linode Cloud Manager is offline during the maintenance period, we are unable to accept requests for new accounts or authenticate accounts for users awaiting full account access.

Thank you for your patience and understanding.
Sep 29, 21:46 UTC

Oct 27, 2026

Scheduled Longview Maintenance - US-Central (Dallas)
Completed - The scheduled maintenance has been completed.
Oct 27, 11:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 27, 05:30 UTC
Scheduled - As part of addressing security vulnerabilities, we will be upgrading Longview servers in Dallas region.

Existing graphs will remain available, but graph updates may be slightly delayed during individual server upgrades.

The Maintenance period is expected to be from October 27 through November 3, 2026, with activities scheduled between 5:30 AM and 11:30 AM UTC.
Oct 23, 13:15 UTC

Oct 26, 2026

No incidents reported.

Oct 25, 2026

Unresolved incident: Connectivity Issue between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2).

Oct 24, 2026

No incidents reported.

Oct 23, 2026

Connectivity Issue - Dallas Data Center (IPv6 Traffic to Google)
Resolved - This issue is considered resolved.
Oct 23, 20:38 UTC
Monitoring - This was identified to be an upstream issue and should be resolved at this time, we will continue to monitor to ensure things remain stable.
Oct 23, 16:32 UTC
Investigating - Our team is currently investigating a connectivity issue in our Dallas data center. This is strictly affecting traffic routed via IPv6 to Google and its associated products, which may cause intermittent connection timeouts. We will post further updates as soon as more information becomes available.
Oct 23, 09:21 UTC
Customer Security Advisory: PHP Remote Code Execution Vulnerabilities
Resolved - Akamai has completed its assessment of the recently published PHP remote code execution vulnerabilities (CVE-2026-109618 and CVE-2026-109619) across our platform and infrastructure, and mitigation efforts are complete.

Cloud Infrastructure Speed Tests will remain offline in the near term. We plan to bring them back online in the near future.

If you are running a vulnerable version of PHP on a Linode instance, we recommend following guidance from the upstream vendor (PHP) and applying upstream patches as they become available.

We appreciate your patience while our teams completed this work.
Oct 23, 20:37 UTC
Update - Akamai is aware of the recently published (CVE-2026-109618 and CVE-2026-109619) vulnerabilities and our teams are actively investigating its potential impact across our platform and infrastructure. As a part of ongoing mitigation efforts, our Cloud Infrastructure Speed Tests will be unavailable.

If you are running a vulnerable version of PHP on a Linode instance, we recommend following guidance from the upstream vendor (PHP) and applying upstream patches as they become available.

We will provide updates as additional information becomes available.
Oct 22, 18:19 UTC
Identified - Updated Guidance after assessment:
Akamai is aware of the recently published (CVE-2026-109618 and CVE-2026-109619) vulnerabilities and our teams are actively investigating its potential impact across our platform and infrastructure. As a part of ongoing mitigation efforts, our Cloud Infrastructure Speed Tests will be unavailable.

If you are running a vulnerable version of PHP on a Linode instance, we recommend following guidance from the upstream vendor (PHP) and applying upstream patches as they become available.

We will provide updates as additional information becomes available.
Oct 21, 17:41 UTC
Investigating - Akamai is aware of the recently published (CVE-2026-109618 and CVE-2026-109619) vulnerabilities and our teams are actively investigating its potential impact across our platform and infrastructure. As a part of ongoing mitigation efforts, some Quick Deploy Apps, speed test pages, and parts of the website may be unavailable.

If you are running a vulnerable version of PHP on a Linode instance, we recommend following guidance from the upstream vendor (PHP) and applying upstream patches as they become available.

We will provide updates as additional information becomes available.
Oct 21, 14:44 UTC

Oct 22, 2026

Service Issue - Linode Kubernetes Engine
Postmortem - Read details
Oct 22, 16:00 UTC
Resolved - Our team identified an issue affecting the Linode Kubernetes Engine (LKE). During the impact timeframe (~11:10-12:50 UTC), new worker nodes were unable to provision. We have been able to correct the issues affecting the LKE service and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Oct 22, 13:58 UTC

Oct 21, 2026

Oct 20, 2026

Issue in creating new LKE Enterprise cluster across regions
Postmortem - Read details
Oct 21, 15:50 UTC
Resolved - We haven’t observed any additional issues with the LKE service, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Oct 20, 21:42 UTC
Update - Our team has identified the issue affecting the LKE Enterprise service. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Oct 20, 14:06 UTC
Update - We are currently investigating an issue affecting the provisioning of new LKE Enterprise (LKE-E) clusters across all regions. Affected clusters may experience nodes that successfully reach a "Ready" state, but system critical components may fail to start properly, preventing workloads from running.
Oct 20, 12:34 UTC
Update - We are continuing to work on a fix for this issue.
Oct 20, 12:33 UTC
Identified - We are currently investigating an issue affecting the provisioning of new LKE Enterprise (LKE-E) clusters across all regions. Affected clusters may experience nodes that successfully reach a "Ready" state, but system critical components may fail to start properly, preventing workloads from running.
Oct 20, 12:29 UTC

Oct 19, 2026

Connectivity Issue - US-ORD
Postmortem - Read details
Oct 26, 19:33 UTC
Resolved - We haven’t observed any additional connectivity issues in our Chicago (US-ORD) data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Oct 19, 20:33 UTC
Monitoring - At this time we have been able to correct the issues affecting connectivity in our Chicago (US-ORD) data center. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.
Oct 19, 15:29 UTC
Investigating - Our team has identified an issue affecting connectivity in our Chicago (US-ORD) 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.
Oct 19, 14:49 UTC

Oct 18, 2026

No incidents reported.

Oct 17, 2026

Unresolved incident: (PwnEscape) Guest-to-Host KVM Escape [CVE-2026-99999].

Oct 16, 2026

Maintenance - Akamai Cloud Login Service
Resolved - The maintenance has been completed. New customer signup and account creation are fully restored.
Oct 16, 12:20 UTC
Investigating - We are performing maintenance on the Akamai Cloud Login service. During this maintenance, new customer signup and account creation are temporarily disabled. Existing customers accounts are not affected and will be able to log in normally.
Oct 15, 17:15 UTC

Oct 15, 2026

Oct 14, 2026

No incidents reported.

Incident History Powered by Atlassian Statuspage