Increased errors for S3 API
Runpod · Last saved provider status: reported
The last saved event status is not the current service status. Source lists can be incomplete, and disappearance from a source does not confirm recovery. Open the current report or the official source for newer evidence.
Saved event details
- Provider status
- reported
- Provider impact
- degraded
- Provider record created
- 22 Oct 2026, 21:01:44 UTC
- Provider record updated
- 22 Oct 2026, 21:01:44 UTC
- Explicit provider start
- 22 Oct 2026, 21:01:44 UTC
- Explicit provider end
- Not available
Affected components reported by the provider
Component associations were not provided or have not been recovered for this saved revision.
These associations describe this event’s reported scope. They do not establish current component availability or verified dependencies.
A record creation time is not necessarily an outage start. Unreported times remain unavailable. We do not calculate downtime from collection times.
Runpod's published platform resources and current or upcoming reports. These are provider reports, not independent checks of any model, account or region.
Provider updates in saved revisions
Latest first. We show up to 100 distinct updates from the latest 20 saved content revisions. Revised wording at the same provider time is retained separately.
- published update
We are experiencing an issue with S3 APIs. We are working to resolve it.
Seen in a saved revision at 22 Oct 2026, 21:02:19 UTC