CompaniesDigitalOceanIncidents
DigitalOcean: 503 errors in SGP1 region
Timeline of updates
- resolved
From 17:02 - 18:44 UTC, the Spaces API experienced availability dips. These dips caused Spaces bucket operations in SGP1 for a subset of users to experience latency or 503 errors. The fix implemented by our Engineering team has been monitored and availability for the Spaces API is stable. Users should be able to interact with their Spaces buckets successfully. If you continue to experience any issues, please reach out to the Support team from within your account.
From DigitalOcean’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.digitalocean.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by DigitalOcean, started 2024-06-17 18:49 UTC, resolved after 48 min, 1 update(s).
- Title
- 503 errors in SGP1 region
- Vendor
- DigitalOcean
- Date
- URL
- https://rewindex.com/company/digitalocean/incidents/lcdn900frz8z
DigitalOcean profileRecent DigitalOcean incidentsAll outages on June 17, 2024DigitalOcean in June 2024MarkdownJSON