Hacker News Reader

Comment by capableweb | Hacker News Reader

A great first step would be to take responsibility for what the customer has proven to happen. "It is definitively not the case that doing" is directly at odds with what the author provides, you might want to reframe your message to "it shouldn't be like this but unfortunately it is like this right now, sorry" rather than dismissing the author with that they are not correct.

View on HN

You shouldn't assume that he is correct either; i'm a free plan user and have never experienced this

If you're on free plan you have no way to know if this has happened to your website.

> no way

you can (and should) put monitors on the outside of your infrastructure as well as inside. I've multiples hitting the login page and robots file where I work, and never got an unaccounted 503

Like I wrote, for some integrations it is not possible to gather all the logs. Also how will you know that a client accessing your website in a browser gets 503 instead of your web page?

You don't, but your monitors will show the 503 happening, how often, on which endpoint operation and in which regions; that will give you a pretty good picture of whether is actually your CDN layer or something else triggering the 503

What if it's a specific browser with a specific TLS stack, or something weird?

what if it's green lizard man chewing cables?

one has to start somewhere reasonable and realistic first.

But, I thought in your case you did know something was wrong: client complained and you saw 503 errors?

I am taking responsibility for what the customer is reporting here.

I think they are taking your use of "would" literally, and not reading it as an implied "should".

Proven is a strong word and rate limiting is not the only possible explanation. Something is happening and we don't know what.

Reply on news.ycombinator.com