Network Connectivity in SFO

Our upstream provider will continue to work to fully resolve this issue, but at this time, we have not been provided an ETA. Until we receive communication from them, traffic will remain shifted away to alternate providers to mitigate user impact.

Due to this, we will go ahead and close out this incident. The traffic shift to reintroduce upstream providers, when it occurs, should be seamless for users in the SFO regions.

If you have any questions or concerns about this or continue to experience network connectivity issues, please open a ticket with our support team from within your Cloud Control Panel.

We have received numerous reports of DNS resolution issues in SFO1 and are now tracking that incident here: https://status.digitalocean.com/incidents/h6yw8yckkcth

At this time, we do not believe the DNS issues in SFO1 are related to this incident. Our upstream provider continues to work to fully resolve the issue, but traffic has remained shifted away from that provider, which mitigated user impact at 20:10 UTC.

If you continue to face network issues to services in SFO1, we invite you to submit a ticket with our Support team, who will be happy to assist.

Our Engineering team began shifting traffic away from the impacted provider at 19:40 UTC and the shift completed at 20:10 UTC, mitigating user impact.

Since 20:10 UTC, users should be seeing normal latency for inbound and outbound traffic to our SFO datacenters.

The upstream provider we partner with continues to work to mitigate the issue, but because traffic has been shifted away, we do not expect further issues.

We'll continue to monitor the situation to confirm this incident is fully resolved and will post an update soon.

Our Engineering team has identified increased packet loss and latency, stemming from an upstream provider, beginning 17:30 UTC. At this time, inbound and outbound traffic from SFO datacenters is impacted. A case has been opened with the provider. We'll post an update as soon as we have more information.