Where does this status come from?

From Deno Deploy's own status page API at https://denostatus.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Deno Deploy's words.

How can my agent or app check Deno Deploy status?

Fetch https://upbutler.com/status/deno/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"deno"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Deno Deploy's?

Add "deno" to the dependencies of your UpButler workspace. When one of your monitors fails while Deno Deploy has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Deno Deploy down?

Right now

No. Deno Deploy is operational.

No incidents reported.

Read from denostatus.com 4 min ago · every 120s

For agents

proceed

Proceed.

GET upbutler.com/status/deno/status.agent.json

MCP: upstream_status {"service":"deno"}

Deno Deploy, Deno KV and the JSR registry.

What Deno Deploy reports

Operational

Taken as is from Deno Deploy's own status page API. Incident titles and component names below are theirs.

Open denostatus.com

UpButler's independent probe

There is no keyless endpoint of Deno Deploy that says anything useful, so UpButler does not probe it. To check your own Deno Deploy account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Deno Deploy components

20 operational

Deno DeployOperational
Deno Deploy ClassicOperational
Module RegistryOperational
WebsitesOperational
Third Party: GithubOperational

Deno Deploy

ConsoleOperational
Managed NetworkOperational

Deno Deploy Classic

APIOperational
DashboardOperational
Edge NetworkOperational
GitHub IntegrationOperational
KVOperational

Module Registry

cdn.deno.landOperational
deno.land/std importOperational
deno.land/x importOperational

Websites

deno.landOperational
deno.comOperational

Third Party: Github

Github APIOperational
WebhooksOperational
Third Party: GitHub → Git OperationsOperational

Deno Deploy incidents, last 90 days

No finished incidents on record yet. UpButler keeps what Deno Deploy publishes for 90 days from the day it starts tracking a service.

Tell your outage from Deno Deploy's

Declare that your project depends on Deno Deploy. When one of your monitors fails while Deno Deploy has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - deno

Ask before you retry

curl -s https://upbutler.com/status/deno/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "deno",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Deno Deploy down right now?: No. As of 2026-10-10 05:09 UTC, Deno Deploy is operational. This page reads the status again every 2 minutes.
Where does this status come from?: From Deno Deploy's own status page API at https://denostatus.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Deno Deploy's words.
How can my agent or app check Deno Deploy status?: Fetch https://upbutler.com/status/deno/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"deno"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Deno Deploy's?: Add "deno" to the dependencies of your UpButler workspace. When one of your monitors fails while Deno Deploy has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in hosting and compute

UpButler is not affiliated with Deno Deploy. Status and incident text belong to Deno Deploy and are read from their public status source; the probe result is UpButler's own measurement.