I Built a Free Uptime Monitor That Takes...

We've all been there. You get a Slack ping at 2am: "Is the site down?" You check UptimeRobot. It says: DOWN - HTTP 500. Great. But what was HTTP 500? What did the user see? Was it a full crash, a broken layout, or just a flaky API response that cached badly? You dig through logs, try to reproduce it, and eventually just restart the server hoping the problem doesn't repeat. Sound familiar? That's the gap I kept running into with existing uptime monitoring tools. They tell you that your site went