Loading status…
Loading status…
Linode status · Cloud & Infrastructure · checked (2m ago)
Also searched as Akamai Linode, Akamai Cloud.
No — Linode is not down. All Linode systems are reported operational.
According to Linode's official status page, Linode was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Linode's feed reported no outage in 100.00% of our checks.
Everything above is read from Linode's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Linode in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Linode, now part of Akamai, provides virtual machines, managed Kubernetes, object storage, block storage and managed databases across a set of global datacentres.
Linode's status page reports per datacentre — Newark, Frankfurt, Singapore and the rest — as well as by product, and that regional structure is how it should be read: an incident is almost always confined to one facility. Network and storage incidents are listed separately from compute, because they are different layers and fail apart from each other.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Linode's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Linode was down.
9 other services isuptime tracks were also reporting a problem as of the same check, 2m ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Linode's status endpoint.
Linode has published 50 incidents in the last 12 months, the 20 most recent shown here. Only what Linode posted itself — not every problem users hit.
resolved · Sep 21, 05:13 PM (2d ago)
resolved · Sep 21, 04:50 PM (2d ago)
postmortem · Sep 7, 10:38 AM (16d ago)
postmortem · Aug 28, 10:26 AM (26d ago)
resolved · Aug 24, 09:52 PM (29d ago)
postmortem · Aug 21, 05:23 PM (32d ago)
postmortem · Aug 14, 08:13 PM (39d ago)
postmortem · Aug 13, 09:13 PM (40d ago)
postmortem · Aug 13, 06:46 PM (40d ago)
postmortem · Aug 13, 04:16 PM (41d ago)
postmortem · Aug 13, 02:00 PM (41d ago)
resolved · Aug 10, 05:15 PM (44d ago)
postmortem · Jul 31, 05:49 PM (53d ago)
postmortem · Jul 28, 06:14 PM (56d ago)
postmortem · Jul 20, 01:52 AM (65d ago)
postmortem · Jul 18, 03:34 AM (67d ago)
resolved · Jul 16, 01:24 AM (69d ago)
postmortem · Jul 14, 12:21 PM (71d ago)
resolved · Jul 13, 06:29 PM (71d ago)
postmortem · Jul 9, 04:57 PM (76d ago)
Use Lish, the out-of-band console, to reach an instance that will not answer SSH — it works when networking on the instance does not. A full disk or an out-of-memory kill will take down SSH while the host stays healthy. Check the firewall rules and whether the instance is actually running before treating it as a platform issue.
Linode is reporting no problems right now. If it stops, these cover the same job — each shows its own live status.
Status shown for each is read from that provider's own feed, on the same schedule as this page.