Live

Deno

Deno is operational

Checked 2 min ago Operational

User reports

What people told outages.live in the last 24 hours, reviewed before it shows. Not from the Deno status page.

No reviewed reports in the last 24 hours.

History

90 days agoToday

outages.live tracks Deno since Nov 3, 2026. The days before that show only what Deno published.

Incidents in 90 days

0

Days with an incident

0

Median duration

No data

Longest incident

No data

Components

15

Deno Deploy

Console Operational
90 days agoNo incidentsToday
Managed Network Operational
90 days agoNo incidentsToday
API Operational
90 days agoNo incidentsToday
Dashboard Operational
90 days agoNo incidentsToday
Edge Network Operational
90 days agoNo incidentsToday
GitHub Integration Operational
90 days agoNo incidentsToday
KV Operational
90 days agoNo incidentsToday

Module Registry

cdn.deno.land Operational
90 days agoNo incidentsToday
deno.land/std import Operational
90 days agoNo incidentsToday
deno.land/x import Operational
90 days agoNo incidentsToday

Websites

deno.land Operational
90 days agoNo incidentsToday
deno.com Operational
90 days agoNo incidentsToday

Third Party: Github

Github API Operational
90 days agoNo incidentsToday
Webhooks Operational
90 days agoNo incidentsToday
Third Party: GitHub → Git Operations Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

No incident in the last 90 days.

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.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.

RSS
https://outages.cc/feed.xml?providers=deno
Slack
/feed subscribe https://outages.cc/feed.xml?providers=deno

Go from tracking outages to fixing production issues with Polylane.

Try Polylane