Linode logo

Is Linode down?

Minor issues reported

From status.linode.com · checked 41 seconds ago · every 5 minutes

Get alerts for Linode

An email when it goes down, and when it’s back.

As of 03:31 UTC on 12 November 2026, Linode's status page reports minor issues.

Last problem
Going on now
Problems, last 30 days
2
Typical incident
4 days
Longest in 90 days
4 days · 9 Oct

Connectivity Issue between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2)

Issue

Started 18 days ago.

Read the updates on status.linode.com ↗

Uptime

Linode, last 30 days

35.7 %

100%50%0%
Oct 14 Today

Biggest dip: Linode, 421.5 h of issue on Oct 25.

Incidents

Started in the last 7 days

0

210
FSSMTWToday

This week Week before

No incidents this week. The last one: Linode, issue on Oct 25.

Recovery

Median time back online

9 h 11 min

9 h 11 min0
30 days ago Today

0 of 1 were over within an hour. Each dot is one incident; the dashed line is the median.

Components 243

All online

  • Linode.com
  • Cloud Manager and API
  • Hosted DNS Service
  • Longview
  • Managed Databases
Regions 43 parts
  • US-East (Newark)
  • US-Central (Dallas)
  • US-West (Fremont)
  • US-Southeast (Atlanta)
  • US-IAD (Washington)
  • US-ORD (Chicago)
  • CA-Central (Toronto)
  • EU-West (London)
  • EU-Central (Frankfurt)
  • FR-PAR (Paris)
  • AP-South (Singapore)
  • AP-Northeast-2 (Tokyo 2)
  • AP-West (Mumbai)
  • AP-Southeast (Sydney)
  • SE-STO (Stockholm)
  • US-SEA (Seattle)
  • IT-MIL (Milan)
  • JP-OSA (Osaka)
  • IN-MAA (Chennai)
  • ID-CGK (Jakarta)
  • BR-GRU (São Paulo)
  • NL-AMS (Amsterdam)
  • US-MIA (Miami)
  • US-LAX (Los Angeles)
  • ES-MAD (Madrid)
  • AU-MEL (Melbourne)
  • GB-LON (London 2)
  • IN-BOM-2 (Mumbai 2)
  • SG-SIN-2 (Singapore 2)
  • DE-FRA-2 (Frankfurt 2)
  • JP-TYO-3 (Tokyo 3)
  • ZA-JNB (Johannesburg)
  • NZ-AKL (Auckland)
  • CO-BOG (Bogota)
  • US-DEN (Denver)
  • DE-HAM (Hamburg)
  • US-HOU (Houston)
  • MY-KUL (Kuala Lumpur)
  • FR-MRS (Marseille)
  • MX-QRO (Queretaro)
  • CL-SCL (Santiago)
  • FR-PAR-2 (Paris 2)
  • US-IAD-2 (Washington 2)
Block Storage 31 parts
  • US-East (Newark) Block Storage
  • US-Central (Dallas) Block Storage
  • US-West (Fremont) Block Storage
  • US-Southeast (Atlanta) Block Storage
  • US-IAD (Washington) Block Storage
  • US-ORD (Chicago) Block Storage
  • CA-Central (Toronto) Block Storage
  • EU-West (London) Block Storage
  • EU-Central (Frankfurt) Block Storage
  • FR-PAR (Paris) Block Storage
  • AP-South (Singapore) Block Storage
  • AP-Northeast-2 (Tokyo 2) Block Storage
  • AP-West (Mumbai) Block Storage
  • AP-Southeast (Sydney) Block Storage
  • SE-STO (Stockholm) Block Storage
  • US-SEA (Seattle) Block Storage
  • JP-OSA (Osaka) Block Storage
  • IN-MAA (Chennai) Block Storage
  • BR-GRU (São Paulo) Block Storage
  • NL-AMS (Amsterdam) Block Storage
  • ES-MAD (Madrid) Block Storage
  • IT-MIL (Milan) Block Storage
  • US-MIA (Miami) Block Storage
  • ID-CGK (Jakarta) Block Storage
  • US-LAX (Los Angeles) Block Storage
  • GB-LON (London 2) Block Storage
  • AU-MEL (Melbourne) Block Storage
  • IN-BOM-2 (Mumbai 2) Block Storage
  • DE-FRA-2 (Frankfurt 2) Block Storage
  • SG-SIN-2 (Singapore 2) Block Storage
  • JP-TYO-3 (Tokyo 3) Block Storage
NodeBalancers 31 parts
  • US-East (Newark) NodeBalancers
  • US-Central (Dallas) NodeBalancers
  • US-West (Fremont) NodeBalancers
  • US-Southeast (Atlanta) NodeBalancers
  • US-IAD (Washington) NodeBalancers
  • US-ORD (Chicago) NodeBalancers
  • CA-Central (Toronto) NodeBalancers
  • EU-West (London) NodeBalancers
  • EU-Central (Frankfurt) NodeBalancers
  • FR-PAR (Paris) NodeBalancers
  • AP-South (Singapore) NodeBalancers
  • AP-Northeast-2 (Tokyo 2) NodeBalancers
  • AP-West (Mumbai) NodeBalancers
  • AP-Southeast (Sydney) NodeBalancers
  • SE-STO (Stockholm) NodeBalancers
  • US-SEA (Seattle) NodeBalancers
  • JP-OSA (Osaka) NodeBalancers
  • IN-MAA (Chennai) NodeBalancers
  • BR-GRU (São Paulo) NodeBalancers
  • NL-AMS (Amsterdam) NodeBalancers
  • ES-MAD (Madrid) NodeBalancers
  • IT-MIL (Milan) NodeBalancers
  • US-MIA (Miami) NodeBalancers
  • ID-CGK (Jakarta) NodeBalancers
  • US-LAX (Los Angeles) NodeBalancers
  • GB-LON (London 2) NodeBalancers
  • AU-MEL (Melbourne) NodeBalancers
  • IN-BOM-2 (Mumbai 2) NodeBalancers
  • DE-FRA-2 (Frankfurt 2) NodeBalancers
  • SG-SIN-2 (Singapore 2) NodeBalancers
  • JP-TYO-3 (Tokyo 3) NodeBalancers
Backups 31 parts
  • US-East (Newark) Backups
  • US-Central (Dallas) Backups
  • US-West (Fremont) Backups
  • US-Southeast (Atlanta) Backups
  • US-IAD (Washington) Backups
  • US-ORD (Chicago) Backups
  • CA-Central (Toronto) Backups
  • EU-West (London) Backups
  • EU-Central (Frankfurt) Backups
  • FR-PAR (Paris) Backups
  • AP-South (Singapore) Backups
  • AP-Northeast-2 (Tokyo 2) Backups
  • AP-West (Mumbai) Backups
  • AP-Southeast (Sydney) Backups
  • SE-STO (Stockholm) Backups
  • US-SEA (Seattle) Backups
  • JP-OSA (Osaka) Backups
  • IN-MAA (Chennai) Backups
  • BR-GRU (São Paulo) Backups
  • NL-AMS (Amsterdam) Backups
  • ES-MAD (Madrid) Backups
  • IT-MIL (Milan) Backups
  • US-MIA (Miami) Backups
  • ID-CGK (Jakarta) Backups
  • US-LAX (Los Angeles) Backups
  • GB-LON (London 2) Backups
  • AU-MEL (Melbourne) Backups
  • IN-BOM-2 (Mumbai 2) Backups
  • DE-FRA-2 (Frankfurt 2) Backups
  • SG-SIN-2 (Singapore 2) Backups
  • JP-TYO-3 (Tokyo) Backups
Object Storage 26 parts
  • US-East (Newark) Object Storage
  • US-Southeast (Atlanta) Object Storage
  • US-IAD (Washington) Object Storage
  • US-ORD (Chicago) Object Storage
  • EU-Central (Frankfurt) Object Storage
  • AP-South (Singapore) Object Storage
  • FR-PAR (Paris) Object Storage
  • SE-STO (Stockholm) Object Storage
  • US-SEA (Seattle) Object Storage
  • JP-OSA (Osaka) Object Storage
  • IN-MAA (Chennai) Object Storage
  • ID-CGK (Jakarta) Object Storage
  • BR-GRU (Sao Paulo) Object Storage
  • ES-MAD (Madrid) Object Storage
  • GB-LON (London 2)
  • AU-MEL (Melbourne)
  • NL-AMS (Amsterdam) Object Storage
  • IT-MIL (Milan) Object Storage
  • US-MIA (Miami) Object Storage
  • US-LAX (Los Angeles) Object Storage
  • GB-LON (London 2) Object Storage
  • AU-MEL (Melbourne) Object Storage
  • IN-BOM-2 (Mumbai 2) Object Storage
  • DE-FRA-2 (Frankfurt 2) Object Storage
  • SG-SIN-2 (Singapore 2) Object Storage
  • JP-TYO-3 (Tokyo 3) Object Storage
Linode Kubernetes Engine 31 parts
  • US-East (Newark) Linode Kubernetes Engine
  • US-Central (Dallas) Linode Kubernetes Engine
  • US-West (Fremont) Linode Kubernetes Engine
  • US-Southeast (Atlanta) Linode Kubernetes Engine
  • US-IAD (Washington) Linode Kubernetes Engine
  • US-ORD (Chicago) Linode Kubernetes Engine
  • CA-Central (Toronto) Linode Kubernetes Engine
  • EU-West (London) Linode Kubernetes Engine
  • EU-Central (Frankfurt) Linode Kubernetes Engine
  • FR-PAR (Paris) Linode Kubernetes Engine
  • AP-South (Singapore) Linode Kubernetes Engine
  • AP-Northeast (Tokyo 2) Linode Kubernetes Engine
  • AP-West (Mumbai) Linode Kubernetes Engine
  • AP-Southeast (Sydney) Linode Kubernetes Engine
  • SE-STO (Stockholm) Linode Kubernetes Engine
  • US-SEA (Seattle) Linode Kubernetes Engine
  • JP-OSA (Osaka) Linode Kubernetes Engine
  • IN-MAA (Chennai) Linode Kubernetes Engine
  • ID-CGK (Jakarta) Linode Kubernetes Engine
  • BR-GRU (São Paulo) Linode Kubernetes Engine
  • NL-AMS (Amsterdam) Linode Kubernetes Engine
  • ES-MAD (Madrid) Linode Kubernetes Engine
  • IT-MIL (Milan) Linode Kubernetes Engine
  • US-MIA (Miami) Linode Kubernetes Engine
  • US-LAX (Los Angeles) Linode Kubernetes Engine
  • GB-LON (London 2) Linode Kubernetes Engine
  • AU-MEL (Melbourne) Linode Kubernetes Engine
  • IN-BOM-2 (Mumbai 2) Linode Kubernetes Engine
  • DE-FRA-2 (Frankfurt 2) Linode Kubernetes Engine
  • SG-SIN-2 (Singapore 2) Linode Kubernetes Engine
  • JP-TYO-3 (Tokyo 3) Linode Kubernetes Engine
Metadata Service 41 parts
  • US-East (Newark)
  • US-Central (Dallas)
  • US-West (Fremont)
  • US-Southeast (Atlanta)
  • US-IAD (Washington)
  • US-ORD (Chicago)
  • CA-Central (Toronto)
  • EU-West (London)
  • EU-Central (Frankfurt)
  • FR-PAR (Paris)
  • AP-South (Singapore)
  • AP-Northeast-2 (Tokyo 2)
  • AP-West (Mumbai)
  • AP-Southeast (Sydney)
  • SE-STO (Stockholm)
  • US-SEA (Seattle)
  • IT-MIL (Milan)
  • JP-OSA (Osaka)
  • IN-MAA (Chennai)
  • ID-CGK (Jakarta)
  • BR-GRU (São Paulo)
  • NL-AMS (Amsterdam)
  • US-MIA (Miami)
  • US-LAX (Los Angeles)
  • ES-MAD (Madrid)
  • AU-MEL (Melbourne)
  • GB-LON (London 2)
  • IN-BOM-2 (Mumbai 2)
  • SG-SIN-2 (Singapore 2)
  • DE-FRA-2 (Frankfurt 2)
  • JP-TYO-3 (Tokyo 3)
  • ZA-JNB (Johannesburg)
  • NZ-AKL (Auckland)
  • CO-BOG (Bogota)
  • US-DEN (Denver)
  • DE-HAM (Hamburg)
  • US-HOU (Houston)
  • MY-KUL (Kuala Lumpur)
  • FR-MRS (Marseille)
  • MX-QRO (Queretaro)
  • CL-SCL (Santiago)
Observability 3 parts
  • Akamai Cloud Pulse (ACLP) - Alerts
  • Akamai Cloud Pulse (ACLP) - Logs
  • Akamai Cloud Pulse (ACLP) - Metrics
Customer Service, Documentation and Community 1 part
  • Customer Security Advisory

Last 90 days

4 incidents in 48 days tracked · no reported issues 25.3% of the time · typical incident 4 days

Aug 15 Today (UTC)

Recent incidents

Times in UTC

  1. Issue
    Issue in creating new LKE Enterprise cluster across regions. 9 h 11 min
  2. Maintenance
    Maintenance - Akamai Cloud Login Service 19 h 2 min
  3. Issue
    Service Issue - Cloud Manager and API 4 days
  4. Issue
    Service Issue - GPU and VPU Booting issues and 1 more at least 12 days
All incidents on status.linode.com ↗

Where this comes from

Stackpulse reads Linode’s official status page at status.linode.com every 5 minutes and keeps 90 days of what changed. We don’t test Linode ourselves, so a problem shows here once Linode reports it.

Stackpulse isn’t affiliated with Linode. Names and logos belong to their owners.

For agents and scripts

The same data as Markdown for AI agents, updated every 30 seconds. With Pro, the API and the MCP server give scripts and AI assistants every service and your own dashboards.