Hosting & Performance
502 vs 503 Errors: What Website Owners Should Check
A proxy or CDN shows a 502 Bad Gateway or 503 Service Unavailable page. A 502 usually indicates an invalid upstream response, while a 503 commonly signals unavailable or intentionally overloaded capacity.
A proxy or CDN shows a 502 Bad Gateway or 503 Service Unavailable page. This guide works through 502 or 503 website error from evidence to a verified outcome.
Domain, DNS, hosting, TLS and email are separate systems that meet at public records. A change can look complete from one network while caches or an overlooked record still direct other visitors elsewhere.
What the symptom tells you
A 502 usually indicates an invalid upstream response, while a 503 commonly signals unavailable or intentionally overloaded capacity.
The useful question is not “which tool should I install?” but “where does the first confirmed failure occur?” Keep the original state available long enough to answer that question.
Checks to make in order
- Record the authoritative nameservers and current DNS records before changing them.
- Check the response from more than one network and resolver, including the exact hostname involved.
- Keep the previous service available until web, email, TLS and scheduled tasks are verified.
- Issue-specific action: Record status, request ID and time, check origin health and logs, then review deployments, resource limits and maintenance state.
How to verify the result
Repeat the original journey using a fresh session and a representative device or account. Check the expected result, nearby functions and any logs or messages that should accompany success. Record what changed so a later incident does not require the same discovery work.
Before closing the task, confirm who owns the system, where the relevant configuration is documented and what monitoring would reveal a recurrence. That small handover step turns a one-time repair into a more dependable operating practice.
A shortcut to avoid
Do not purge every cache or reboot repeatedly before collecting evidence.
When specialist help is sensible
Escalate quickly when errors affect checkout, login or all traffic.
Related questions
For authoritative background, read MDN domain-name guide. If you would rather have someone investigate the evidence with you, review SoftNSM’s hosting and migration support or send the team the symptoms and affected URL.