PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if Linode is down?

PulseWatch evaluates user reports and replay-approved automated evidence for Linode. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported Linode issues today?

As of Sep 28, 2026 10:36 UTC, 0 users had reported issues with Linode in the previous 24 hours.

How can I report a Linode outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Cloud Infrastructure

Is Linode down right now?

UnknownOfficial status last polled Sep 28, 2026 09:43 UTCwww.linode.com Official status page

Are you on the Linode team and see something inaccurate? Report it to us. We respond within one business day.

Is Linode down right now?

Vendor-reported issue. Linode: Service Issue - GPU and VPU Booting issues Affected scope is described in the vendor notice; service-wide impact is not established. Independent corroboration has not been established.

Status as of Sep 28, 2026 10:36 UTC

UnknownVendor-reported issue

Linode: vendor reports an issue

As of Sep 28, 2026 10:36 UTC

Service Issue - GPU and VPU Booting issues Affected scope is described in the vendor notice; service-wide impact is not established. Independent corroboration has not been established.

Checking product coverage. Overall service status has not been established.

Reports 24h

Last incident

Sep 25, 2026 17:33 UTC

Trend

0/15m

Monitoring

Checking coverage

Observed health

Loading…

Current measurements are not available for a health score.

Evidence strength

Vendor-reported

An official notice is available; independent agreement is unproven.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Linode.

Incident days

No recorded incident

35h 23m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Linode. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

1 incident

Busiest day

35h 23m

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Linode outage on September 25 — 1h 57m disruption

Sep 25, 03:36 PM → Sep 25, 05:33 PM · 1h 57m · medium

Linode experienced a service disruption on September 25. This incident was detected through automated monitoring and the vendor's status page. The disruption was resolved on September 25, 2026, at 17:33 UTC.

Peak reports

in 15 min

Total reports

during outage

Duration

1h 57m

until recovery

Impact

During the 1 hour and 57 minute disruption, Linode services experienced a medium severity incident. This incident was identified through automated signals and the vendor's public status page. No user-reported data was collected for this incident, and its impact was assessed based on the duration and severity reported by monitoring systems.

Outage timeline

Sep 25, 03:36 PM
PulseWatch detected the incident from automated vendor and probe signals (medium severity)
Sep 25, 03:36 PM
Status updated: possible issue
Sep 25, 05:33 PM
Signals cleared — incident resolved

Official updates

Sep 25, 03:36 PM
Linode status page acknowledged the incident.
View official source

Reliability

Not measured

30-day uptime

n/a

90-day uptime

n/a

Not calculated: Linode is unknown, so there is no incident history to measure and no uptime figure is shown.

Other cloud infrastructure services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →

ResolvedMedium

Linode: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/25/2026, 3:36:01 PM · 1h 57m

03:36 PM05:33 PM

Detection9/25/2026, 3:36:01 PM · 2d ago

Detected — medium severity

Linode: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

Linode: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/21/2026, 6:38:41 PM · 1d 9h

06:38 PM04:03 AM

Detection9/21/2026, 6:38:41 PM · 6d ago

Detected — medium severity

Linode: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium