Linode incident

Object Storage Key creation and validation failing with error 403 in multiple data centers

Minor Resolved View vendor source →
Started
Apr 29, 2026, 09:22 AM UTC
Resolved
Apr 29, 2026, 07:19 PM UTC
Duration
9h 57m
Detected by Pingoru
Apr 29, 2026, 09:22 AM UTC

Affected components

US-East (Newark) Object StorageUS-Southeast (Atlanta) Object StorageUS-IAD (Washington) Object StorageUS-ORD (Chicago) Object StorageEU-Central (Frankfurt) Object StorageAP-South (Singapore) Object StorageFR-PAR (Paris) Object StorageSE-STO (Stockholm) Object StorageUS-SEA (Seattle) Object StorageJP-OSA (Osaka) Object StorageIN-MAA (Chennai) Object StorageID-CGK (Jakarta) Object StorageBR-GRU (Sao Paulo) Object StorageES-MAD (Madrid) Object StorageGB-LON (London 2)AU-MEL (Melbourne)NL-AMS (Amsterdam) Object StorageIT-MIL (Milan) Object StorageUS-MIA (Miami) Object StorageUS-LAX (Los Angeles) Object StorageGB-LON (London 2) Object StorageAU-MEL (Melbourne) Object StorageIN-BOM-2 (Mumbai 2) Object StorageDE-FRA-2 (Frankfurt 2) Object StorageSG-SIN-2 (Singapore 2) Object StorageJP-TYO-3 (Tokyo 3) Object Storage

Update timeline

  1. investigating Apr 29, 2026, 09:22 AM UTC

    We are aware that some customers have been experiencing 403 (InvalidAccessKeyId) errors when attempting to access object storage, beginning yesterday evening. We will share additional updates as we have more information.

  2. investigating Apr 29, 2026, 10:30 AM UTC

    Our team is investigating an issue affecting the Object Storage service. During this time, users may experience connection timeouts and errors with this service.

  3. investigating Apr 29, 2026, 11:42 AM UTC

    We are continuing to investigate this issue.

  4. investigating Apr 29, 2026, 12:41 PM UTC

    We are continuing to investigate this issue.

  5. resolved Apr 29, 2026, 07:19 PM UTC

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

  6. postmortem Apr 30, 2026, 01:05 PM UTC

    Between approximately 09:15 UTC on April 28, 2026 and 16:54 UTC on April 29, 2026 customers could have experienced issues with their Object Storage key pairs, including: key creation and validation, Object Storage access with their keys. The impact was seen throughout multiple data centers. Our investigation established that the issue started due to a combination of factors, including: a cascading failure of a background process from one cluster to others and a reconciler appliance not running due to missing metrics and an abnormal system load that led to call failures. To resolve the issue, we have restarted the reconciler and key operations were processed for customers. To help prevent similar issues in the future, Akamai will address the cascading failure scenario, add reconciler metrics to prevent the type of outage seen as well enhance queue management to improve reconciler performance. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent recurrence. This summary provides an overview of our current understanding of the incident, given the information available. Our investigation is ongoing, and any information herein is subject to change.

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