Linode incident

Emerging Service Issue - Network - London 2(gb-lon)

Major Resolved View vendor source →
Started
Apr 07, 2026, 09:02 AM UTC
Resolved
Apr 08, 2026, 06:32 AM UTC
Duration
21h 30m
Detected by Pingoru
Apr 07, 2026, 09:02 AM UTC

Affected components

GB-LON (London 2)

Update timeline

  1. investigating Apr 07, 2026, 09:02 AM UTC

    Our team is investigating an emerging service issue affecting connectivity to our Linode infrastructure in the London 2(gb-ion) region likely caused due to a upstream AS. We will continue to share more details as we verify this.

  2. monitoring Apr 07, 2026, 10:17 AM UTC

    We've determined that the impact of the issue caused by an upstream AS has been mitigated. We continue to monitor the situation until we recieve further confirmation of the resolution.

  3. resolved Apr 08, 2026, 06:32 AM UTC

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

Looking to track Linode downtime and outages?

Pingoru polls Linode's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Linode reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Linode alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Linode for free

5 free monitors · No credit card required