Partially Degraded Service
ResolvedOfficial update
0
Doppler reports a partially degraded service that affects ReadMe Hubs. Doppler states that the incident is resolved. The outage lasted 96 minutes.
State
Resolved
Started
2 h ago
2026-11-02 22:45 UTC
Lasted
1 h 36 min
until 2026-11-03 00:21 UTC
Worst impact
Degraded
Timeline
2 updates22:4523:0923:3323:5700:21
DegradedUpdate postedTimes in UTC
Components degraded
1 h 36 min 100%
Updates
Times in UTCAs posted by Doppler
Resolved2026-11-03 00:21 UTC
Components degraded2026-11-02 22:45 UTC
Affected components
1ReadMe ReadMe Hubs
Doppler in the last 90 days
Full history90 days agoToday
Incidents in 90 days
2
Days with an incident
3
Median duration
1 h 18 min
This incident
1.2× the median
Other Doppler incidents
All incidentsFollow 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.
Prompt
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.
RSS
https://outages.cc/feed.xml?providers=dopplerSlack
/feed subscribe https://outages.cc/feed.xml?providers=dopplerFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane