First steps when your site is down
Don't change anything yet. Start by working out whether the site is really down, and for whom. Most of the first ten minutes is looking, not fixing.
Rule out your own connection
Sometimes the site is fine and the trouble sits on your side. MDN says that for gateway errors, an exception is a client networking error, particularly if the service works for other visitors.1 In those cases, it suggests checking network settings, firewall setup, proxy settings and DNS configuration.1
You can check fast.
- Try the site on your phone using mobile data, not your Wi-Fi.
- Try a different browser, or a private window.
- Ask someone in another town or suburb to open it.
- Look at what your uptime monitor says. It checks from outside your network.
If it loads for others, the problem is likely local. If it fails everywhere, it's the site.
Check whether the whole site is down
Open the home page, then an inside page, then your admin login. Note which ones fail. A home page that loads while a single page fails points to a smaller problem than a blank screen on everything.
Write down what you see. Copy the exact words of any error message, and the error number if there is one. The page on common error codes explains what those numbers hint at.
Think about what changed
Outages often follow a change. Did you update a plugin, edit a file, change a setting or renew something recently? Did your host mention maintenance? MDN says common causes of a 503 error are that a server is down for maintenance or overloaded.2
Check your email, including spam, for notices from your host or domain registrar. Also look at your host's status page if it has one.
Here's a rule worth keeping. Before you change any DNS, hosting or domain setting, write down the existing settings first, and follow your own provider's help pages. Then you can always put things back. Keep your logins to yourself: no passwords, recovery codes or registrar logins go to anyone, in a chat or in any tool. Your host does not need them to look at an error. Give them the error code, the time and the web address instead.
Contact your host with the right details
Cloudflare's support pages say that when troubleshooting most 5XX errors, the correct course of action is to first contact your hosting provider or site administrator.3 That's useful for any site, not just those using Cloudflare.
It also lists what to pass on.3
- The specific error code and message.
- The time and time zone when the error happened.
- The web address that caused the error.
Add what you were doing and what changed recently. A short, exact report gets a faster answer than "my site is down".
While you wait
Don't keep refreshing. Check back every few minutes, and note the times. If your site takes orders, consider a short message on social media or by email saying you know about the problem.
When it's back, keep your notes. They'll help you read the outage later, and they're the start of a record for next time.
Notes and sources
- 504 Gateway Timeout, MDN Web Docs
- 503 Service Unavailable, MDN Web Docs
- Cloudflare 5xx errors, Cloudflare Support docs