Degraded performance
DegradedOfficial update
0
Deno reports degraded performance for Git Operations in the Third Party: GitHub component. The incident started at 21:00 UTC on 3 November 2026. Deno continues to investigate the problem.
State
Components degraded
Started
Ongoing for
1 h 22 min
Worst impact
Degraded
Timeline
1 update21:0021:2021:4122:0122:22
DegradedUpdate postedTimes in UTC
Components degraded
1 h 22 min 100%
Updates
Times in UTCAs posted by Deno
Components degraded
Affected components
1Third Party: GitHub → Git Operations
Deno in the last 90 days
Full history90 days agoToday
Incidents in 90 days
1
Days with an incident
1
Median duration
Not enough data
This incident
Not comparable
Follow Deno
Your coding agent knows when Deno is down, and tells you when a failure is theirs, not yours. You can also get Deno 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.live/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 "deno" and tell me if Deno 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.live/feed.xml?providers=denoSlack
/feed subscribe https://outages.live/feed.xml?providers=denoFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane