
Linode Linode Kubernetes Engine Status
Linode Linode Kubernetes Engine is currently operational with all systems functioning normally.
Last checked from Linode Linode Kubernetes Engine's official status page

Linode Linode Kubernetes Engine Status
Part of Linode
Operational
Last updated Loading...•31 sub-components
Service Health — Last 15 days
Uptime
100.0%
15 of 15 days
Last Incident
None
No recent incidents
Incidents
0
All systems operational
Avg Resolution
—
No incidents to measure
Status Timeline
15 days ago — Today
Linode Linode Kubernetes Engine Status Timeline - Last 15 days
- Jan 23
- Jan 23: Operational - No issues reported
- Jan 24
- Jan 24: Operational - No issues reported
- Jan 25
- Jan 25: Operational - No issues reported
- Jan 26
- Jan 26: Operational - No issues reported
- Jan 27
- Jan 27: Operational - No issues reported
- Jan 28
- Jan 28: Operational - No issues reported
- Jan 29
- Jan 29: Operational - No issues reported
- Jan 30
- Jan 30: Operational - No issues reported
- Jan 31
- Jan 31: Operational - No issues reported
- Feb 1
- Feb 1: Operational - No issues reported
- Feb 2
- Feb 2: Operational - No issues reported
- Feb 3
- Feb 3: Operational - No issues reported
- Feb 4
- Feb 4: Operational - No issues reported
- Feb 5
- Feb 5: Operational - No issues reported
- Today
- Today: Operational - No issues reported
Linode Kubernetes Engine Sub-Components
31 sub-components with real-time status monitoring
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 (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) Linode Kubernetes Engine
Operational
BR-GRU (São Paulo) Linode Kubernetes Engine
Operational
NL-AMS (Amsterdam) Linode Kubernetes Engine
Operational
ES-MAD (Madrid) Linode Kubernetes Engine
Operational
IT-MIL (Milan) Linode Kubernetes Engine
Operational
US-MIA (Miami) Linode Kubernetes Engine
Operational
US-LAX (Los Angeles) Linode Kubernetes Engine
Operational
GB-LON (London 2) Linode Kubernetes Engine
Operational
AU-MEL (Melbourne) Linode Kubernetes Engine
Operational
IN-BOM-2 (Mumbai 2) Linode Kubernetes Engine
Operational
DE-FRA-2 (Frankfurt 2) Linode Kubernetes Engine
Operational
SG-SIN-2 (Singapore 2) Linode Kubernetes Engine
Operational
JP-TYO-3 (Tokyo 3) Linode Kubernetes Engine
Operational
Frequently Asked Questions About Linode Linode Kubernetes Engine
Common questions about monitoring Linode Kubernetes Engine and understanding component status