Only some pages return 502
Curl a URL that works and one that fails. Read both status lines. When the homepage is 200 and one path is 502, the proxy answered and that path's upstream did not.
Read full articleBlog
-
-
Too many redirects
Print the redirect chain and stop when a URL repeats. One hop from HTTP to HTTPS is normal. A loop never returns a status code.
Read full article -
DNS works, the site does not
dig returned an address and the page still does not load. Test the port, then the certificate, then the HTTP status, and stop at the first failure.
Read full article -
When 403 means up
A WAF 403 is not an outage. A 200 with an error payload is. Scan HTTP status codes for website and API checks, and what to set as expected.
Read full article -
Why we ping from different regions
A check from one city only answers “is it down for me?” Multi-region pings separate a global outage from a regional routing problem.
Read full article