502 Bad Gateway
A proxy or load balancer in front of the site got an invalid answer (or none) from the application behind it.
Why it happens
- The application process crashed or is restarting.
- The app server (PHP-FPM, Gunicorn, Node) isn't running or is out of workers.
- A deploy where the new process isn't up yet.
- A misconfigured upstream address in nginx or Caddy.
What to do
- Check that the application process is running and listening on the port the proxy expects. Look at both the proxy's and the app's logs.
In monitoring
Counts as down. If two checks in a row see it, you're alerted with this code as the cause.
Catch the next 502 before a customer does.
heyUptime checks your site every 30 seconds, confirms a failure before alerting, and tells you the code and the likely reason.
All status codes · Not sure what your site returns right now? Check it.
Quick checks, no sign-up.
Is it down right now?
Check whether a website is down for everyone or just for you.
SSL certificate checker
See when a site's certificate expires, who issued it, and whether browsers trust it.
Domain expiry checker
Find out when a domain name's registration runs out, before it does.
Website speed test
Where the time goes when a page is requested: DNS, connection, TLS, server, download.
Cron job tester
Make a test URL, have your cron job call it, and watch the call arrive.
Uptime and SLA calculator
What 99.9% really means: the downtime an uptime percentage allows per day, month and year.
Status page example
See what a public status page looks like, with your company's name on it.
Next time, be the first to know.
Let someone else watch the shop. If anything breaks, you will hear it from us, not from a customer.