Skip to content

Comment on Deno’s July 13th incident update

Comments

Hugops to the team. A quick question: is it intentional that there's nothing on https://denostatus.com/?

They mentioned that their automated monitoring did not pick up the issue and that they are working on improving the tooling around this.

No, it wasn't intentional. Because the incident was not triggered by automation, the incident on the status page was not automatically created. The team did not remember to update the status page while we were investigating the issue. Sorry for that!

I have retroactively added the outage to the status page now: https://denostatus.com/cl5ob2i5s943266vk890ushwov.

Happens to the best of us :hug: You folks are working on a great product!

What would be the benefit for Deno to have an accurate status page? It would only stand to detract potential customers/investors

They are establishing their brand, transparency, ethics and trust is what should be part of that for what is the next Heroku/Digital Oceam.

You guys took my comment way too literally. It was tongue in cheek :P

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.