CompaniesDigitalOceanIncidents
DigitalOcean: DNS Resolution for .co TLD
Timeline of updates
- resolved
Our Engineering team has confirmed that the issue affecting the DNS resolution of .co top-level domain (TLD) has been resolved. The DNS resolution for .co domains is now working as expected. We apologize for the inconvenience. If you continue to face any issues, please open a support ticket from within your account.
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: minor) posted by DigitalOcean, started 2026-04-17 21:22 UTC, resolved after 17 h, 1 update(s).
- Title
- DNS Resolution for .co TLD
- Vendor
- DigitalOcean
- Date
- URL
- https://rewindex.com/company/digitalocean/incidents/v6qdbpt1dcd3
DigitalOcean profileRecent DigitalOcean incidentsAll outages on April 17, 2026DigitalOcean in April 2026MarkdownJSON