← Live dashboard

Emerging Service Issue - GPU Instances - All Regions

ResolvedminorOfficial source confirmedGlobal service disruptionFirst recorded update Jun 24, 2026, 06:53 PM · Resolved Jun 25, 2026, 07:29 PM

On June 23, 2026, following a global software deployment, we identified an issue causing intermittent boot failures specifically for GPU Linodes. The impact was limited to instances where multiple GPU Linodes attempted to boot simultaneously. During the impact window customers could have experienced localized disruption or elevated error rates, particularly during automated node recycling or scaling events. During the investigation it was found that a recent software update created a conflict when multiple GPU servers tried to start up at the exact same time. The servers essentially...

Linode live status →

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with Linode now? Check the current status

Affected services

US-SEA (Seattle)IN-BOM-2 (Mumbai 2)AU-MEL (Melbourne)JP-TYO-3 (Tokyo 3)MX-QRO (Queretaro)FR-PAR-2 (Paris 2)FR-MRS (Marseille)DE-FRA-2 (Frankfurt 2)US-MIA (Miami)US-DEN (Denver)FR-PAR (Paris)IN-MAA (Chennai)EU-West (London)ID-CGK (Jakarta)ZA-JNB (Johannesburg)US-Southeast (Atlanta)CL-SCL (Santiago)DE-HAM (Hamburg)ES-MAD (Madrid)CO-BOG (Bogota)JP-OSA (Osaka)US-ORD (Chicago)GB-LON (London 2)BR-GRU (São Paulo)US-Central (Dallas)US-East (Newark)US-LAX (Los Angeles)US-West (Fremont)US-IAD-2 (Washington 2)AP-West (Mumbai)AP-South (Singapore)MY-KUL (Kuala Lumpur)AP-Southeast (Sydney)IT-MIL (Milan)SG-SIN-2 (Singapore 2)EU-Central (Frankfurt)CA-Central (Toronto)NZ-AKL (Auckland)SE-STO (Stockholm)US-HOU (Houston)NL-AMS (Amsterdam)US-IAD (Washington)AP-Northeast-2 (Tokyo 2)

Updates (5)

  1. Jun 26, 2026, 06:14 PM
    Emerging Service Issue - GPU Instances - All Regions

    On June 23, 2026, following a global software deployment, we identified an issue causing intermittent boot failures specifically for GPU Linodes. The impact was limited to instances where multiple GPU Linodes attempted to boot simultaneously. During the impact window customers could have experienced localized disruption or elevated error rates, particularly during automated node recycling or scaling events. During the investigation it was found that a recent software update created a conflict when multiple GPU servers tried to start up at the exact same time. The servers essentially blocked o

    Linode ↗
  2. Jun 25, 2026, 07:29 PM
    Emerging Service Issue - GPU Instances - All Regions

    We haven’t observed any additional boot failures on GPU Instances in all regions, and will now consider this incident resolved. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.

    Linode ↗
  3. Jun 24, 2026, 09:12 PM
    Emerging Service Issue - GPU Instances - All Regions

    At 20:32 UTC on June 24th, 2026 we have been able to correct the issue that is causing intermittent boot failures on GPU Instances in all Regions. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.

    Linode ↗
  4. Jun 24, 2026, 08:00 PM
    Emerging Service Issue - GPU Instances - All Regions

    We continue to investigate the issue that is causing intermittent boot failures on GPU Instances in all Regions. We will share additional updates as we have more information.

    Linode ↗
  5. Jun 24, 2026, 06:53 PM
    Emerging Service Issue - GPU Instances - All Regions

    Our team is investigating an emerging service issue that is causing intermittent boot failures on GPU Instances in all Regions. We will share additional updates as we have more information.

    Linode ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow Linode's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.