CompaniesDigitalOceanIncidents
DigitalOcean: Managed Kubernetes Connectivity with Internal Droplets
Timeline of updates
- resolved
From March 1st 12:00 UTC to March 10th 18:43 UTC, a subset of users experienced issues connecting Managed Kubernetes nodes to Droplets as a source to allow traffic, due to an issue with tags being applied internally. Some users may also have experienced issues adding Managed Kubernetes Clusters as a source in Cloud firewalls with related Droplets. Our Engineering team has confirmed full resolution of the issue. Users should now be able to connect Managed Kubernetes nodes to Droplets and should also be able to add Managed Kubernetes Cluster as a source in the Cloud Firewall with related Droplets. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel.
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 2025-03-10 12:03 UTC, resolved after 9.8 h, 1 update(s).
- Title
- Managed Kubernetes Connectivity with Internal Droplets
- Vendor
- DigitalOcean
- Date
- URL
- https://rewindex.com/company/digitalocean/incidents/tb0kfpyzty9g
DigitalOcean profileRecent DigitalOcean incidentsAll outages on March 10, 2025DigitalOcean in March 2025MarkdownJSON