Deno - Notice history

All systems operational

Notice history

Jun 2026

No notices reported this month

May 2026

Intermittent Request Failures
  • Resolved
    Resolved

    This incident has been resolved.

    The internal service mesh has seen handshake failures between some nodes and we have implemented mitigation measures. We're investigating the root cause for a final fix.

  • Investigating
    Investigating

    We are currently investigating this incident.

    We're seeing again some requests failing with 503 errors with the message `NO_VALID_CLUSTER`

Intermittent Request Failures
  • Resolved
    Resolved

    This incident has been resolved.

    It was caused by some networking changes being rolled out that caused peering instability.

  • Investigating
    Investigating

    Some requests failed to be served with 500 errors and a NO_VALID_CLUSTER error message.

Apr 2026

Degraded performance on Deno Deploy
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    The storage connectivity issue in our Chicago (ord) region has resolved. Traffic has been restored to ord and requests are being served normally. Builds are operational. We are monitoring the cluster for any remaining issues.

  • Identified
    Identified

    We have identified the issue as a storage connectivity problem in our Chicago (ord) region. Traffic has been rerouted to our Amsterdam (ams) region and requests are now being served successfully. Builds may still be affected. We are continuing to work with our infrastructure provider on the underlying issue.

  • Investigating
    Investigating

    We are investigating degraded performance affecting Deno Deploy. Some deployments routed through our Chicago (ord) region are experiencing boot failures and elevated error rates due to an upstream storage connectivity issue.

    Deployments served by other regions are unaffected.

    We are working with our infrastructure provider to resolve the issue and will post updates as they become available.

New builds might take longer to start serving traffic
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified

    Users are experiencing that new builds are not immediately serving traffic after deployment and that traffic continues being served by the previous build.

    We're currently working on a fix for this issue.

Apr 2026 to Jun 2026

Next