CheckWebsiteNow

CheckWebsiteNow results

Result: The server returned an error

The website is online, but answered our check with an error code.

Quick answer

We reached the server and it replied with a 4xx or 5xx status code. 4xx codes usually mean the page is missing or the request was refused. 5xx codes mean something went wrong on the server. The exact code in the details tells you which.

When to wait: 5xx errors are often temporary; try again in a few minutes. A 404 or 410 will not go away by waiting.

If you are visiting the website

  1. Look up the exact code Open the guide for the code shown in the details, for example 503 or 404.
  2. Wait and reload Wait a few minutes, then reload the page once. Short problems often fix themselves.
  3. Check the service's status page Big services often publish an official status page that lists known problems.

If you run the website

  1. Check server error logs Look at your web server and application logs for the time of the error. They usually name the exact cause.
  2. Review recent changes Think about what changed recently: a deployment, plugin update, configuration edit or DNS change. Roll back with your tested procedure if needed.
  3. Check your hosting provider's status Your host may have a known outage. Their status page or support can confirm it.

Likely causes

  • Common The homepage or server has a problem right now (5xx). (Website side)
  • Sometimes The page was moved or removed (404 or 410). (Website side)
  • Sometimes A service in front of the website, such as a CDN or proxy, could not reach the real server. (Website side)

What to avoid

  • Do not keep reloading quickly; it adds load to a server that may already be struggling.

Is the website down? Check it now

One measurement point. Results explain what we saw, not a worldwide verdict.

Sources

Last reviewed: