Deno Deploy

First posted only after it was over

0% 0 of the 25 incidents we have in full detailbetterworse

The first update already said resolved. Typical vendor: 6%.

Deno Deploy: lower than most vendors.

Time to resolve

2 h 53 min median; 9 in 10 within 2.6 daysbetterworse

From the vendor’s own start and resolve times, last 365 days. Typical vendor: 2 h.

Deno Deploy: around the middle.

Major or critical incidents

0.0 a month 0 in the last 365 daysbetterworse

Impact as the vendor labels it. Typical vendor: 1.2 a month.

Deno Deploy: lower than most vendors.

Rewrites caught

None so far

Counts, not a rate: 10-minute tracking began Oct 17, so there are too few events to compare yet.

Deno Deploy depends on

Outage events: AWS us-east-1, Oct 20, 2025 (timing).

Strong: same company, or blamed in two separate outages. Likely: blamed once, or named as hosting and failing together. Weak: listed as a subprocessor, integration-only, or failing together repeatedly without being named.

No notable changes yet. We compare every snapshot of Deno Deploy’s status page (taken every 10 minutes) and its 0 tracked pages.

Full Deno Deploy change history

No pricing, trust or legal pages tracked for Deno Deploy.

Each change links to its diff: the changed passages with a few words of context, never a full copy of the page.

Deno Deploy incidents, last 90 daysJSONMarkdown