Deno’s July 13th incident update
deno.com
Deno’s July 13th incident update
1–10 of 47 posts
Re: Deno’s July 13th incident update
#2Hugops to the team. A quick question: is it intentional that there's nothing on https://denostatus.com/?
Re: Deno’s July 13th incident update
#3Ew, we've had similar issues in the past. These are really messy and confusing to recognize.
In our case, 1 out of 5 LB instances lost its connection to the service discovery and later on ended up not knowing about a failover of one of the 5 backends for a service. As a result, something like 1 in 20 to 1 in 25 requests got answered with a connection refused. That took a minute to find.
Re: Deno’s July 13th incident update
#4Hugops to the team. A quick question: is it intentional that there's nothing on https://denostatus.com/ ?
What would be the benefit for Deno to have an accurate status page? It would only stand to detract potential customers/investors
Re: Deno’s July 13th incident update
#5Hugops to the team. A quick question: is it intentional that there's nothing on https://denostatus.com/ ?
No post body was provided.
Re: Deno’s July 13th incident update
#6Re: Deno’s July 13th incident update
#7Re: Deno’s July 13th incident update
#8Hugops 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.
Re: Deno’s July 13th incident update
#9Hugops to the team. A quick question: is it intentional that there's nothing on https://denostatus.com/ ?
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.