Is Linode down right now?
Checking…Verifying live status…
Our latest checks found Linode responding normally. Live verification is running now.
Your report feeds the live outage-velocity detector. One click per 30 s.
Live latency (probe round-trip, ms)
User reports, last 24 hours
Outage history
last 30 days
Recent outages and issues we recorded for Linode, based on our own checks. An episode opens on the second check that finds a problem, since a single adverse reading is not reported, and closes when a check finds the service normal again.
No problemsProblemsOutageNot monitored
What Linode reported
last 30 days
Taken from Linode's own published incident feed. These are their words about their own service, shown here so you can compare them with what we measured. Scheduled maintenance and test posts are filtered out.
Comments
Comments are hosted and moderated via Disqus. Spam is filtered automatically, readers can flag anything, and the thread loads only when you scroll to it so the rest of the page stays fast.
Comments are loading in our built-in box because Disqus was blocked or unavailable. Spam and abuse are filtered automatically, and comments are hidden once 3 readers flag them.
How we check Linode
No evidence of problems with Linode. Our last recorded check found it behaving normally. That does not rule out a fault affecting only some users or regions.
Every check runs a four-tier cascade and stops at the first tier that gives a clear answer: Linode's official status feed, then a direct HTTP probe, then an ICMP network ping, and finally reports from visitors. The Verification tier box above tells you which one produced the verdict you are looking at. When enough separate people report a problem for it to be well outside what Linode normally sees, that counts as evidence too, which is how a partial fault can show here before an operator's own status page catches up.
Linode (linode.com) is re-checked continuously, and this page picks up any change on its own, with no refresh needed.
Common Linode problems users report
- Cannot SSH or connect to running instances
- API calls to manage infrastructure are timing out or returning errors
- Instances are running but unreachable from the internet
- Console access to instances is unavailable
What to do when Linode is not working
First check the banner above. If it shows evidence of problems, the fault is most likely on Linode's side and waiting is usually the only option. If it shows nothing wrong, verify your instance is running in the Linode console, check that your firewall rules and security groups permit inbound traffic, confirm DNS records point to the correct IP address, and try accessing from a different ISP or VPN to rule out routing issues on your path to Linode's network.
About Linode
Linode is a cloud hosting provider offering virtual machines, managed databases, and Kubernetes clusters. When Linode is down, users cannot access their deployed applications, databases become unreachable, and infrastructure management through the console stops working.
Official Linode resources
Cross-check an incident with the company's own channels:
- Official Linode status pageTheir own incident dashboard
- Linode help centerSupport articles and contact options
- @linode on XOften the fastest official acknowledgement
Frequently asked questions
Is Linode down right now?
No. Our checks are finding no problems with Linode right now. That verdict is live, and the banner at the top of this page carries it too. We re-check Linode continuously using its official status feed, direct network probes and reports from visitors, stopping at the first check that gives a clear answer, and the page updates itself as soon as anything changes. A green verdict does not rule out a fault affecting only some users or regions.
What usually goes wrong with Linode?
The problems visitors report most often on this page are can't connect, website / app down, API errors, no response / timing out, high latency, DNS / site unreachable, 5xx error pages and lag or disconnects. Those are the options the report button offers for Linode, chosen for how this service actually fails rather than a generic list, and the "user reports" chart above breaks down which ones people are picking right now.
Why is Linode instances unreachable for me when this page says it is fine?
Our checks run from one place on the internet, so a fault limited to your region or network can be real while our probes succeed. With Linode specifically, a single region or availability zone may be degraded while others function normally, or your instance's network path may be affected while the API remains accessible from your location. That is why this page reports what it observed rather than declaring the service healthy, and why reports from other visitors count toward the verdict.
How do I tell whether it is Linode or my own connection?
For Linode, try pinging or SSH-ing to your instance from a different network, and check the Linode API status endpoint directly with curl to confirm the control plane is responding. A problem that follows you across networks and devices is very unlikely to be yours.
What should I do while Linode is down?
If this page shows evidence of problems, the fault is most likely on Linode's side. Specifically: avoid repeatedly rebooting instances or recreating infrastructure, as queued operations may execute once service recovers and duplicate your changes. Reporting the specific region and instance IDs here helps others identify whether the outage is widespread or localized. Reporting it here helps other people see they are not alone.
How does status.buzz check Linode?
Continuously, around the clock. Linode publishes a machine-readable status feed, so our first check reads it directly and reports what Linode itself says. If that feed is unreachable we fall back to a direct HTTP probe, then an ICMP ping, then reports from visitors. The verification tier box on this page names whichever check produced the verdict you are reading, so you can see how direct the evidence is.
Does Linode have an official status page?
Yes, at status.linode.com, and it is linked further up this page. That is Linode's own account of their service and it is the place to look for their estimate of a fix. We read it where we can, but we publish our own observations beside it rather than only repeating theirs, because an operator's status page can lag a problem their users are already hitting.
Is status.buzz affiliated with Linode?
No. status.buzz is an independent monitoring site operated by LuzLab LLC, with no connection to Linode or linode.com. It reads publicly available endpoints and status feeds, and publishes what it observed. For account or billing problems you need Linode's own support, not us.
No comments yet. Be the first to describe what you're seeing.