Linode incident
Service Issue - Object Storage - gb-lon (London)
Update timeline
- resolved Feb 04, 2026, 03:35 PM UTC
Starting at 14:43 UTC on February 4, 2026, users in our London (gb-lon) region may have encountered 500 errors when accessing object storage. We identified the issue quickly and resolved it by 15:19 UTC the same day. We apologize for any inconvenience this may have caused. If you are still experiencing issues, please open a Support ticket for assistance.
- postmortem Feb 09, 2026, 07:30 PM UTC
On February 4, 2026, starting at 14:43 UTC, users accessing [gb-lon-1.linodeobjects.com](http://gb-lon-1.linodeobjects.com) experienced increased error rates due to an issue with one of the storage backends supporting the London Object Storage service. During this period, success rates dropped to between 93% and 95%. Our team identified that one of the six storage backends was experiencing problems, which affected service availability. The affected components recovered on their own, and service success rates returned to normal by 15:19 UTC. We are continuing to investigate the underlying cause of the backend issue and will implement additional safeguards to help prevent similar incidents. Thank you for your patience as we work to enhance service reliability. This summary reflects our current understanding of the incident. Our investigation is ongoing, and details may be updated as more information becomes available.
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
5 free monitors · No credit card required