rewindex

CompaniesDigitalOceanIncidents

DigitalOcean: Event Processing in AMS3

No impact listedStatus: resolvedStarted Resolved (1.1 h)1 updatestatus.digitalocean.com (opens in new tab)

Timeline of updates

  1. resolved

    As of 01:30 UTC, our Engineering team has confirmed full resolution of the issue with processing events in AMS3 region. All impacted events have been marked as failed and users should now be able to process events normally for Droplets and Droplet-based services like Load Balancers, Kubernetes or Database clusters, etc. If you continue to experience problems, please open a ticket with our support team from your Cloud Control Panel. Thank you for your patience and we apologize for any inconvenience.

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: none) posted by DigitalOcean, started 2023-06-24 00:28 UTC, resolved after 1.1 h, 1 update(s).

Title
Event Processing in AMS3
Vendor
DigitalOcean
Date
URL
https://rewindex.com/company/digitalocean/incidents/vyk14zgrg3kd

DigitalOcean profileRecent DigitalOcean incidentsAll outages on June 24, 2023DigitalOcean in June 2023MarkdownJSON