502 Bad Gateway: checks for a website owner
A 502 Bad Gateway response means a server acting as an intermediary received an invalid response from another server it needed. The number describes a failed conversation between systems, not a definite diagnosis. Your host or website administrator usually needs to inspect the relevant service and logs.
Before you start
- Save the exact page address, visible provider branding and any request reference.
- Note when the page last worked and whether a release, hosting change or update happened nearby.
- Use an existing support route if your website is already managed; avoid purchasing a duplicate investigation.
What to do
Identify what is actually affected
Check the homepage and one ordinary content page, without submitting a form or order. Note whether the whole site fails or only a particular feature. A working static page and a failing booking connection give the administrator a more useful starting point than simply saying the internet is down.
Look for an acknowledged incident
Visit the actual provider’s status or support page through a known address. Match the affected product and time rather than assuming every incident applies to your site. If an incident is confirmed, follow its updates and keep the support reference instead of changing your website configuration.
Provide evidence for the server review
Send the failure time, page, screenshot and recent-change history privately to the responsible administrator. Ask which system returned the error and which upstream response failed. They may need the hosting supplier’s help; the logo on an error page alone does not establish who caused the problem.
Check recovery beyond the homepage
Once the provider reports a fix, repeat the affected read-only route and any separately authorised functional test. Record what succeeds and any remaining failures. An intermittent fault needs a clear follow-up point, not a claim that one successful refresh proves the underlying issue has disappeared.
What to check
- The affected pages and time window are recorded.
- The responsible provider has an incident or investigation reference.
- The original route works again, with any form or order checks separately authorised.
Sources and further reading
Platform features can change. Check the provider’s current guidance before changing a live service.