How uptime checks work, which intervals and locations to use, and how to set up monitoring that catches real outages without flooding you with alerts.
Guides 5 min read
A 500 Internal Server Error means the application failed while handling the request. Where to find the real error message, the causes behind most 500s and how to make sure you hear about them first.
ReadGuides 6 min read
A 504 Gateway Timeout means a proxy waited for the server behind it and gave up. How to find the slow part, fix it instead of just raising timeouts, and see slowdowns before they turn into 504s.
ReadGuides 6 min read
A 502 Bad Gateway means a proxy, load balancer or CDN got no valid answer from the server behind it. How to find which layer failed, fix the usual causes and catch the next 502 before customers do.
ReadMonitoring 7 min read
Good server alert thresholds catch a filling disk or a memory leak early without paging anyone for a harmless spike. Starting values for CPU, load, RAM, swap, disk, network and reboots.
ReadGuides 6 min read
MTTR, MTTA and MTBF measure how fast you fix incidents, how fast you respond and how often things break. Formulas, a worked example and practical ways to improve each one.
ReadGuides 5 min read
An API can return 200 and still be broken. A practical checklist for API monitoring: methods, headers, request bodies, authentication, expected responses and response time thresholds.
ReadGuides 7 min read
A health check endpoint tells monitors and load balancers whether your app can serve requests. What to check, how to keep it fast and safe, code for Laravel, Express and Flask, and how to monitor it.
ReadGuides 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 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 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 · Then free on 5 monitors · No credit card
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