Deno - Notice history

Webhooks experiencing degraded performance

Notice history

Apr 2022

Degraded performance for our edge network
  • Resolved
    UTC
    Resolved

    We have confirmed the issue is now resolved. Error and latency levels have returned to normal.

  • Monitoring
    UTC
    Monitoring

    We have implemented a fix and currently monitoring the result.

  • Identified
    UTC
    Identified

    We are currently seeing increased error rates and degraded latency for the Deno Deploy edge network. We have identified the root cause and are working on a fix.

Edge Network isn't accessible at the moment
  • Resolved
    UTC
    Resolved

    The issue has been resolved!

  • Investigating
    UTC
    Investigating

    The Deno Deploy edge network cannot be accessed at the moment. We are working on a fix.

Mar 2022

deno.land/x registry - deno.land/std import isn't accessible at the moment (automated)
  • Resolved
    UTC
    Resolved

    deno.land/x registry - deno.land/std import is now operational again.

  • Investigating
    UTC
    Investigating

    deno.land/x registry - deno.land/std import cannot be accessed at the moment. This incident was created by an automated monitoring service.

GitHub outage
  • Resolved
    UTC
    Resolved

    This issue has been resolved.

  • Monitoring
    UTC
    Monitoring

    GitHub has implemented a fix for the outage.

  • Identified
    UTC
    Identified

    GitHub is currently having an outage that is impacting our ability to talk to GitHub's API. This currently is impacting the following:

    • Sign-in with GitHub
    • Automatic GitHub deployments
    • Playground exports
    • Linking of GitHub repositories

    Serving of existing deployments via our edge network is unaffected.

    The situation is unchanged as of 15:25 UTC. Expect another update at 16:15 UTC at latest.

    You can view the GitHub incident status here: https://www.githubstatus.com/incidents/sksd097hm0y5.

Occasional failed deployments
  • Resolved
    UTC
    Resolved

    The issue has been resolved.

  • Monitoring
    UTC
    Monitoring

    We implemented a fix and currently monitoring the result.

  • Identified
    UTC
    Identified

    We have identified the cause of the issue and are working on a fix.

  • Investigating
    UTC
    Investigating

    We are investigating reports of occasional failed deployments. Existing deployments are unaffected.

Feb 2022

No notices reported this month

Feb 2022 to Apr 2022

Next