Vendor record
Deno Deploy
Checked
Front door check counts and Deno Deploy’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented Deno Deploy endpoint and count the checks that got the answer it is documented to give.
Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
- Endpoint checked
- api.deno.com
- Scope
- apiNo vendor region
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Deno Deploy product, region or your app worked.
How we count front door checksDeno Deploy says
Incident posts from Deno Deploy’s status page, with its titles, impact levels and times. They say what Deno Deploy chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
9
incidents Deno Deploy posted, last 180 days
Median recorded duration: 3h 3m. From 9 incidents with vendor-supplied starts and recorded closure times.
Most recent records · all dates
Deno Deploy request failures in ord
Not specifiedDeno Deploy’s postStarted, per Deno Deploy
Closed in our record(1h 16m)
Deno Deploy Chicago cluster outage
Not specifiedDeno Deploy’s postStarted, per Deno Deploy
Closed in our record(3h 3m)
Edge network outage in Chicago
Not specifiedDeno Deploy’s postStarted, per Deno Deploy
Closed in our record(3h 30m)
Deno Deploy Outage
Not specifiedDeno Deploy’s postStarted, per Deno Deploy
Closed in our record(38m)
Deno Deploy Console - Slow to respond
Not specifiedDeno Deploy’s postStarted, per Deno Deploy
Closed in our record(18m)
4 older records
Registering new and renew existing custom domains
Not specifiedDeno Deploy’s postStarted, per Deno Deploy
Closed in our record(3h 20m)
Intermittent Request Failures
Not specifiedDeno Deploy’s postStarted, per Deno Deploy
Closed in our record(41m)
Degraded performance on Deno Deploy
Not specifiedDeno Deploy’s postStarted, per Deno Deploy
Closed in our record(2d 11h)
New builds might take longer to start serving traffic
Not specifiedDeno Deploy’s postStarted, per Deno Deploy
Closed in our record(3d 2h)
Your code, your dependencies
See which of your code paths call Deno Deploy
Connect GitHub or GitLab to find where your public or private repository uses Deno Deploy. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add Deno Deploy status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is Deno Deploy currently down?
Deno Deploy's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did Deno Deploy last have an outage?
The most recent closed incident record began 39 days ago and spans 1h 16m. The vendor reported an incident. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for Deno Deploy?
No. CheckUpstream checks Deno Deploy’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor Deno Deploy in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track Deno Deploy?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.