Odown product news and updates

Insights on uptime, status pages, and alerting, written for builders. Follow along for product updates, how-tos, and real examples that help you keep users happy.

Why Does My Heroku App Take 30 Seconds to Load: Dyno Sleep, Boot Time, and the Router Timeout

Why Does My Heroku App Take 30 Seconds to Load: Dyno Sleep, Boot Time, and the Router Timeout

Heroku Eco dynos sleep after 30 minutes without web traffic. The wake itself takes seconds; the rest of the delay is your app booting

Does Vercel Have Built-In Uptime Monitoring? What It Covers and What It Misses

Does Vercel Have Built-In Uptime Monitoring? What It Covers and What It Misses

Not in the external sense. Vercel's Observability alerts on anomalies in traffic it serves, but nothing checks your site from outside. Here is the split.

Nginx Upstream Timed Out (110: Connection Timed Out): Reading the Log Line and Fixing It

Nginx Upstream Timed Out (110: Connection Timed Out): Reading the Log Line and Fixing It

The nginx log line "upstream timed out (110: Connection timed out)" means nginx gave up waiting on your app server. Here is which timer fired and the fix.

How to Monitor a Netlify Site for Downtime: The Five Checks That Matter

How to Monitor a Netlify Site for Downtime: The Five Checks That Matter

Netlify does not include uptime monitoring for your site, so you add an external monitor. Here are the five checks that cover a Netlify deployment.

Cloudflare Error 1020: Access Denied by a Firewall Rule, Decoded for Both Sides

Cloudflare Error 1020: Access Denied by a Firewall Rule, Decoded for Both Sides

Cloudflare error 1020 means a firewall rule the website configured blocked your request. Here is what triggers it and how both sides fix it.

Exit Code 137: What It Means and How to Fix It

Exit Code 137: What It Means and How to Fix It

Exit code 137 means the process was killed with SIGKILL, and in containers that almost always means it ran out of memory. Here is how to confirm and fix it.

Nginx 499 Status Code: Client Closed Request, Explained and Fixed

Nginx 499 Status Code: Client Closed Request, Explained and Fixed

Nginx status 499 means the client closed the connection before your server answered. It is a latency symptom in your logs. Here is how to read and fix it.

Cloudflare Error 522: Connection Timed Out Between Cloudflare and Your Origin

Cloudflare Error 522: Connection Timed Out Between Cloudflare and Your Origin

Cloudflare error 522 means the connection to your origin timed out: Cloudflare waited about 19 seconds and heard nothing. Here is what to check.

Cloudflare Error 521: What Web Server Is Down Really Means and How to Fix It

Cloudflare Error 521: What Web Server Is Down Really Means and How to Fix It

Cloudflare error 521 means your origin server refused Cloudflare's connection: it is down or blocking Cloudflare's IPs. Here is the five-step fix.

Cloudflare Error 524: A Timeout Occurred Because Your Origin Took Too Long

Cloudflare Error 524: A Timeout Occurred Because Your Origin Took Too Long

Cloudflare error 524 means your origin took longer than 120 seconds to answer, so the request timed out. Here is how to fix work that outlives the limit.

Ready to Simplify Your
Uptime Monitoring?

Start your 14-day free trial and see just how easy uptime
monitoring can be.

Try Odown Free For 14 DaysNo credit card required.