Practical guides and articles about uptime monitoring, SSL certificates, DNS, cron jobs, servers and status pages, from the team behind Uptimecheck.
Guides 7 min read
False alerts teach teams to ignore monitoring. How to cut the noise: confirm every failure with a second check, set sensible timeouts, validate the right URL and route alerts to the people who can act.
ReadGuides 4 min read
What does an hour offline really cost? A simple formula for the direct and hidden costs of downtime, worked examples and what uptime percentages mean in money.
ReadMonitoring 7 min read
Response time is how long your server takes to answer a request, not how long the page takes to load. What counts as good, why monitors and browsers measure differently, and what slows sites down.
ReadGuides 6 min read
A copy-ready incident postmortem template, the blameless principles behind it, a filled-in example from a checkout outage and how to publish a short summary on your status page.
ReadGuides 5 min read
A status page tells customers what is broken, what you are doing and when to check back. How to set one up, what to put on it and ready-to-use incident update templates.
ReadGuides 7 min read
An SLI measures how a service behaves, an SLO is the target for that measurement and an SLA is the promise to customers. Definitions, downtime tables and how to set each one.
ReadGuides 6 min read
DNS_PROBE_FINISHED_NXDOMAIN means the domain name could not be found in DNS. What causes it on the site owner side, how to check with dig and nslookup, and how to prevent it.
ReadGuides 5 min read
A changed DNS record can send your visitors or email somewhere else without a single error. How DNS monitoring works, which records to watch and what to do when one changes.
ReadAgencies 7 min read
Monitoring only the homepage misses most outages. A checklist of the URLs and checks that matter, from login and checkout to webhooks, cron jobs, SSL, DNS and servers, with example setups.
ReadGuides 7 min read
NET::ERR_CERT_DATE_INVALID, ERR_CERT_COMMON_NAME_INVALID and the other browser SSL warnings explained: what each one means, what causes it and how to fix it on your server.
ReadGuides 4 min read
An expired SSL certificate turns your site into a browser warning. Why certificates still expire with auto-renewal, what to monitor and how to set reminders that work.
ReadGuides 7 min read
Which HTTP status codes mean your site is down, which are fine and which depend on the endpoint. A monitoring-focused cheat sheet covering 1xx to 5xx, redirects, 401, 403, 429 and 5xx errors.
ReadSet up your first monitor in under a minute, or look around the live demo first.
14-day free trial · No credit card required
With your OK, Google Analytics and Microsoft Clarity show us which pages help and where visitors get stuck. They set cookies for up to 13 months. Without your OK, neither of them runs. You can change your mind at any time under Cookie settings at the bottom of the page. Privacy policy