rewindex

CompaniesDigitalOceanIncidents

DigitalOcean: Kubernetes Clusters in NYC3

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

Timeline of updates

  1. resolved

    Impact: minor; As of 01:00 UTC, our Engineering team has confirmed the full resolution of the issue impacting our managed Kubernetes service in the NYC3 region. All operations for clusters should now be functioning normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience. Affected Components: Services - Kubernetes Regions - NYC3 Status: resolved 2023-04-07 02:27 UTC - Our Engineering team has deployed a fix for the issue impacting our Managed Kubernetes service in the NYC3 region. As of 17:50 UTC, all impact has been mitigated and users should no longer experience any issues with our managed Kubernetes service in the NYC3 region. We are monitoring the situation and will post an update once the incident is completely resolved. Affected Components: Services - Kubernetes Regions - NYC3 Status: monitoring 2023-04-06 17:58 UTC - Our Engineering team is investigating an issue with Kubernetes clusters in the NYC3 region. During this time, a subset of users will experience errors while communicating with their clusters in the NYC3 region. Specifically, as of 14:10 UTC, users will be unable to load the Kubernetes Dashboard in the Cloud Control Panel, see errors when accessing via kubectl, and/or see unauthorized/500 errors when attempting to establish connectivity. Any prior workloads running on the cluster are not affected by this incident. Users will not be able to deploy new workloads. We apologize for the inconvenience and will share an update once we have more information. Affected Components: Services - Kubernetes Regions - NYC3 Status: investigating 2023-04-06 16:43 UTC - Incident Created at: 2023-04-06 16:43 UTC Resolved at: 2023-04-07 02:27 UTC

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-04-06 16:43 UTC, resolved after 0 min, 1 update(s).

Title
Kubernetes Clusters in NYC3
Vendor
DigitalOcean
Date
URL
https://rewindex.com/company/digitalocean/incidents/b22q1wvbh40p

DigitalOcean profileRecent DigitalOcean incidentsAll outages on April 6, 2023DigitalOcean in April 2023MarkdownJSON