Guides for staying up.

Practical guides and articles about uptime monitoring, SSL certificates, DNS, cron jobs, servers and status pages, from the team behind Uptimecheck.

Guides 5 min read

Incident Communication: A Plan and Templates for Every Stage

How to tell customers about an outage: who speaks, how often, on which channel and in what words. A one-page plan, severity levels, update cadence and ready-to-use templates for status pages, email and social media.

Read

Guides 5 min read

500 Internal Server Error: How to Find and Fix the Cause

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.

Read

Guides 6 min read

504 Gateway Timeout: What It Means and How to Fix It

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.

Read

Guides 6 min read

502 Bad Gateway: What It Means and How to Fix It

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.

Read

Guides 5 min read

API Monitoring Checklist: What to Check Beyond a 200 OK

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.

Read

Guides 7 min read

How to Build a Health Check Endpoint (and Monitor It)

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.

Read

Downtime is obsolete.

Set up your first monitor in under a minute, or look around the live demo first.

14-day free trial · No credit card required