Why is this happening, is it token related? (command was executed on different machines with different ip but same token)
doctl -v --trace databases list -o json
doctl: 2024/03/05 13:48:38 [DEBUG] GET https://api.digitalocean.com/v2/databases?page=1&per_page=200
doctl: 2024/03/05 13:48:38 -> "GET /v2/databases?page=1&per_page=200 HTTP/1.1\r\nHost: api.digitalocean.com\r\nUser-Agent: doctl/1.104.0-release (darwin arm64) godo/1.107.0\r\nAccept: application/json\r\nAccept-Encoding: gzip\r\n\r\n"
doctl: 2024/03/05 13:49:24 [DEBUG] GET https://api.digitalocean.com/v2/databases?page=1&per_page=200 (status: 504): retrying in 1s (5 left)
doctl: 2024/03/05 13:50:10 [DEBUG] GET https://api.digitalocean.com/v2/databases?page=1&per_page=200 (status: 504): retrying in 2s (4 left)
doctl: 2024/03/05 13:50:58 [DEBUG] GET https://api.digitalocean.com/v2/databases?page=1&per_page=200 (status: 504): retrying in 4s (3 left)
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Sign up for Infrastructure as a Newsletter.
Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Hey!
Indeed, there was an incident reported on the DigitalOcean status page that affected the Managed Databases Control Plane and API:
The report states that the DigitalOcean engineering team has implemented a fix to resolve the issue with our Managed Databases services. At this time, they are observing error rates returning to pre-incident levels and seeing operations such as create/fork/restore succeed. Trusted sources updates are also functioning normally, so connectivity to Database clusters from newly added resources to trusted sources is restored.
This is now being and I would recommend keeping an eye on the incident page above for further updates.
Sorry for any inconvenience caused!
Best,
Bobby