At 19:06 UTC on 2017-07-11, Droplet creation was delayed after a deployment of an internal image management service. This change created high load on image replication services, causing new Droplet creates to be delayed.
When the change was reverted, we disabled new Droplet creation and re-enabled them once load on the image services had dropped. In total, 502 users were affected from delayed creates totaling 4,755.
The change to the image replication service increased our replication factor too fast, causing the system to be overloaded while trying to achieve the desired level. Moving forward, we will introduce rate-limiting to ensure that changes like these are handled more gracefully by the system.
In addition, we are working to make sure development and testing environments more closely mirror production, so that we can accurately predict the impact of replication factor changes.
We understand that the delayed creates may have caused interruption to your work or business. We apologize to all of the affected users for this incident.