Fail

Your site didn't answer with a working page

The short version

Check the server and your host's status page; the event shows what we saw.

What it means

Your uptime monitor asked for the page and didn't get a working answer, twice in a row about a minute apart. A working answer comes within 10 seconds with a status from 200 to 399 and, when you set a keyword, contains it. The alert's details say which part failed:

  • A status of 500 or above: the server answered but reported an error. This is often an application crash, an overloaded server, or a proxy that can't reach the application behind it.
  • A status from 400 to 499: the server refused the request. For example, the page moved without a redirect (404), a firewall or bot protection blocks us (403), or the page needs a login (401).
  • A timeout or a failed connection: nothing answered in time. The server is down or unreachable, or its DNS records point at the wrong address.
  • A certificate error: the HTTPS connection failed because the certificate expired, doesn't cover the host name, or isn't trusted.
  • The keyword is missing: the server answered with a different page, such as a maintenance page, an error page sent with a 200 status, or a page whose wording changed.

Why it matters

While the page doesn't work, visitors and customers can't use it. Anything that depends on it, such as sign-ups, payments or an API, stops too, and search engines may rank the site lower if the outage lasts.

How to fix it

  1. Open the page yourself from another network, such as a phone on mobile data. If it works for you, the problem may be regional, or a firewall rule may block our checks.
  2. Check your host's status page and your server's dashboard: CPU, memory, disk space, and whether the web server and the application are running. Restart whatever has stopped.
  3. For a 5xx status, read the application and web server error logs from the time of the alert. A recent deploy is the most common cause; roll it back if needed.
  4. For a timeout, run a DNS lookup on the host name and check that its addresses are your server's. Then check the server's firewall and your provider's network.
  5. For a certificate error, run the SSL checker and renew or replace the certificate.
  6. For a 403, allow our checks in your firewall or bot protection. They name DNS Super in the user agent.
  7. For a missing keyword, open the page and check that the text you chose is still on it. If the wording changed on purpose, change the monitor's keyword.

Check it worked

Choose Check now on the monitor's page. Once the page answers again, the monitor records a recovery, says how long the site was down, and sends a "back up" alert to the same channels.