401 Unauthorized
The page needs a sign-in (or an API key) and none was given.
Why it happens
- Basic auth on a staging site.
- An API endpoint called without a token.
What to do
- If the page should be public, remove the authentication. If it should be private, that's correct: monitor a public page instead, or a health endpoint.
In monitoring
Counts as down by default. If the page is meant to require a sign-in, add 401 to the monitor's accepted status codes.
Catch the next 401 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.