Legacy API Keys

Our engineering team has deployed the fix. As of 22:53 UTC users should no longer experience issues with the Managed databases, Kubernetes, and API. We're monitoring the fix and will post an update once we confirm this incident is fully resolved.

Our engineering team is currently rolling out a fix for the issue with API keys in to resolve the impacts with Managed databases, Kubernetes, and API. As soon as the rollout has completed we will provide an update. Thank you very much for your patience and we apologize for the inconvenience.

Our engineering team has identified an impact to managed databases, Kubernetes, and API. This is in addition to the issue impacting Legacy API keys on our platform. Currently, users might face issues creating new Managed databases, performing select actions with Kubernetes, and performing general actions using the DigitalOcean API. We will provide an update as soon as information is available. We apologize for the inconvenience.

Our engineering team is currently investigating an issue regarding connections to the DigitalOcean API using legacy API keys. At this time users with old style API keys may experience some issues connecting to the API. We apologize for the inconvenience and will share an update once we have more information.