rewindex

CompaniesDigitalOceanIncidents

DigitalOcean: DNS Resolution in SFO1

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatestatus.digitalocean.com (opens in new tab)

Timeline of updates

  1. resolved

    Our Engineering team has confirmed full resolution of this incident. Reports show that from approximately 20:00 UTC on May 8th to 02:30 UTC on May 9th, DNS resolution was inoperative for services in our SFO1 region. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. Resolved: May 09, 2023 - 03:42 UTC - Our Engineering team identified an issue with the path that resolver traffic was taking for our SFO1 region, resulting in services in SFO1 being unable to complete DNS lookups/resolve domains. A fix has been put in place and we've confirmed that DNS resolution is now functioning normally. We're now monitoring the situation and will post an update shortly once we confirm full resolution of this incident. Monitoring: May 09, 2023 - 02:49 UTC - Our Engineering team is investigating user reports of services in our SFO1 region being unable to complete DNS lookups/resolve domains. This includes running commands on Droplets that utilize DNS lookups, such as "wget" and "apt update", etc. Inbound network connections to services should still be operating normally. Thank you for your patience as our team works to understand the root cause of the issue. We'll post an update once we have further information. Investigating: May 09, 2023 - 02:06 UTC - This incident affected: Services (DNS) and Regions (SFO1).

From DigitalOcean’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.digitalocean.com (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by DigitalOcean, started 2023-05-09 02:00 UTC, resolved after 0 min, 1 update(s).

Title
DNS Resolution in SFO1
Vendor
DigitalOcean
Date
URL
https://rewindex.com/company/digitalocean/incidents/jp6lt1bmhx85

DigitalOcean profileRecent DigitalOcean incidentsAll outages on May 9, 2023DigitalOcean in May 2023MarkdownJSON