Introducing uptime monitoring

booboo.dev has always told you what broke inside your app — the exception, the stack trace, the line that threw. Today we’re adding the other half of the picture: uptime monitoring that watches your app from the outside.

What it does

Add the endpoints you care about — your API, your health check, your marketing site — and booboo.dev polls each one on a schedule. For every check we record whether it responded as expected and how long it took. When an endpoint stops responding the way it should, we confirm it isn’t a one-off blip and then alert you.

• Scheduled checks at intervals from every minute to hourly, depending on your plan.
• Response-time tracking so you can see latency trends, not just up/down.
• Down & recovery alerts routed through the same Slack, Discord, and webhook integrations you already use for error alerts — set up once, get everything in one place.

Why it’s part of an error tracker

“Is my app working?” has two answers. Error tracking catches the failures that happen while your code runs. Uptime monitoring catches the failures where your code never runs at all — a crashed process, a bad deploy, an expired certificate, a downstream dependency dragging everything to a crawl. Having both in one tool means one place to look when something feels off, and one set of alert rules to maintain.

Getting started

Open any project, head to Monitors, and add a URL. That’s it — the first check runs within a minute. Plans include 1 monitor on Free, 5 on Starter, and 25 on Team.

This is the first step. A public status page and an embeddable status widget — so you can show your own users that you’re up — are next on the list.