Skip to main content
Vendor reliability

Vendor record

Linode

Vendor reports Operational

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 checks

Linode 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.

26

incidents Linode posted, last 1 year

Median recorded duration: 5h 44m. From 25 incidents with vendor-supplied starts and recorded closure times.

All vendors’ incidents

Most recent records · all dates

  • (PwnEscape) Guest-to-Host KVM Escape [CVE-2026-99999]

    Not specified

    Started, per Linode

    Latest status Linode postedIdentified. No resolution posted.

    Linode’s post

  • Maintenance - Akamai Cloud Login Service

    Not specified

    Started, per Linode

    Closed in our record(19h 15m)

    Linode’s post

  • Service Issue - Cloud Manager and API

    Minor

    Started, per Linode

    Closed in our record(4d 4h)

    Linode’s post

  • Service Issue - Object Storage - US-Southeast (Atlanta)

    Minor

    Started, per Linode

    Closed in our record(4h 23m)

    Linode’s post

  • Service Issue - Cloud Manager and API

    Minor

    Started, per Linode

    Closed in our record(1h 20m)

    Linode’s post
15 older records

  • Emerging Service Issue - Cloud Manager and API

    Minor

    Started, per Linode

    Closed in our record(1d 10h)

    Linode’s post

  • Emerging Service Issue - [DNS] - [eu-west]

    Not specified

    Started, per Linode

    Closed in our record(7h 20m)

    Linode’s post

  • Service Issue - Cloud Manager and API

    Minor

    Started, per Linode

    Closed in our record(3h 2m)

    Linode’s post

  • Service Issue - US-SEA (Seattle, WA)

    Not specified

    Started, per Linode

    Closed in our record(7h 24m)

    Linode’s post

  • Service Issue - Object Storage - US-SEA

    Not specified

    Started, per Linode

    Closed in our record(3h 27m)

    Linode’s post

  • Emerging Service Issue - us-sea (Seattle, WA)

    Not specified

    Started, per Linode

    Closed in our record(7m)

    Linode’s post

  • Connectivity Issue - IT-MIL (Milan) data center

    Minor

    Started, per Linode

    Closed in our record(1h 26m)

    Linode’s post

  • Service Issue - Linode Kubernetes Engine - IAD2 (Washington)

    Minor

    Started, per Linode

    Closed in our record(2h 17m)

    Linode’s post

  • Emerging Service Issue - API - All Regions

    Not specified

    Started, per Linode

    Closed in our record(5h 44m)

    Linode’s post

  • Service Issue - Linode Kubernetes Engine (IAD2)

    Minor

    Started, per Linode

    Closed in our record(14m)

    Linode’s post

  • Upstream Issues - Ubuntu

    Not specified

    Started, per Linode

    Closed in our record(11d 1h)

    Linode’s post

  • Upstream Loss - Some Paths (in-maa/in-bom-2 to US Region)

    Not specified

    Started, per Linode

    Closed in our record(4d 7h)

    Linode’s post

  • Service Issue - Host Job Performance Degradation - Several Regions

    Not specified

    Started, per Linode

    Closed in our record(18h 17m)

    Linode’s post

  • Connectivity Issue - Linodes in Milan, Italy

    Minor

    Started, per Linode

    Closed in our record(2h 28m)

    Linode’s post

  • Service Issue - Object Storage

    Minor

    Started, per Linode

    Closed in our record(1h 11m)

    Linode’s post

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.

Connect a repository

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.

Appearance
Detail
Preview · LinodeStatus only

For HTML pages that permit CheckUpstream frames. Loads a snapshot; reload the containing page for a newer reading. Theme and detail settings apply to this format.

Iframe snippet
<iframe src="https://checkupstream.com/embed/linode?layout=card" style="border:0;width:320px;max-width:100%;height:96px" loading="lazy" title="Linode status badge"></iframe>

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.

Related vendors