Is Deno Deploy down?

Last checked just now
Current status
Deno Deploy is up

No incidents right now.

Official status page: https://denostatus.com · Polled every 5 minutes · 20 components tracked

Deno Deploy is operational right now. Last checked just now; the most recent incident resolved 29d ago.

Real-time Deno Deploy status, recent outages, and incident history — pulled directly from Deno Deploy's official status page at https://denostatus.com every 5 minutes. Pingoru tracks 20 Deno Deploy services and has captured 14 incidents in the last 90 days (98.33% uptime). Get email, Slack, Discord, or webhook alerts the moment Deno Deploy reports a new incident — free for 5 monitors, no credit card.

Users who monitor Deno Deploy also follow these Development services: Bitbucket OpenAI Datadog US1 Sentry NPM Travis CI Postman Pusher Pendo SonarCloud View all 6,000+ providers
Deno Deploy uptime 98.33% uptime · past 90 days
Mon Wed Fri
MayJunJul
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started Jul 03, 2026, 12:07 AM UTC · Resolved Jul 03, 2026, 12:07 AM UTC
    Timeline · 1 update
    • resolved · Jul 03, 2026, 12:07 AM UTC

      Type: Incident Duration: 2 hours and 53 minutes Affected Components: Managed Network, deno.land, deno.com Jul 3, 00:07:00 GMT+0 - Investigating - Starting around 00:07 UTC, the Deno Deploy Chicago cluster is unreachable. This affects the Deno Deploy managed edge network for visitors routed through that region, impacting a significant portion of global traffic. Because deno.land and deno.com are hosted on Deno Deploy, they may be affected as well. The Deno Deploy console remains available, but builds triggered via GitHub integration, CLI, or API may fail because builds run in Chicago. Sandbox creation in Chicago may also fail. We are investigating. Jul 3, 00:23:08 GMT+0 - Investigating - We are continuing to investigate a major outage affecting deno.com, deno.land, and Deno Deploy managed network traffic. Builds triggered via GitHub integration, CLI, or API may also fail because builds run in Chicago. Sandbox creation in Chicago may also fail. Jul 3, 00:53:15 GMT+0 - Monitoring - The infrastructure problem at one of our cloud providers has been mitigated, and affected services are recovering. We are monitoring for any remaining issues. Jul 3, 00:34:39 GMT+0 - Identified - We have identified the cause as an infrastructure problem at one of our cloud providers. deno.com, deno.land, and Deno Deploy managed network traffic remain impacted while recovery work continues. Jul 3, 03:00:06 GMT+0 - Resolved - The incident has been resolved. deno.com, deno.land, and Deno Deploy managed network traffic have recovered and we are no longer seeing impact.

    Latest: Type: Incident Duration: 2 hours and 53 minutes Affected Components: Managed Network, deno.land, deno.com Jul 3, 00:07:00 GMT+0 - Investigating - Starting around 00:07 UTC, the Den…

  2. Resolved 2h 53m
    Started Jul 03, 2026, 12:07 AM UTC · Resolved Jul 03, 2026, 03:00 AM UTC
    Managed Networkdeno.landdeno.com
    Timeline · 5 updates
    • investigating · Jul 03, 2026, 12:07 AM UTC

      Starting around 00:07 UTC, the Deno Deploy Chicago cluster is unreachable. This affects the Deno Deploy managed edge network for visitors routed through that region, impacting a significant portion of global traffic. Because deno.land and deno.com are hosted on Deno Deploy, they may be affected as well. The Deno Deploy console remains available, but builds triggered via GitHub integration, CLI, or API may fail because builds run in Chicago. Sandbox creation in Chicago may also fail. We are investigating.

    • investigating · Jul 03, 2026, 12:23 AM UTC

      We are continuing to investigate a major outage affecting deno.com, deno.land, and Deno Deploy managed network traffic. Builds triggered via GitHub integration, CLI, or API may also fail because builds run in Chicago. Sandbox creation in Chicago may also fail.

    • identified · Jul 03, 2026, 12:34 AM UTC

      We have identified the cause as a Vultr Chicago infrastructure incident: multiple Kubernetes control plane VPS nodes became unreachable, causing the Deno Deploy Chicago cluster to temporarily lose quorum. Kubernetes quorum has been restored, but Vultr object storage in Chicago is still affected, so recovery is not complete and deno.com, deno.land, and Deno Deploy managed network traffic remain impacted.

    • identified · Jul 03, 2026, 12:53 AM UTC

      We have identified the problem and are working on a fix. deno.com, deno.land, and Deno Deploy managed network traffic remain impacted while recovery work continues.

    • resolved · Jul 03, 2026, 03:00 AM UTC

      The incident has been resolved. deno.com, deno.land, and Deno Deploy managed network traffic have recovered and we are no longer seeing impact.

    Latest: The incident has been resolved. deno.com, deno.land, and Deno Deploy managed network traffic have recovered and we are no longer seeing impact.

  3. Resolved
    Started Jul 01, 2026, 04:25 PM UTC · Resolved Jul 01, 2026, 04:25 PM UTC
    Timeline · 1 update
    • resolved · Jul 01, 2026, 04:25 PM UTC

      Type: Incident Duration: 50 minutes Affected Components: deno.land, Managed Network, deno.com Jul 1, 16:25:00 GMT+0 - Investigating - Starting around 09:25 PDT, the Deno Deploy Chicago cluster experienced an outage. This affected the Deno Deploy managed edge network for visitors routed through that region, impacting a significant portion of global traffic. Because deno.land and deno.com are hosted on Deno Deploy, they were affected as well. The Deno Deploy console remained available, but builds triggered via GitHub integration, CLI, or API were failing because builds run in Chicago. Sandbox creation in Chicago was also failing. Jul 1, 17:15:00 GMT+0 - Monitoring - The Chicago cluster outage was resolved around 10:15 PDT and affected services have recovered. We are continuing to monitor. Jul 1, 17:15:00 GMT+0 - Resolved - This incident has been resolved.

    Latest: Type: Incident Duration: 50 minutes Affected Components: deno.land, Managed Network, deno.com Jul 1, 16:25:00 GMT+0 - Investigating - Starting around 09:25 PDT, the Deno Deploy Chi…

  4. Resolved 50m
    Started Jul 01, 2026, 04:25 PM UTC · Resolved Jul 01, 2026, 05:15 PM UTC
    ConsoleAPIManaged NetworkDashboarddeno.landEdge NetworkGitHub Integrationdeno.com
    Timeline · 3 updates
    • investigating · Jul 01, 2026, 03:30 PM UTC

      We are currently investigating this incident.

    • resolved · Jul 01, 2026, 05:15 PM UTC

      This incident has been resolved.

    • identified · Jul 01, 2026, 05:36 PM UTC

      We are continuing to work on a fix for this incident.

    Latest: We are continuing to work on a fix for this incident.

  5. Resolved 31m
    Started Jun 20, 2026, 09:42 PM UTC · Resolved Jun 20, 2026, 10:13 PM UTC
    ConsoleManaged Networkcdn.deno.landdeno.land/std importdeno.landdeno.land/x importdeno.com
    Timeline · 3 updates
    • investigating · Jun 20, 2026, 09:42 PM UTC

      We are currently investigating this incident.

    • monitoring · Jun 20, 2026, 09:59 PM UTC

      We implemented a fix and are currently monitoring the result.

    • resolved · Jun 20, 2026, 10:13 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

See the full Deno Deploy outage history

9 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Deno Deploy outage history →

Or sign up free to get alerts when Deno Deploy breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 14 incidents View full outage history →