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

Affected components

• AP-South (Singapore) Object Storage
• AU-MEL (Melbourne)
• AU-MEL (Melbourne) Object Storage
• BR-GRU (Sao Paulo) Object Storage
• DE-FRA-2 (Frankfurt 2) Object Storage
• ES-MAD (Madrid) Object Storage
• EU-Central (Frankfurt) Object Storage
• FR-PAR (Paris) Object Storage
• GB-LON (London 2)
• GB-LON (London 2) Object Storage
• ID-CGK (Jakarta) Object Storage
• IN-BOM-2 (Mumbai 2) Object Storage
• IN-MAA (Chennai) Object Storage
• IT-MIL (Milan) Object Storage
• JP-OSA (Osaka) Object Storage
• JP-TYO-3 (Tokyo 3) Object Storage
• NL-AMS (Amsterdam) Object Storage
• SE-STO (Stockholm) Object Storage
• SG-SIN-2 (Singapore 2) Object Storage
• US-East (Newark) Object Storage
• US-IAD (Washington) Object Storage
• US-LAX (Los Angeles) Object Storage
• US-MIA (Miami) Object Storage
• US-ORD (Chicago) Object Storage
• US-SEA (Seattle) Object Storage

1. postmortemApr 30, 2026, 13:05 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 c

2. resolvedApr 29, 2026, 19:19 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 <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.

3. investigatingApr 29, 2026, 12:41 UTC

   We are continuing to investigate this issue.

4. investigatingApr 29, 2026, 11:42 UTC

   We are continuing to investigate this issue.

5. investigatingApr 29, 2026, 10:30 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.

6. investigatingApr 29, 2026, 09:22 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Linode's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Snyk: Snyk recurring tests showing slow performanceMinor · Apr 21, 2026, 18:58 UTC
• GitHub: Incomplete pull request results in repositoriesMinor · Apr 28, 2026, 14:17 UTC
• Akamai: Intermittent Edge Delivery Delays in Chennai, IN (MAA) RegionMinor · Apr 28, 2026, 16:42 UTC
• Akamai: Reporting Issues affecting URL Traffic and URL Responses reportsMinor · Apr 29, 2026, 05:19 UTC
• Amplitude: Data Processing DelaysMinor · Apr 29, 2026, 08:15 UTC
• Snyk: Reports PDF Export DegradedMinor · Apr 29, 2026, 15:43 UTC
• npm: Degraded Performance in View Package and Login on npmjs.comMinor · Apr 29, 2026, 16:48 UTC

How often does Linode have incidents?

Linode reported 10 incidents in the last 90 days. A typical incident lasted 2h 15m. See Linode's uptime and incident history