Intermittent 522: Cloudflare TLS -> Azure LB -> Azure AKS
Our Cloudflare-proxied TLS requests started having intermittent 522 earlier this week, and had to turn off proxying due to failing assets.
These issues all disappear when proxying is turned off or if users hardcode IPs on their local hosts files.
The majority of our ingress logs show response timings of less than 1 second. And peak at 8 seconds, which indicate that there are no performance issues on origin.
We've also gone through the 522 guide, but we cant find anything concerning so far
https://developers.cloudflare.com/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522/
We initially assumed it was due to a recent maintenance in MEL, but issues persisted even after that window.
Anyone in 🇦🇺 or anyone have any experience in between Azure and Cloudflare recently?
Cloudflare Docs
Error 522
Error 522 occurs when Cloudflare times out contacting the origin web server.
1 Reply
Thanks @Leo will revisit browser traces
You were right @Leo I couln't test MTR from Azure to Cloudflare ATM, but found that there is indeed some packet loss even direct to Azure. Sent support MTR traces. Thanks again.
Now its just hearing back from support
Ah thats nifty
Am just on business tier ATM
Thanks! Yeah was in a sales call with them recently like the nice rate limiting and discovery bits