Our Engineering team has seen no recurrences and performance has remained stable since 16:40 UTC. This incident is fully resolved.
If you continue to experience problems, please open a ticket with our support team. Thank you for your patience!
Posted Nov 08, 2023 - 18:07 UTC
Our Engineering team identified a configuration that was responsible for the recurrence we saw. From 16:20 - 16:40 UTC, connectivity between SFO2 and the rest of DigitalOcean's network was impacted.
As of 16:40 UTC, all impact has subsided and users should no longer face any issues.
We are monitoring the situation closely and will share an update once the issue is completely resolved.
Posted Nov 08, 2023 - 17:23 UTC
Our Engineering team is seeing a recurrence of network alerts that indicate we're experiencing worsening performance on these paths once more. They are currently investigating and we'll provide an update soon.
Posted Nov 08, 2023 - 16:32 UTC
Our Engineering team has completed adding the additional networking paths and we are starting to observe recovery across our services. At this time, users should be seeing restoration of connectivity and less latency/packet loss.
Posted Nov 08, 2023 - 16:01 UTC
Our Engineering team has identified heavy loss originating from an upstream provider. They are working to add additional networking paths on an alternate provider to help alleviate customer impact, as well as reaching out to the impacted provider for further details.
We will post another update once the additional paths are in place or we have an update from the impacted provider.
Posted Nov 08, 2023 - 15:27 UTC
As of 14:19 UTC, our Engineering team is investigating reports of connectivity issues, including loss and latency, on network paths between our NYC and SFO regions. Some users may experience increased latency/packet loss on traffic traversing paths between NYC and SFO, or connectivity issues on Droplets and Droplet-based services.
We apologize for the inconvenience and will share an update once we have more information.
Posted Nov 08, 2023 - 15:08 UTC
This incident affected: Networking (NYC1, NYC2, NYC3, SFO1, SFO2, SFO3).