Degraded performance
Deno Webhooks had degraded performance. Deno reports that this incident is resolved. The incident lasted 33 minutes.
State
Resolved
Started
Lasted
33 min
Worst impact
Degraded
Timeline
2 updatesComponents degraded
33 min 100%
Updates
Times in UTCAs posted by Deno
Affected components
1Deno in the last 90 days
Full historyIncidents in 90 days
3
Days with an incident
2
Median duration
1 h 42 min
This incident
68% shorter than the median
Other Deno incidents
All incidentsDeno·Degraded performance
Deno reports degraded performance for Third Party: GitHub, Git Operations. Deno reports that this incident is resolved. The incident lasted 1 hour and 45 minutes.
Deno·Degraded performance
Deno reports degraded performance for Third Party: GitHub, Git Operations. Deno reports that the incident is resolved. The incident lasted 102 minutes.
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.
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 "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.
https://outages.cc/feed.xml?providers=deno/feed subscribe https://outages.cc/feed.xml?providers=denoFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane