HenriToivonen on Thu, 05 May 2016 10:32:34
During this night we have suddenly started getting a lot of 504 errors on the https endpoint of our cdn.
Here is an example:
It might work well for a while, and then suddenly again 504 errors.
When its not working, the server is still hosting the file properly:
Here are screenshots of the problem:
I cannot file a support ticket on this since i dont have a support plan, out of ideas here. What's next?
Cam Soper [MSFT] on Thu, 05 May 2016 15:41:15
504 is a gateway timeout. You'll sometimes see this one if your origin server isn't able to serve requests on the specified origin port for some reason. Since your origin is still up and happy, though, I'd guess that it's more likely a localized issue with the POP you're hitting.
It seems to be working now, at least from my location (which is hitting the POP in Dallas, TX, USA). If you're still having the issue, try purging your endpoint.