Is Linode down?

Last checked 4m ago
Current status
Linode has degraded performance

2 active incidents: Object Storage Key creation and validation failing with err…, Service Issue - Connectivity Issues - Chennai (IN-MAA)

Get alerts when Linode breaks →

Free · no credit card

Official status page: https://status.linode.com · Polled every 5 minutes · 239 components tracked

Real-time Linode status, recent outages, and incident history — pulled directly from Linode's official status page at https://status.linode.com every 5 minutes. Pingoru tracks 239 Linode services and has captured 34 incidents in the last 90 days (98.89% uptime). Get email, Slack, Discord, or webhook alerts the moment Linode reports a new incident — free for 5 monitors, no credit card.

Users who monitor Linode also follow these Cloud Infrastructure services: Amazon Web Services DigitalOcean Cisco Umbrella Wasabi Vercel Hetzner HashiCorp Egnyte Dyn Genesys Cloud View all 6,000+ providers
Linode uptime 98.89% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. Object Storage Key creation and validation failing with error 403 in multiple data centers
    Ongoing ● 7h 54m
    Started Apr 29, 2026, 09:22 AM UTC
    US-East (Newark) Object StorageUS-Southeast (Atlanta) Object StorageUS-IAD (Washington) Object StorageUS-ORD (Chicago) Object StorageEU-Central (Frankfurt) Object StorageAP-South (Singapore) Object StorageFR-PAR (Paris) Object StorageSE-STO (Stockholm) Object StorageUS-SEA (Seattle) Object StorageJP-OSA (Osaka) Object Storage
    4 updates · show timeline
    • investigating · Apr 29, 2026, 09:22 AM UTC

      We are aware that some customers have been experiencing 403 (InvalidAccessKeyId) errors when attempting to access object storage, beginning yesterday evening. We will share additional updates as we have more information.

    • investigating · Apr 29, 2026, 10:30 AM UTC

      Our team is investigating an issue affecting the Object Storage service. During this time, users may experience connection timeouts and errors with this service.

    • investigating · Apr 29, 2026, 11:42 AM UTC

      We are continuing to investigate this issue.

    • investigating · Apr 29, 2026, 12:41 PM UTC

      We are continuing to investigate this issue.

    Latest: We are continuing to investigate this issue.

  2. Service Issue - Connectivity Issues - Chennai (IN-MAA)
    Ongoing ● 23h 58m
    Started Apr 28, 2026, 05:17 PM UTC
    IN-MAA (Chennai)
    2 updates · show timeline
    • identified · Apr 28, 2026, 05:17 PM UTC

      Our team is investigating an emerging service issue affecting the network and connectivity in our Chennai (IN-MAA) data center. Customers may see intermittent delays and timeouts during peak traffic hours in the region. If you are seeing impact that may be related, please open a Support Ticket.

    • identified · Apr 28, 2026, 09:35 PM UTC

      Our team has identified the issue affecting connectivity in our Chennai (IN-MAA) data center as a degraded network component and are working to expedite replacement as quickly as possible. At this time there is no customer impact, but due to lessened capacity as a result of this hardware degradation, we do expect intermittent delays or timeouts during peak traffic hours in the Chennai (IN-MAA) region. The current ETA for replacing this hardware is end of day on April 29, 2026. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

    Latest: Our team has identified the issue affecting connectivity in our Chennai (IN-MAA) data center as a degraded network component and are working to expedite replacement as quickly as p…

  3. Service Issue - Linode Kubernetes Engine (LKE)
    Resolved 3d 19h
    Started Apr 24, 2026, 07:27 PM UTC · Resolved Apr 28, 2026, 03:16 PM UTC
    US-East (Newark) NodeBalancersUS-East (Newark) Linode Kubernetes EngineUS-Central (Dallas) NodeBalancersUS-Central (Dallas) Linode Kubernetes EngineUS-West (Fremont) NodeBalancersUS-West (Fremont) Linode Kubernetes EngineUS-Southeast (Atlanta) NodeBalancersUS-Southeast (Atlanta) Linode Kubernetes EngineUS-IAD (Washington) NodeBalancersUS-IAD (Washington) Linode Kubernetes Engine
    8 updates · show timeline
    • investigating · Apr 24, 2026, 07:27 PM UTC

      Our team is investigating an emerging service issue affecting the Linode Kubernetes Engine (LKE) service across multiple regions. We will share additional updates as we have more information.

    • identified · Apr 24, 2026, 08:19 PM UTC

      Our team has identified the issue affecting the LKE service. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

    • identified · Apr 24, 2026, 08:48 PM UTC

      Our team has identified that due to this issue, customers may also experience issues creating new nodebalancers. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

    • identified · Apr 24, 2026, 09:46 PM UTC

      Our team has identified the issue affecting the LKE and newly updated/created NodeBalancer configurations. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

    • identified · Apr 24, 2026, 10:07 PM UTC

      We are continuing work to apply the identified fix the issue affecting the LKE and newly updated/created NodeBalancer configurations and we will provide an update as soon as the solution is in place.

    • identified · Apr 24, 2026, 11:06 PM UTC

      We are continuing work to apply the identified fix the issue affecting the LKE and newly updated/created NodeBalancer configurations and we will provide an update as soon as the solution is in place.

    • monitoring · Apr 24, 2026, 11:53 PM UTC

      At this time we have been able to correct the issues affecting the NodeBalancer service at 23:36 UTC on April 24, 2026. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a ticket with our Support Team.

    • resolved · Apr 28, 2026, 03:16 PM UTC

      We haven’t observed any additional issues with the LKE and NodeBalancer services and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

    Latest: We haven’t observed any additional issues with the LKE and NodeBalancer services and will now consider this incident resolved. If you continue to experience problems, please open a…

See the full Linode outage history

28 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Sign up free to unlock full history

10 free monitors · No credit card

Outage history

Past 30 days · 10 incidents
  • Object Storage Key creation and validation failing with error 403 in multiple data centers Ongoing
    Started Apr 29, 2026, 09:22 AM UTC · ● 7h 54m
  • Service Issue - Connectivity Issues - Chennai (IN-MAA) Ongoing
    Started Apr 28, 2026, 05:17 PM UTC · ● 23h 58m
  • Service Issue - Linode Kubernetes Engine (LKE) Resolved
    Started Apr 24, 2026, 07:27 PM UTC · Resolved Apr 28, 2026, 03:16 PM UTC · 3d 19h
  • Emerging Service Issue - Connectivity issues in Frankfurt (DE-FRA-2) Resolved
    Started Apr 20, 2026, 11:49 AM UTC · Resolved Apr 21, 2026, 01:08 AM UTC · 13h 19m
  • Linode Kubernetes Engine Standard and Enterprise provisioning failures in all regions Resolved
    Started Apr 16, 2026, 01:20 PM UTC · Resolved Apr 17, 2026, 01:30 PM UTC · 1d
  • Service Issue - Cloud Manager and API Resolved
    Started Apr 15, 2026, 04:57 PM UTC · Resolved Apr 15, 2026, 08:21 PM UTC · 3h 23m
  • Service Issue - Dedicated CPU - Several Regions Resolved
    Started Apr 14, 2026, 06:33 PM UTC · Resolved Apr 16, 2026, 07:32 PM UTC · 2d
  • Service Issue - Networking in US-IAD (Washington) Resolved
    Started Apr 09, 2026, 11:32 PM UTC · Resolved Apr 10, 2026, 02:31 AM UTC · 2h 58m

See Linode in your Pingoru dashboard

Monitor Linode alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add Linode to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every Linode incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just Linode or see every provider at once.

Maintenance calendar

Scheduled Linode maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every Linode status change, one inbox

Pingoru watches Linode's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

Linode reports on 239 services. Subscribe to the ones you actually use — everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route Linode alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming Linode maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy Linode services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching Linode from the same account, with per-user notification preferences for any monitor.

Get notified on Linode status changes

Pingoru watches Linode's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring Linode free

Monitor Linode along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add Linode and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track Linode uptime & incident history

See 90 days of Linode uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See Linode uptime history

Frequently asked questions

What is Linode's uptime?
Over the last 90 days, Linode reported 98.89% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.linode.com — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Linode's uptime history rolling forward in real time.
Has Linode had outages in 2026?
Yes — Linode has had 31 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last Linode outage?
The most recent Linode incident was "Service Issue - Linode Kubernetes Engine (LKE)", which started on April 24, 2026 and was resolved on April 28, 2026. Pingoru captured this directly from https://status.linode.com. See the full incident card above for affected components and the update timeline.
How often does Linode have outages?
Based on the last 90 days, Linode averages 10.3 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is Linode's status page?
Linode's official status page is https://status.linode.com. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.
Is Linode down right now?
Linode has degraded performance. Pingoru checks the official status page every 5 minutes and flips this headline the moment Linode reports a change. Current status is based on 239 tracked services.
How does Pingoru know if Linode is down?
We read https://status.linode.com directly, using Linode's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.
Where can I get notified when Linode has an outage?
Create a free Pingoru account and add Linode as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
Linode's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real Linode incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Linode issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.
Where does Pingoru get the official Linode status?
We use Linode's own status page at https://status.linode.com. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.
What does "Degraded" mean?
Linode is reporting degraded performance — services are up but slower than usual, or a subset of requests is failing.

Stop finding out from your users.

We watch Linode's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor Linode free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →