zlacker

>>gruseo+(OP)
Never let a good crisis go to waste: I'm launching https://20-things.com/ :) Could use a good load test ;)

>>dt3ft+51
Just got Cloudflare Error 522, Our work is done here HN, next one please.

>>kamyar+D6
That can't be right though. The box is fairly strong :) I believe that CF may have a new IP range which accesses origins, and I white-listed their known ranges a few months ago. Perhaps this calls for an update to that whitelist.

>>dt3ft+48
> That can't be right though.

Unsolicited advice, but please don't have this mindset towards system failure. More things go wrong than you anticipate.

>>random+se
Thank you for your advice, I appreciate it. I did examine everything that came to mind and the only thing at this point that may be happening is cloudflare -> origin connectivity for some users. I am using a keyword based monitoring since day one and so far no issues with reachability have been detected. This could be related to CF Geo firewall (disabled, but perhaps caching on CF side need to expire?). The only way I can verify CF<->Origin connectivity is by paying for CF a Pro account with Origin health check feature. If you have any ideas/suggestions how to troubleshoot this, I would be happy to hear them. Thanks!