Elevated timeouts for dashboard, CLI, and API
This incident has been resolved.
The latest update from Doppler.
State
Resolved
Started
5 d ago
2026-10-27 19:26 UTC
Lasted
59 min
until 2026-10-27 20:25 UTC
Worst impact
Degraded
Timeline
5 updatesInvestigating
4 min 7%
Identified
45 min 76%
Monitoring
10 min 17%
Updates
Times in UTCAs posted by Doppler
This incident has been resolved.
A fix has been deployed and we are monitoring the results.
We're continuing to work toward resolution. A fix has been prepared and will be deployed shortly.
We've identified the cause of the increased timeout rate and are working toward resolving it.
We are currently investigating this issue.
Affected components
2Doppler in the last 90 days
Full historyIncidents in 90 days
1
Days with an incident
1
Median duration
59 min
This incident
About the median
Follow Doppler
Your coding agent knows when Doppler is down, and tells you when a failure is theirs, not yours. You can also get Doppler incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "doppler" and tell me if Doppler has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=doppler/feed subscribe https://outages.cc/feed.xml?providers=dopplerFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane