Is Linode down today?

Check the status badge at the top of this page for the current status. Pulsetic polls the official status page every few minutes and cross-references with user reports to give you the most accurate picture.

How often does Linode go down?

Based on our 90-day data, we've detected 28 incidents, of which 4 were major or critical. The median resolution time is 8h 53m.

How are outages detected?

Pulsetic polls the official status page every few minutes from multiple global locations. Crowdsourced user reports provide an additional early-warning signal, often surfacing issues before the official monitors catch them.

Is it down for everyone or just me?

The outage map and region breakdown help answer this. If reports are concentrated in one area it may be regional; if hotspots appear globally it's a widespread outage. Submit your own report to help others understand the scope.

What does "never acknowledged" mean?

"Never acknowledged" means Pulsetic detected a real service disruption, confirmed by multiple user reports, but the official status page never posted an incident for it. This is one of the core reasons teams use third-party monitoring alongside official status pages.

ACTIVE INCIDENT DETECTED

Linode is
experiencing issues.

Pulsetic detects outages before the provider officially reports them. Monitoring since Nov 2025 · 64 incidents caught

Last checked: 3 min ago · 0 user reports (24h) · Trusted by 30,000+ teams

Report an outage

MINOR · INVESTIGATING

[Fragnesia] Linux Privilege Escalation Vulnerability

Started 4 weeks ago · May 13, 2026 · 9:02 PM UTC

We are responding to the publication of the most recent variation of the CopyFail[1] adjacent vulnerabilities “DirtyFrag” and “Fragnesia” with additional updates while we wait for upstream OS providers to release patches. Please see our detailed advisory[2] for more information on the current status, possible mitigation mechanisms, and our recommended actions. We will provide another update when more OS images have been updated and/or additional attack vectors are discovered. [1] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/ [2] https://www.linode.com/docs/guides/dirty-frag-mitigation/

View official incident → Having issues too? Let us know →
User Reports: Last 24 Hours
0 reports

Bars represent 20-min intervals. Occasional spikes may reflect individual issues, not widespread outages.

Outage Map
No reports yet

Reports by region (last 24h)

No reports in the last 24h

View full map →
Recent User Reports
Live

Updating in real-time

Top reported issues

Click an issue to upvote it and help us better indicate the service status.

Service outage 0

Degraded performance 0

Error messages 0

Timeouts / no response 0

Authentication issues 0

Network / connectivity issues 0

Feature not working 0

API errors 0

Billing or usage issues 0

Other 0

Have a different problem?
Report an outage
Issue breakdown
0 total votes

Distribution of reported issues over the last 24 hours.

Service outage 0%

Degraded performance 0%

Error messages 0%

Timeouts / no response 0%

Authentication issues 0%

Network / connectivity issues 0%

Feature not working 0%

API errors 0%

Billing or usage issues 0%

Other 0%

Last 90 days

90-Day Health Summary

Total Incidents

28

Since Nov 2025
Major / Critical

4

4 high-impact incidents
Minor Incidents

24

Avg. 0.3 per day
Median Resolution

8h 53m

P95: 130h 25m

Linode Response Time, ms

By Continent

Location List

From official status page

Recent Outage History

View all incidents →

Incident	Started	Duration	Impact	Status	Link
Emerging Service Issue - LKE Enterprise - All Regions	Jun 5, 2026 · 2:23 PM	35m	None	Resolved	Details →
Emerging Service Issue - Support Phone Line	Jun 3, 2026 · 2:22 PM	1d 1h 29m	None	Resolved	Details →
Service Issue - Block Storage Newark, US	Jun 3, 2026 · 8:58 AM	1d 13m	Minor	Postmortem	Details →
Linode Community Maintenance	Jun 2, 2026 · 1:26 AM	6d 18h 9m	Maintenance	Resolved	Details →
Service Issue - Object Storage	May 29, 2026 · 6:23 PM	< 1m	None	Postmortem	Details →
Service Issue - Paris (FR-PAR3)	May 22, 2026 · 11:22 AM	3d 18h 52m	Minor	Postmortem	Details →
Emerging Service Issue - GPU Deployment	May 19, 2026 · 7:48 PM	4h 38m	None	Postmortem	Details →
Service Issue - [Linodes and Linode Kubernetes Engine (LKE)] - [All Regions]	May 16, 2026 · 12:42 AM	1h 1m	None	Postmortem	Details →
Investigating - Linode VM Migration Delays (All Regions)	May 15, 2026 · 2:24 AM	1h 27m	None	Postmortem	Details →
[Fragnesia] Linux Privilege Escalation Vulnerability	May 13, 2026 · 9:02 PM	Ongoing	Minor	Investigating	Details →

How do they compare?

Alternatives to Linode

DigitalOcean

Cloud hosting

Online 8 incidents / 30d
Compare →
OVHcloud

Cloud hosting

Online 0 incidents / 30d
Compare →
UpCloud

Cloud hosting

Online 2 incidents / 30d
Compare →

Teams monitoring Linode also watch

Other Monitored Services

Get alerted the moment Linode goes down.

No credit card · free plan · 2-minute setup

Start Free Trial

Common questions

Frequently Asked Questions

Is Linode down today?

Check the status badge at the top of this page for the current status. Pulsetic polls the official status page every few minutes and cross-references with user reports to give you the most accurate picture.
How often does Linode go down?

Based on our 90-day data, we've detected 28 incidents, of which 4 were major or critical. The median resolution time is 8h 53m.
How are outages detected?

Pulsetic polls the official status page every few minutes from multiple global locations. Crowdsourced user reports provide an additional early-warning signal, often surfacing issues before the official monitors catch them.
Is it down for everyone or just me?

The outage map and region breakdown help answer this. If reports are concentrated in one area it may be regional; if hotspots appear globally it's a widespread outage. Submit your own report to help others understand the scope.
What does "never acknowledged" mean?

"Never acknowledged" means Pulsetic detected a real service disruption, confirmed by multiple user reports, but the official status page never posted an incident for it. This is one of the core reasons teams use third-party monitoring alongside official status pages.