All Systems Operational
Linode.com Operational
Linode Manager and API Operational
Hosted DNS Service Operational
Longview Operational
Regions Operational
US-East (Newark) Operational
US-Central (Dallas) Operational
US-West (Fremont) Operational
US-Southeast (Atlanta) Operational
CA-Central (Toronto) Operational
EU-West (London) Operational
EU-Central (Frankfurt) Operational
AP-South (Singapore) Operational
AP-Northeast-2 (Tokyo 2) Operational
AP-West (Mumbai) Operational
AP-Southeast (Sydney) Operational
Backups Operational
US-East (Newark) Backups Operational
US-Central (Dallas) Backups Operational
US-West (Fremont) Backups Operational
US-Southeast (Atlanta) Backups Operational
CA-Central (Toronto) Backups Operational
EU-West (London) Backups Operational
EU-Central (Frankfurt) Backups Operational
AP-South (Singapore) Backups Operational
AP-Northeast-2 (Tokyo 2) Backups Operational
AP-West (Mumbai) Backups Operational
AP-Southeast (Sydney) Backups Operational
Block Storage Operational
US-East (Newark) Block Storage Operational
US-Central (Dallas) Block Storage Operational
US-West (Fremont) Block Storage Operational
CA-Central (Toronto) Block Storage Operational
EU-West (London) Block Storage Operational
EU-Central (Frankfurt) Block Storage Operational
AP-South (Singapore) Block Storage Operational
AP-Northeast-2 (Tokyo 2) Block Storage Operational
AP-West (Mumbai) 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
CA-Central (Toronto) NodeBalancers Operational
EU-West (London) NodeBalancers Operational
EU-Central (Frankfurt) NodeBalancers Operational
AP-South (Singapore) NodeBalancers Operational
AP-Northeast-2 (Tokyo 2) NodeBalancers Operational
AP-West (Mumbai) NodeBalancers Operational
AP-Southeast (Sydney) NodeBalancers Operational
Object Storage Operational
US-East (Newark) Object Storage Operational
EU-Central (Frankfurt) 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
EU-West (London) Linode Kubernetes Engine Operational
EU-Central (Frankfurt) Linode Kubernetes Engine Operational
AP-South (Singapore) Linode Kubernetes Engine Operational
AP-Northeast-2 (Tokyo 2) Linode Kubernetes Engine Operational
AP-Southeast (Sydney) Linode Kubernetes Engine Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
We will be performing a scheduled network maintenance on our gateway routers in the Sydney data center from Tuesday, June 9th, 16:00 UTC until Tuesday, June 9th, 17:30 UTC. We do not expect any downtime during this maintenance however, a brief period of packet loss or increased latency may be observed.
Posted on Jun 3, 13:35 UTC
Past Incidents
Jun 3, 2020

No incidents reported today.

Jun 2, 2020
Resolved - Our team is confident that the issue affected the Dallas data center has been fully resolved. If you are having trouble connecting please open a Support ticket in the Linode Manager
Jun 2, 23:14 UTC
Monitoring - At this time we have been able to correct the degradation issues affecting our Dallas data center. We will be monitoring this issue to ensure connectivity remains stable.
If you are still experiencing issues with our LKE and API services, please reach out to our Customer Support Team for assistance.
Jun 2, 21:39 UTC
Identified - We have identified the source of this issue as network performance degradation affecting the Dallas data center. This is impacting LKE and API services. We are working to resolve this issue and will be posting updates as they become available.
Jun 2, 20:35 UTC
Investigating - We are currently aware of and investigating degraded service with the Linode Kubernetes Engine. We will be providing additional information here as it become available.
Jun 2, 19:22 UTC
Jun 1, 2020
Resolved - Because we have not experienced any additional connectivity issues affecting our London data center this matter is now resolved.
If you are still experiencing connectivity issues, please reach out to our Customer Support Team for assistance.
Jun 1, 04:45 UTC
Monitoring - At this time we have been able to correct the connectivity issues affecting our London data center. We will be monitoring this issue to ensure connectivity remains stable.
If you are still experiencing connectivity issues, please reach out to our Customer Support Team for assistance.
Jun 1, 03:41 UTC
Update - We are continuing to investigate this issue.
Jun 1, 03:13 UTC
Investigating - We are aware of connectivity issues affecting Linodes in our London data center and are currently investigating. We will continue to provide additional updates as this incident develops.
Jun 1, 02:57 UTC
Resolved - Because we have not experienced additional connectivity issues affecting our Mumbai data center, this matter is now resolved.
If you are still experiencing connectivity issues, please reach out to our Customer Support Team for assistance.
Jun 1, 03:24 UTC
Update - At this time we have restored connectivity for the majority of the affected subnet. However, we are still aware of intermittent losses in connectivity for some Linodes. We'll continue to work with our upstream partners to resolve this matter and post updates as we receive them.
May 31, 23:15 UTC
Monitoring - We have implemented a fix with our upstream partners to restore connectivity to the affected IP subnet. We are currently monitoring to ensure that connectivity remains stable.
May 31, 21:50 UTC
Investigating - We are currently investigating connectivity issues affecting an IP subnet in the Mumbai datacenter. We will be providing updates as they become available. If you are having trouble connecting please open a Support ticket in the Linode Manager
May 31, 20:42 UTC
May 31, 2020
May 30, 2020

No incidents reported.

May 29, 2020
Resolved - After monitoring this issue, Linode Kubernetes Engine services have remained stable and we are confident that this matter has been resolved. If you are still experiencing issues please reach out to Linode Customer Support.
May 29, 02:39 UTC
Monitoring - We've deployed a fix for this issue, and we're monitoring the status of the Linode Kubernetes Engine to ensure that no further issues occur. We'll continue to provide updates until we're confident this has been resolved.
May 29, 01:52 UTC
Identified - We have identified the cause of the degraded services affecting the Linode Kubernetes Engine and are implementing a fix at this time. We will continue to investigate this issue and provide updates as they become available.
May 29, 00:54 UTC
Investigating - We are currently investigating an issue with the Linode Kubernetes Engine that has resulted in partially degraded service for some customers. We will be providing additional updates as we gather more information.
May 29, 00:33 UTC
May 28, 2020
Resolved - We are confident the fix implemented to correct issues with the CSI Block Storage driver is working as expected, and so we are considering this issue resolved. If you are still experiencing additional problems please open a Support ticket from the Linode Manager.
May 28, 22:27 UTC
Monitoring - Our team has implemented a fix to correct the upstream issue affecting the use of the CSI Block Storage driver. All LKE Clusters which were deployed over the impacted timeframe, along with existing clusters, have had their CSI driver updated. We will continue to monitor this situation for any related issues.
May 28, 20:48 UTC
Identified - We are aware of an upstream issue affecting the use of the CSI Block Storage driver for LKE Clusters and Nodes which are newly created or have recently restarted the CSI driver. We will continue to post additional updates as the situation develops.
May 28, 16:27 UTC
May 27, 2020

No incidents reported.

May 26, 2020

No incidents reported.

May 25, 2020

No incidents reported.

May 24, 2020

No incidents reported.

May 23, 2020

No incidents reported.

May 22, 2020
Completed - The scheduled maintenance has been completed.
May 22, 00:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 21, 22:00 UTC
Scheduled - We will be performing an emergency network maintenance on a Core Switch in the Newark data center on Thursday, May 21st, 22:00 UTC, until Thursday, May 21st, at 24:00 UTC.
We do not expect any downtime during this maintenance; however, a 30 to 60 second period of packet loss or increased latency may be observed.
May 21, 21:52 UTC
May 21, 2020
Resolved - Connectivity in our Newark data center has remained stable, and we are confident this matter has been resolved. If you are still experiencing additional issues, please contact our Customer Support Team for assistance.
May 21, 01:41 UTC
Monitoring - We have been able to correct the intermittent connectivity issues affecting our Newark data center. We will be monitoring this issue to ensure our services remain stable.
May 21, 00:14 UTC
Identified - We have identified the connectivity issues affecting our Newark data center. Our team is working quickly to implement a fix for the brief and sporadic networking issues affecting some customers.
May 20, 22:22 UTC
Investigating - We are aware of intermittent networking issues affecting public and private connections in our Newark data center. Our Network Operations team is working quickly to identify and resolve the root cause of these brief and sporadic outages. We’ll provide additional information as this situation develops.
May 20, 20:22 UTC
May 20, 2020