DigitalOcean Services Status
Event Processing in AMS3
Incident
Report for DigitalOcean
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.
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.
Monitoring
From 23:50 UTC to 00:30 UTC, our Engineering team observed an issue with processing events in our AMS3 region.
Users may have experienced delays or errors while creating and deleting Droplets and Droplet-based products like Load Balancers, Kubernetes or Database clusters, etc. From 00:30 UTC, Users can try performing events/tasks that were failing earlier.
At this time, our Engineering team is monitoring this incident. We will post an update as soon as we have further information.
Users may have experienced delays or errors while creating and deleting Droplets and Droplet-based products like Load Balancers, Kubernetes or Database clusters, etc. From 00:30 UTC, Users can try performing events/tasks that were failing earlier.
At this time, our Engineering team is monitoring this incident. We will post an update as soon as we have further information.
Investigating
Beginning 23:50 UTC, our Engineering team is investigating an issue with processing events in our AMS3 region. During this time users may experience delays or errors while creating and deleting Droplets and Droplet-based products like Load Balancers, Kubernetes, or Database clusters, etc.
As soon as we have further information to share, we'll post an update.
As soon as we have further information to share, we'll post an update.
This incident affected: Event Processing (AMS3).