Linode logo

Is Linode Down?

Cloud InfrastructureLive status, outages, and incident history

No. Linode is up right now.

Every monitored Linode system is operational as of August 24, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive, rechecked every 60s1 active incident
How we know: the official Linode status page, PulsAPI's own check every 60 seconds, and outage reports from engineers. How PulsAPI monitoring works

Linode Component Status

The main Linode systems on this page. All 242 are operational right now.

242operational
Backups » AP-Northeast-2 (Tokyo 2) Backups
Operational
Backups » AP-South (Singapore) Backups
Operational
Backups » AP-Southeast (Sydney) Backups
Operational

239 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Backups » AP-West (Mumbai) Backups, Backups » AU-MEL (Melbourne) Backups, Backups » BR-GRU (São Paulo) Backups, Backups » CA-Central (Toronto) Backups, Backups » DE-FRA-2 (Frankfurt 2) Backups, Backups » ES-MAD (Madrid) Backups, Backups » EU-Central (Frankfurt) Backups, Backups » EU-West (London) Backups, Backups » FR-PAR (Paris) Backups, Backups » GB-LON (London 2) Backups, Backups » ID-CGK (Jakarta) Backups, Backups » IN-BOM-2 (Mumbai 2) Backups, and 227 more.

Create a free account

Component statuses may change independently during partial outages.

Recent Linode Outages & Incidents

Incident history from the official Linode status page, including resolution updates.

Service Issue - US-SEA (Seattle, WA)Resolved Aug 21, 2026 · 4h 35mResolved

At this time we have been able to correct the issue and the service has resumed normal operation. --- [2026-08-21T17:23:15.885Z] (investigating) Our team is investigating an emerging service issue affecting us-sea (Seattle, WA). We will share additional updates as we have more information.

Scheduled Maintenance for Linode Cloud Manager, API, CLIScheduled for Aug 19, 2026 · 1h 30mScheduled

Scheduled maintenance is currently in progress. We will provide updates as necessary. --- [2026-08-19T03:00:13.385Z] (scheduled) Maintenance will begin as scheduled in 60 minutes. --- [2026-07-09T14:53:15.853Z] (scheduled) The Linode Cloud Manager, API, and CLI will be offline for scheduled maintenance between 04:00 UTC and 05:30 UTC on August 19, 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.

Connectivity Issue - IT-MIL (Milan) data centerResolved Aug 14, 2026 · 1h 17mResolved

On August 14, 2026, starting around 17:30 UTC, during an event in our IT-MIL \(Milan\) data center, multiple alerts were triggered indicating that multiple hosts in this data center became unreachable. ‌ Akamai immediately began investigating the issue and working to restore the impacted hosts. During the impact window, customers would have experienced intermittent connection timeouts and errors across all services deployed in this data center. ‌ We restored the impacted hosts and fixed the connectivity issues at 21:20 UTC on August 14, 2026. We are still investigating the cause of the failure condition. ‌ We are committed to preventing future incidents and will conduct a thorough investigation into why the hosts became unreachable, implementing measures to enhance stability and reliability. ‌ 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. --- [2026-08-14T21:30:41.727Z] (resolved) We haven’t observed any additional connectivity issues in our IT-MIL (Milan) data center and will now consider this incident resolved. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance. --- [2026-08-14T21:18:10.920Z] (investigating) We are continuing to investigate this issue. We will share additional updates as we have more information. --- [2026-08-14T20:13:30.922Z] (investigating) Our team is investigating an issue affecting connectivity in our IT-MIL (Milan) 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.

Linode Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Linode incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
May 2698.75% average · 9 days with incidentsAug 24

Going further back: Linode uptime by month and every recorded Linode outage.

Live Linode Outage Reports

Problems reported by engineers using Linode. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Linode problems reported yet.

Something wrong with Linode on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Linode

Akamai Cloud (formerly Linode) is a developer-focused cloud hosting platform providing VMs, managed Kubernetes, object storage, and bare metal across 11 global regions. Track Akamai Cloud status and outages here.

Over the past 30 days, PulsAPI has measured Linode uptime at 100.00%. Response times, incident history, and SLA tracking for Linode are available on the PulsAPI dashboard.

Linode Status FAQ

Is Linode down right now?

PulsAPI checks Linode every 60 seconds. The verdict at the top of this page comes from the latest poll of the official Linode status feed and refreshes automatically, so you are not looking at a stale cached answer.

What should I do if Linode is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Linode recovers.

How do I check Linode uptime history?

PulsAPI tracks Linode uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. A free PulsAPI account unlocks the full 90-day SLA history and incident timeline for Linode.

How fast does PulsAPI detect Linode outages?

PulsAPI polls the official Linode status page every 60 seconds and usually delivers alerts to Slack, Discord, Microsoft Teams, PagerDuty, or email in under 4 seconds after detection. That is often faster than someone on your team notices on their own.

Does PulsAPI track individual Linode components?

Yes. PulsAPI monitors 242 individual Linode components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Linode goes down?

Yes. Create a PulsAPI account and subscribe to Linode. Email alerts are included on the free Starter plan. Paid plans add Slack, Discord, Microsoft Teams, PagerDuty, and webhooks whenever Linode status changes.

How do I report an issue with Linode to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Linode problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Linode?

Yes. PulsAPI's Starter plan includes up to 25 monitored services with Slack and email alerts, and the 30-day free trial requires no credit card. You can monitor Linode alongside up to 24 other services at pulsapi.com/signup.

Track Linode with the rest of your stack

Monitor 2463+ cloud services from one dashboard and get alerts when Linode status changes.

Start free trial