Linode status
Is Linode down? This is Linode’s current status, its components and its recent incidents, read from Linode’s official status page and refreshed every 2 minutes.
All Systems Operational
As reported by Linode’s status page, read Nov 15, 2026, 08:05 UTC.
Ongoing incidents
- Connectivity Issue between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2) · Oct 25, 2026, 13:54 UTC · monitoring, minor impact
We will continue to monitor to ensure that the impact has been fully mitigated. Further updates will be provided as we make progress.
- Service Issue - Block Storage (BR-GRU) · Oct 28, 2026, 20:17 UTC · monitoring
A fix has been implemented and we are monitoring the results.
Scheduled maintenance
- Scheduled maintenance for Block storage switches - AP-West (Mumbai) · Nov 7, 2026, 00:56 UTC · scheduled, maintenance impact
- Scheduled Maintenance for Linode Cloud Manager, API, CLI · Nov 12, 2026, 19:02 UTC · scheduled, maintenance impact
Components
| Component | Status |
|---|---|
| US-East (Newark) | Operational |
| Linode.com | Operational |
| US-East (Newark) Block Storage | Operational |
| US-East (Newark) NodeBalancers | Operational |
| US-East (Newark) Backups | Operational |
| US-East (Newark) Object Storage | Operational |
| US-East (Newark) Linode Kubernetes Engine | Operational |
| US-East (Newark) | Operational |
| Akamai Cloud Pulse (ACLP) - Alerts | Operational |
| Customer Security Advisory | Operational |
| Cloud Manager and API | Operational |
| US-Central (Dallas) | Operational |
| US-Central (Dallas) Block Storage | Operational |
| US-Central (Dallas) NodeBalancers | Operational |
| US-Central (Dallas) Backups | Operational |
| US-Central (Dallas) Linode Kubernetes Engine | Operational |
| US-Southeast (Atlanta) Object Storage | Operational |
| US-Central (Dallas) | Operational |
| Akamai Cloud Pulse (ACLP) - Logs | Operational |
| US-West (Fremont) | Operational |
| Hosted DNS Service | Operational |
| US-West (Fremont) Block Storage | Operational |
| US-West (Fremont) NodeBalancers | Operational |
| US-West (Fremont) Backups | Operational |
| US-West (Fremont) Linode Kubernetes Engine | Operational |
| US-IAD (Washington) Object Storage | Operational |
| US-West (Fremont) | Operational |
| Akamai Cloud Pulse (ACLP) - Metrics | Operational |
| US-Southeast (Atlanta) | Operational |
| US-Southeast (Atlanta) NodeBalancers | Operational |
| US-Southeast (Atlanta) Backups | Operational |
| Longview | Operational |
| US-Southeast (Atlanta) Block Storage | Operational |
| US-Southeast (Atlanta) Linode Kubernetes Engine | Operational |
| US-ORD (Chicago) Object Storage | Operational |
| US-Southeast (Atlanta) | Operational |
| EU-Central (Frankfurt) Object Storage | Operational |
| Managed Databases | Operational |
| US-IAD (Washington) | Operational |
| US-IAD (Washington) Backups | Operational |
| US-IAD (Washington) Block Storage | Operational |
| US-IAD (Washington) NodeBalancers | Operational |
| US-IAD (Washington) Linode Kubernetes Engine | Operational |
| US-IAD (Washington) | Operational |
| AP-South (Singapore) Object Storage | Operational |
| US-ORD (Chicago) | Operational |
| US-ORD (Chicago) Backups | Operational |
| US-ORD (Chicago) Block Storage | Operational |
| US-ORD (Chicago) NodeBalancers | Operational |
| US-ORD (Chicago) Linode Kubernetes Engine | Operational |
| US-ORD (Chicago) | Operational |
| CA-Central (Toronto) | Operational |
| CA-Central (Toronto) Block Storage | Operational |
| CA-Central (Toronto) NodeBalancers | Operational |
| CA-Central (Toronto) Backups | Operational |
| CA-Central (Toronto) Linode Kubernetes Engine | Operational |
| FR-PAR (Paris) Object Storage | Operational |
| CA-Central (Toronto) | Operational |
| EU-West (London) | Operational |
| EU-West (London) Block Storage | Operational |
What a degraded performance status means, and how much downtime an SLA allows: the uptime calculator.
Recent Linode incidents
- Customer Security Advisory: Critical F5/NGINX Out-of-Band Vulnerabilities · Oct 22, 2026, 20:08 UTC · resolved, lasted 453 h 51 min
Akamai has completed its investigation of the recently published F5/NGINX vulnerabilities (CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479). We have not identified any impact to Akamai’s platform or infrastructure. If you run a vulnerable version of NGINX Open Source or NGINX…
- Customer Security Advisory: CVE-2026-98432 · Oct 30, 2026, 18:10 UTC · resolved, lasted 243 h 13 min
We continue to monitor our systems and track upstream OS providers’ security releases; as of November 9, 2026, the majority of upstream vendors have provided updated kernel packages that include fixes for this vulnerability, and we recommend customers apply those updates to…
- Customer Security Advisory: OpenSSH Password Authentication Bypass Vulnerability [CVE-2026-123158] · Nov 5, 2026, 17:40 UTC · resolved, lasted 0 min
Akamai is aware of the <a href="https://sshhole.com">password authentication bypass vulnerability</a> affecting certain Linux systems using <a href="https://www.openwall.com/lists/musl/2026/11/05/4">musl libc</a> that was recently mitigated by an <a…
- Emerging Host Issue · Nov 5, 2026, 12:58 UTC · resolved, minor impact, lasted 4 h 24 min
We have implemented a fix, and after a period of monitoring, we can confirm that this incident is resolved as of 14:09 UTC on November 5, 2026. If you are still experiencing additional issues, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a>…
- Connectivity Issue - FR-PAR-2 (Paris 2) · Nov 2, 2026, 18:03 UTC · resolved, minor impact, lasted 2 h 50 min
We haven’t observed any additional connectivity issues in our FR-PAR-2 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.
- Connectivity Issue - IN-MAA and IN-BOM-2 · Nov 1, 2026, 16:40 UTC · resolved, lasted 3 h 12 min
This incident has been resolved.
- (PwnEscape) Guest-to-Host KVM Escape [CVE-2026-99999] · Oct 15, 2026, 17:27 UTC · resolved, lasted 357 h 39 min
We have completed our investigation and response to the “PwnEscape” Guest-to-Host Escape vulnerability (CVE-2026-99999). We have published a documentation article with detailed guidance on available mitigations and recommended actions for affected systems:…
- Service Issue - Block Storage (BR-GRU) · Oct 28, 2026, 20:17 UTC · monitoring
A fix has been implemented and we are monitoring the results.
- Connectivity Issue between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2) · Oct 25, 2026, 13:54 UTC · monitoring, minor impact
We will continue to monitor to ensure that the impact has been fully mitigated. Further updates will be provided as we make progress.
- Connectivity Issue - Dallas Data Center (IPv6 Traffic to Google) · Oct 23, 2026, 09:21 UTC · resolved, lasted 11 h 17 min
This issue is considered resolved.
- Customer Security Advisory: PHP Remote Code Execution Vulnerabilities · Oct 21, 2026, 14:44 UTC · postmortem, lasted 53 h 53 min
On October 10, 2026, Akamai became aware of two zero-day remote code execution \(RCE\) vulnerabilities affecting the PHP core engine, tracked as CVE-2026-109618 and CVE-2026-109619. Akamai began a platform-wide investigation, and deployed global Web Application Firewall \(WAF\)…
- Service Issue - Linode Kubernetes Engine · Oct 22, 2026, 13:58 UTC · postmortem, lasted 0 min
On October 22, 2026, starting around 11:10 UTC, a new Debian Kubernetes image was made available. The metadata for that image included malformed data, which resulted in Linode provisioning failures on LKE clusters due to validation errors. Akamai immediately began investigating…
- Issue in creating new LKE Enterprise cluster across regions · Oct 20, 2026, 12:29 UTC · postmortem, minor impact, lasted 9 h 14 min
Starting October 17, 2026, customers were unable to create new Linode Kubernetes Engine-Enterprise \(LKE-E\) clusters globally. The impact was limited to newly provisioned LKE-E clusters, while the existing clusters, ongoing customer workloads, and cluster scaling remained fully…
- Connectivity Issue - US-ORD · Oct 19, 2026, 14:49 UTC · postmortem, lasted 5 h 43 min
Beginning at approximately 14:23 UTC on October 19, 2026, as part of a planned internal maintenance, we migrated too many of the same routing resources at the same time. This resulted in route instability in certain network segments until the migration completed and routes were…
- Maintenance - Akamai Cloud Login Service · Oct 15, 2026, 17:15 UTC · resolved, maintenance impact, lasted 19 h 5 min
The maintenance has been completed. New customer signup and account creation are fully restored.
Source: Linode, Linode’s public status page, read Nov 15, 2026, 08:05 UTC. Uptimely is not affiliated with Linode; incident text is Linode’s own.
Is it down for you, or for everyone?
A status page shows what the vendor has confirmed, which often lags what users see. Run a live check of linode.com to see whether it answers right now.
Get alerted when Linode has an incident
Uptimely’s External Status Page monitor watches Linode’s status page and alerts your team by email, SMS, phone call, Slack, Discord or browser push when it reports a problem, next to the monitors for your own services.
Status of similar services
- Vercel status
- Netlify status
- Render status
- Fly.io status
- DigitalOcean status
- Webflow status
- Squarespace status
- Wix status
Is Linode down right now?
The status at the top of this page is Linode's own, read from its public status page every couple of minutes. It shows what Linode's team has confirmed. For an independent check of whether linode.com answers right now, use the live check on the is-it-down page.
Where is Linode's official status page?
Linode publishes its status at https://status.linode.com. This page shows the same data with the recent incident history in one place, and links each incident to Linode's own write-up.
Why does Linode not work for me when its status says operational?
A status page lists the incidents a vendor has confirmed, and confirmation takes time: problems often reach users minutes before they reach the status page, and some partial or regional problems never appear on it. Your own network, account or region can also be the cause.
How can I get alerted when Linode has an incident?
Add an External Status Page monitor in Uptimely pointed at https://status.linode.com. It reads the page on a schedule and alerts your team by email, SMS, phone call, Slack, Discord or browser push when Linode reports a problem, beside the monitors for your own services.
Verified by the Uptimely team.