Vendor record
Linode
Checked
Front door check counts and Linode’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented Linode endpoint and count the checks that got the answer it is documented to give.
Front door reachable in 2,876 of 2,876 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
3 more checks gave no clear answer and are not counted.
- Endpoint checked
- api.linode.com
- Scope
- apiNo vendor region
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Linode product, region or your app worked.
How we count front door checksLinode says
Incident posts from Linode’s status page, with its titles, impact levels and times. They say what Linode chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
7
incidents Linode posted, last 30 days
Median recorded duration: 7h 20m. From 6 incidents with vendor-supplied starts and recorded closure times.
Most recent records · all dates
(PwnEscape) Guest-to-Host KVM Escape [CVE-2026-99999]
Not specifiedLinode’s postStarted, per Linode
Latest status Linode postedIdentified. No resolution posted.
Maintenance - Akamai Cloud Login Service
Not specifiedLinode’s postStarted, per Linode
Closed in our record(19h 15m)
Service Issue - Cloud Manager and API
MinorLinode’s postStarted, per Linode
Closed in our record(4d 4h)
Service Issue - Object Storage - US-Southeast (Atlanta)
MinorLinode’s postStarted, per Linode
Closed in our record(4h 23m)
Service Issue - Cloud Manager and API
MinorLinode’s postStarted, per Linode
Closed in our record(1h 20m)
15 older records
Emerging Service Issue - Cloud Manager and API
MinorLinode’s postStarted, per Linode
Closed in our record(1d 10h)
Emerging Service Issue - [DNS] - [eu-west]
Not specifiedLinode’s postStarted, per Linode
Closed in our record(7h 20m)
Service Issue - Cloud Manager and API
MinorLinode’s postStarted, per Linode
Closed in our record(3h 2m)
Service Issue - US-SEA (Seattle, WA)
Not specifiedLinode’s postStarted, per Linode
Closed in our record(7h 24m)
Service Issue - Object Storage - US-SEA
Not specifiedLinode’s postStarted, per Linode
Closed in our record(3h 27m)
Emerging Service Issue - us-sea (Seattle, WA)
Not specifiedLinode’s postStarted, per Linode
Closed in our record(7m)
Connectivity Issue - IT-MIL (Milan) data center
MinorLinode’s postStarted, per Linode
Closed in our record(1h 26m)
Service Issue - Linode Kubernetes Engine - IAD2 (Washington)
MinorLinode’s postStarted, per Linode
Closed in our record(2h 17m)
Emerging Service Issue - API - All Regions
Not specifiedLinode’s postStarted, per Linode
Closed in our record(5h 44m)
Service Issue - Linode Kubernetes Engine (IAD2)
MinorLinode’s postStarted, per Linode
Closed in our record(14m)
Upstream Issues - Ubuntu
Not specifiedLinode’s postStarted, per Linode
Closed in our record(11d 1h)
Upstream Loss - Some Paths (in-maa/in-bom-2 to US Region)
Not specifiedLinode’s postStarted, per Linode
Closed in our record(4d 7h)
Service Issue - Host Job Performance Degradation - Several Regions
Not specifiedLinode’s postStarted, per Linode
Closed in our record(18h 17m)
Connectivity Issue - Linodes in Milan, Italy
MinorLinode’s postStarted, per Linode
Closed in our record(2h 28m)
Service Issue - Object Storage
MinorLinode’s postStarted, per Linode
Closed in our record(1h 11m)
Your code, your dependencies
See which of your code paths call Linode
Connect GitHub or GitLab to find where your public or private repository uses Linode. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add Linode status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is Linode currently down?
Linode's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did Linode last have an outage?
The most recent closed incident record began 1 day ago and spans 19h 15m. The vendor reported an incident. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for Linode?
No. CheckUpstream checks Linode’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor Linode in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track Linode?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.