6 comments

[ 3.2 ms ] story [ 26.8 ms ] thread
I had a blip about 40 minutes ago for around 4 minutes, where an internal IP for a redis server failed to connect, and didn't failover to the backup node... which is just excellent.

Hoping it's a small issue & resolved quickly

They took time to add the incident to their status page, appears to be fine now after 10:13 UTC.
I still get "Health check: unavailable" errors and need to continously redeploy.
Just moved from fly.io (due to severe continuous networking issues in their JNB data center lasting for 48 hours) to DigitalOcean and on the second day my services (via DO Apps Platform) are offline thanks to this incident :face-palm:
Around 11am BST everything I have in LON1 across all DO services (droplets, Kubernetes, App Platform) disappeared for about 10 minutes.

It resolved but is now showing intermittent issues an hour later.

It's the first DigitalOcean incident in memory that has caused me any problems though.

Still having issues in some regions.