TROUBLESHOOTING GUIDE
What do 403, 429, 502 and 503 errors mean?
An HTTP error means a server or intermediary returned a response. The number narrows the investigation, but does not identify the underlying cause by itself. Record the code, time and action instead of repeatedly retrying a failed transaction.
Reviewed
Likely causes
An access rule, request limit, missing page, overloaded service or upstream failure can produce an error response. The page may come from a CDN or proxy rather than the website application itself.
Steps for visitors
Change one thing at a time. Keep certificate warnings, firewalls and other security protections in place. Ask your administrator before changing a managed network.
403: access was refused
Check that the address is correct and that you are using the intended account. Follow the website’s normal access process.
What the result means: The server understood the request but refused it. This is not proof that the whole website is down; automated checkers may also be refused.
429: too many requests
Stop repeated retries and follow any Retry-After instruction. Allow the service time before another ordinary request.
What the result means: A rate limit has been applied. It may relate to a shared connection or an account; switching identities to evade it is not a diagnosis.
502 or 504: investigate the upstream path
Check official incident information and wait briefly. If a payment failed, confirm its state before attempting it again.
What the result means: A gateway received an invalid upstream response or did not receive one in time. The code alone does not identify which dependency failed.
503: service temporarily unavailable
Look for a maintenance message or retry instruction. Record the time and contact the operator if the problem persists.
What the result means: The server is currently unable to handle the request. A later successful request does not establish the duration or scope of an incident.
Our checker makes a request from our server. It cannot test your Wi-Fi, account or every website feature.
If you own the website
Compare the exact response with access, application, gateway and dependency logs. Preserve request identifiers only where safe to share. Investigate one failed component before changing DNS, restarting unrelated systems or weakening access rules.
Who to contact
Visitors should contact the website with the code, time and affected action. Owners should involve hosting, CDN or dependency support according to their logs. Never send session cookies or authentication headers in a public report.
Sources and further reading
These provider documents support the technical explanations. The comparisons above narrow the investigation; they cannot diagnose every network or service.