DigitalOcean Services Status
Droplet Resize Events
Incident
Report for DigitalOcean
Resolved
Impact: minor;
As of 09:04 UTC, our Engineering team has confirmed the full resolution of the issue processing Droplet Resize events in NYC1, NYC3, SGP1, TOR1 and BLR1 regions.
If you continue to experience problems, please open a ticket with our Support team. Thank you for your patience and we apologize for the inconvenience.
Affected Components: Services - Event Processing Regions - BLR1 Regions - NYC1 Regions - NYC3 Regions - TOR1
Status: resolved
2022-11-02 10:37 UTC
-
Our Engineering team took action to mitigate the issues leading to delays in resize event processing. Users should no longer see any delays in processing resize events in the NYC1, NYC3, SGP1, TOR1, and BLR1 regions. We're now monitoring the situation closely and will post an update as soon as the problem appears to be fully resolved.
Affected Components: Services - Event Processing Regions - BLR1 Regions - NYC1 Regions - NYC3 Regions - TOR1
Status: monitoring
2022-11-02 09:26 UTC
-
Our Engineering team believes they have found the root cause of the issue and are working on implementing a fix. Once that fix is implemented users should no longer see any delays in processing resize events in the NYC1, NYC3, SGP1, TOR1, and BLR1 regions. We apologize for the inconvenience and will share an update once we have more information.
Affected Components: Services - Event Processing Regions - BLR1 Regions - NYC1 Regions - NYC3 Regions - TOR1
Status: identified
2022-11-02 08:25 UTC
-
As of 01:00 UTC, our Engineering team is investigating an issue that is currently leading to Droplet resize events taking longer than usual in the NYC1, NYC3, SGP1, TOR1, and BLR1 regions. Users may experience delayed processing when attempting to resize Droplets in all the listed regions. We apologize for the inconvenience and will share an update once we have more information.
Affected Components: Services - Event Processing Regions - BLR1 Regions - NYC1 Regions - NYC3 Regions - TOR1
Status: investigating
2022-11-02 07:51 UTC
-
Incident Created at: 2022-11-02 07:51 UTC Resolved at: 2022-11-02 10:37 UTC
As of 09:04 UTC, our Engineering team has confirmed the full resolution of the issue processing Droplet Resize events in NYC1, NYC3, SGP1, TOR1 and BLR1 regions.
If you continue to experience problems, please open a ticket with our Support team. Thank you for your patience and we apologize for the inconvenience.
Affected Components: Services - Event Processing Regions - BLR1 Regions - NYC1 Regions - NYC3 Regions - TOR1
Status: resolved
2022-11-02 10:37 UTC
-
Our Engineering team took action to mitigate the issues leading to delays in resize event processing. Users should no longer see any delays in processing resize events in the NYC1, NYC3, SGP1, TOR1, and BLR1 regions. We're now monitoring the situation closely and will post an update as soon as the problem appears to be fully resolved.
Affected Components: Services - Event Processing Regions - BLR1 Regions - NYC1 Regions - NYC3 Regions - TOR1
Status: monitoring
2022-11-02 09:26 UTC
-
Our Engineering team believes they have found the root cause of the issue and are working on implementing a fix. Once that fix is implemented users should no longer see any delays in processing resize events in the NYC1, NYC3, SGP1, TOR1, and BLR1 regions. We apologize for the inconvenience and will share an update once we have more information.
Affected Components: Services - Event Processing Regions - BLR1 Regions - NYC1 Regions - NYC3 Regions - TOR1
Status: identified
2022-11-02 08:25 UTC
-
As of 01:00 UTC, our Engineering team is investigating an issue that is currently leading to Droplet resize events taking longer than usual in the NYC1, NYC3, SGP1, TOR1, and BLR1 regions. Users may experience delayed processing when attempting to resize Droplets in all the listed regions. We apologize for the inconvenience and will share an update once we have more information.
Affected Components: Services - Event Processing Regions - BLR1 Regions - NYC1 Regions - NYC3 Regions - TOR1
Status: investigating
2022-11-02 07:51 UTC
-
Incident Created at: 2022-11-02 07:51 UTC Resolved at: 2022-11-02 10:37 UTC