Help / Troubleshooting
A monitor says down but my site works
Sometimes a monitor says your site is down while it opens fine for you. Usually the site really did fail for our checks, but only from some places, or only in a way your own browser does not see. This guide shows how to find the cause and how to make the monitor less jumpy.
How we decide a monitor is down
We check from several cities. By default a monitor only goes down when 2 cities agree, and each of them has failed 2 checks in a row. One lost packet or one slow answer does not send an alert. Probes in the same data centre count as one city. Domain expiry and third-party service monitors are checked from one place each round, so these rules do not apply to them.
More detail is in How checks work.
Find out what failed
- Open the monitor from your dashboard.
- Look at By location. It shows what each city got back. If only cities in one region fail, the problem is probably a route or a block in that region.
- Look at Latest checks for each check's result and error, such as a timeout, a status code or “No reply to 3 pings”.
- Open Incidents to see the cause of past outages and the cities that saw them, under Seen from.
Common causes and fixes
Your firewall or bot protection blocks our checks
Security tools, rate limits and “are you human” pages often block automated checks. Your browser gets through, our probes do not. The error is often a 403 or 429 status code, or a timeout. Allow our checks through: see Allowing our checks through a firewall.
The site blocks some countries
If your site only serves some countries, cities elsewhere will fail. Press Edit on the monitor's page, open More settings and tick the cities that should reach the site under Check from. Your plan sets how many you can tick. Press Save changes.
The answer takes longer than the timeout
The default timeout is 10 seconds. A slow page, or a server far from some cities, can go past it. Press Edit on the monitor's page, open More settings and raise Timeout (seconds). The highest is 30.
The status code is not one you expect
By default any code from 200 to 399 counts as up. A page behind a login may answer 401 or 403 instead. Under More settings, add the code you expect to Good status codes, for example 200-299,401.
Follow redirects is ticked to start with. Then the code that counts is the one from the page at the end of the redirect, so a redirect to a broken or blocked page shows as down.
A keyword changed
A keyword monitor fails when the word is missing from the page, or when it is there and you chose Start incident when keyword exists. We search the page's HTML source, not the text you see after scripts run. A redesign, a cookie banner or a different language for some countries can change it. Check the word is still in the page source, and whether Case-sensitive check is ticked.
Ping is blocked
Many servers and firewalls drop ping. A ping monitor sends 3 pings and counts as up if any one comes back. If ping is blocked on purpose, use a port monitor or a website monitor instead. See Which monitor to use.
The monitor is too sensitive
Under More settings you can change two numbers:
- Down when this many locations agree: raise it to 3 or more so a problem has to be seen in more places. The highest is 10.
- Each of them after this many failed checks in a row: choose 3 to only hear about longer outages. 3 is the highest.
Both make alerts arrive a little later. That is the trade-off.
Planned work
If the site goes down while you deploy or restart something, set up a maintenance window first. Alerts are held back during the window. If the monitor is still down when the window ends, you get the alert then. See Maintenance windows.
Stop repeated alerts
If you set the down alert to repeat, it keeps coming until the monitor is back up or someone acknowledges the incident. Open the monitor and press Acknowledge next to the open incident under Incidents. You can type a short note first.
Still getting alerts you think are wrong
Note the monitor name and the time of the alert, and contact support. Tell us which cities failed and the error from Latest checks.
Still stuck? Email [email protected] and say which guide you were following.