Connectivity Issue - ASIA Data Centers
Update - The third-party continues working on a fix for this issue, and due to the complexity of this problem, it will take longer to mitigate it completely. In the meantime, we continue monitoring our systems. If you are still experiencing issues, please open a Support ticket for assistance.
Feb 25, 2025 - 19:44 UTC
Monitoring - At this time we have been able to correct the issues affecting connectivity from our Asia to Europe 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.
Jan 27, 2025 - 10:16 UTC
Identified - Our team has identified a third-party issue affecting connectivity from our Asia to Europe Data Centers between ~02:10 to ~14:58 UTC on January 25, 2025. During this time, users may have experienced latency and potential congestion on some providers between Asia and Europe. 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 support@linode.com.
Jan 25, 2025 - 16:49 UTC
Linode.com Operational
Linode 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 (Sao 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
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
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
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
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
AP-West (Mumbai) Operational
EU-West (London) Operational
GB-LON (London 2) Operational
AU-MEL (Melbourne) 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-2 (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) Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

Managed Databases Monitoring and Alerting Maintenance Apr 8, 2025 09:30-11:30 UTC

The Akamai Cloud Pulse observability suite which enables Monitoring and Alerting for our Managed Databases offering is scheduled to undergo maintenance on April 8th, 2025, between 9:30 AM and 11:30 AM UTC. During this window there is the potential for duplicate alerts configured for your Managed Databases services to be triggered. This maintenance WILL NOT impact the functionality of our Managed Databases service, only the Monitoring and Alerting features. We will update this status page if we encounter any unexpected issues.
Posted on Mar 27, 2025 - 12:49 UTC
Mar 28, 2025
Emerging Service Issue - Node Balancers - All Regions
Resolved - We haven’t observed any additional issues with the Node Balancers, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Mar 28, 09:05 UTC
Monitoring - At this time we have been able to correct the issues affecting the NodeBalancer service. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a ticket with our Support Team.
Mar 28, 05:56 UTC
Update - We are continuing to investigate this issue.
Mar 28, 01:07 UTC
Update - We are continuing to investigate this issue.
Mar 27, 23:45 UTC
Investigating - Our team is investigating an emerging service issue affecting Node Balancers in all regions. We will share additional updates as we have more information.
Mar 27, 22:57 UTC
Mar 27, 2025
Mar 26, 2025

No incidents reported.

Mar 25, 2025
Cloud Manager, API, CLI, linode.com Maintenance
Completed - The scheduled maintenance has been completed.
Mar 25, 16:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 25, 14:00 UTC
Scheduled - The Linode Cloud Manager, API, CLI, and linode.com will be undergoing scheduled maintenance between 14:00 UTC and 16:00 UTC, Tuesday, March 25, 2025. During this window, running Linodes and related services should not be disrupted. We will update this status page if we encounter any unexpected issues.
Mar 7, 18:18 UTC
Mar 24, 2025
Service Issue - Object Storage (LON)
Resolved - We haven’t observed any additional issues with the Object Storage service, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Mar 24, 21:31 UTC
Monitoring - At this time we have been able to correct the issues affecting the Object 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.
Mar 24, 21:01 UTC
Update - Our team continues to investigate the issue affecting the Object Storage service in London. During this time, users may experience connection timeouts and errors with this service.
Mar 24, 19:54 UTC
Investigating - Our team is investigating an issue affecting the Object Storage service in London. During this time, users may experience connection timeouts and errors with this service.
Mar 24, 17:08 UTC
Mar 23, 2025

No incidents reported.

Mar 22, 2025

No incidents reported.

Mar 21, 2025
Emergency Network Maintenance - AP-WEST (Mumbai)
Completed - The scheduled maintenance has been completed.
Mar 21, 00:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 20, 18:30 UTC
Scheduled - We will be performing an emergency network maintenance in our AP-WEST (Mumbai) data center beginning 20 March 2025, 18:30 UTC until 21 March 2025, 00:30 UTC. During this time, users with resources in the AP-WEST (Mumbai) region may experience intermittent issues when attempting to take actions like creating, updating, and deleting resources within this region.
Mar 20, 16:05 UTC
Mar 20, 2025
Maintenance for Linode Support Ticketing System
Completed - The scheduled maintenance has been completed.
Mar 20, 17:15 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 20, 17:00 UTC
Scheduled - On Thursday, March 20th, 2025, at 1:00PM EDT (17:00 UTC), scheduled maintenance will be performed on the Linode Support Ticketing System.

Expected downtime for this maintenance will be about 15 minutes.

This should not impact the ability to access services or utilize Cloud Manager. 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.
Mar 19, 18:19 UTC
Mar 19, 2025

No incidents reported.

Mar 18, 2025
Service Issue - Object Storage (LAX)
Resolved - We haven’t observed any additional issues with the Object Storage service, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Mar 18, 17:04 UTC
Monitoring - At this time we have been able to correct the issues affecting the Object 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.
Mar 16, 05:00 UTC
Identified - Our team has identified the issue affecting the Object Storage service. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Mar 16, 03:53 UTC
Investigating - Our team is investigating an issue affecting the Object Storage service in the Los Angeles region. During this time, users may experience connection timeouts and errors with this service.
Mar 16, 01:42 UTC
Emergency Network Maintenance - AP-South (Singapore)
Completed - The scheduled maintenance has been completed.
Mar 18, 17:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 18, 15:00 UTC
Scheduled - We will be performing an emergency network maintenance in our AP-South (Singapore) data center, it should not be causing any impact.
Mar 17, 22:09 UTC
Service Issue - Connectivity Issues - All Regions
Postmortem - Read details
Mar 18, 21:56 UTC
Resolved - We haven’t observed any additional connectivity issues in our data centers, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Mar 18, 16:24 UTC
Monitoring - We have successfully mitigated the network connectivity issues affecting all regions. At this time, we are observing a return to normal service, and disruptions, including difficulties with deploying, booting, or using Linodes, are no longer occurring. We are continuing to monitor the fix closely to ensure overall systems stability.


Thank you for your patience as we ensure the ongoing reliability of our services. We will provide further updates if necessary.
Mar 17, 21:22 UTC
Update - We are continuing to work on a fix for this issue.
Mar 17, 20:18 UTC
Update - We are actively working to resolve the networking issues affecting all regions. Users in Amsterdam (NL-AMS) may experience more significant disruptions, including difficulties deploying, booting, or using Linodes.

Our team is focused on resolving these issues as quickly as possible, and we will provide further updates as they become available.
Mar 17, 19:20 UTC
Identified - We are still actively working to resolve the network connectivity issue impacting all regions. We believe we have identified the root cause and are currently implementing a fix. Our team continues to monitor the situation closely, and we will provide additional updates as more information becomes available. Thank you for your continued patience.
Mar 17, 18:44 UTC
Investigating - Our team is investigating an emerging service issue affecting network connectivity in multiple regions . We will share additional updates as we have more information.
Mar 17, 17:26 UTC
Service Issue - Connectivity Issues - Multiple Regions
Resolved - We became aware of a connectivity issue related to intermittent performance degradation and latency issues on workload on multiple Data Centers. The issue was observed intermittently between 08:26 UTC and 10:54 UTC on March 18, 2025. We can confirm that the issue is now resolved, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700000KtyFoCAJ or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.
Mar 18, 14:24 UTC
Emerging Service Issue - Cloud Manager Payment Processing
Resolved - At this time we have resolved the issue affecting payments being processed successfully. We will continue to monitor for additional issues. If you continue to experience problems please open a Support ticket.
Mar 18, 03:37 UTC
Update - We are continuing to work on a fix for this issue.
Mar 18, 01:41 UTC
Investigating - Our team is investigating an emerging service issue preventing payments from processing successfully. This includes users attempting to sign up for a new account as well as adding or updating payment methods to existing accounts. We will share additional updates as we have more information.
Mar 17, 23:07 UTC
Mar 17, 2025
Service Issue - Block Storage (US-IAD)
Resolved - We have resolved the issue affecting Block Storage in (IAD, which occurred between 10:19 and 12:10 UTC on 17 March 2025. During this time, customers may have experienced read/write timeouts or errors when accessing resources in the Block Storage US-IAD data center.

We believe the issue has been fully resolved, and we are actively monitoring the service to ensure stability. If you continue to experience problems, please open a Support ticket for assistance.
Mar 17, 19:22 UTC
Emergency Network Maintenance - AP-South (Singapore)
Completed - The scheduled maintenance has been completed.
Mar 17, 16:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 17, 15:00 UTC
Scheduled - We will be performing an emergency network maintenance in our AP-South (Singapore) data center, it should not be causing any impact.
Mar 14, 19:27 UTC
Mar 16, 2025
Mar 15, 2025

No incidents reported.

Mar 14, 2025
Emerging Service Issue - DNS Resolution - Italy and Switzerland
Resolved - We haven’t observed any additional issues with our Hosted DNS Service, and will now consider this incident resolved. If you are still experiencing issues, please open a Support ticket for assistance.
Mar 14, 15:20 UTC
Monitoring - We have been able to correct the issue affecting our Hosted DNS Service at 20:25 UTC, on March 13th, 2025. We will be monitoring this to ensure that connectivity remains stable. If you continue to experience problems, please open a ticket with our Support Team.
Mar 13, 22:58 UTC
Identified - Our team has identified the issue affecting our Hosted DNS Service. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Mar 13, 22:31 UTC
Update - After our initial investigation we have been able to confirm the connectivity issues in our DNS Services is only impacting to users located in Italy and Switzerland. During this time, users may experience timeouts or errors when making DNS lookups against domains configured to use ns1-5.linode.com. We are continuing to investigate the issue and will share additional updates as more information is available.
Mar 13, 19:06 UTC
Investigating - Our team is investigating an emerging service issue impacting connectivity to our DNS Services for a subset users located in Europe. We will share additional updates as we have more information.
Mar 13, 17:56 UTC
← Incident History Powered by Atlassian Statuspage