Free tool · no sign-up
Free status page, no sign-up
Yes, you can have a public status page in a minute, for free, without an account. Type up to 5 sites below and BugOtter gives you a link that checks each one live whenever someone opens it.
- 5sites per page
- Freeno account, no card
- Nothingstored: it lives in the link
Status status
- Websitemyapp.comChecked on open
- APIapi.myapp.com/healthChecked on open
Powered by BugOtter
This page checks your sites each time someone opens it. It doesn't watch them in between or alert you. For that, BugOtter checks every minute and keeps history (every minute on Builder and Pro).
What the free page does, and doesn't
It lives in its link
The title and sites are packed into the?s=part of the URL. BugOtter keeps no copy.It checks when opened
Each visit sends one request per site and shows working, slow or down. Nobody watches in between, so there are no alerts.It stays out of search
Generated pages are noindex. People reach them through the link you share.
What you get with BugOtter
A BugOtter status page is fed by monitoring that never stops. Here is the real one for bugotter.com.
- One headline, readable in two seconds, in colour and in words.
- Daily uptime bars and a percentage for each part you watch.
- Incidents with your updates, dated, in plain words.
It's checked around the clock (every minute on Builder and Pro, every 5 min on Starter) from three regions, with 90 days of history, planned maintenance and email subscribers. It comes with every plan. Status pages in the docs shows how to set one up.
What a status page is
A status page is a public page that answers one question for your users: is it me, or is it them?
It lists the parts of your product (the website, the API, checkout) and says whether each one is working right now. A good one also shows recent incidents and what you're doing about them.
It sits on its own address, often status.yourapp.com, so it still loads when your app doesn't. That's the whole point: when your app is down, your app can't tell anyone.
Why an indie app needs one
Big companies have status pages to protect their support teams. Solo founders need one for the same reason, with a team of one.
Fewer “is it down?” emails
When something breaks, every user who notices writes to you, and you answer the same email twenty times instead of fixing the problem.
A status link in your footer and your error screen lets people check for themselves. One update answers all of them.
Trust you can point at
A customer deciding whether to pay you wonders if a one-person app will still be up next month.
Months of green bars and honestly written incidents answer that better than any promise on your pricing page. Being open about the bad days makes the good days believable.
A calmer outage
Once you've posted “Checkout is failing for some cards, fix going out now”, you can work without your inbox filling up.
Users who know you're on it are patient. Users who hear nothing assume the worst, and some of them cancel.
What to put on it
Keep it short. A status page is read by worried people in a hurry.
- One clear headline“All systems operational” or “Checkout is down”. Readable in two seconds, in color and in words.In the free page
- The parts people useWebsite, API, Checkout, Email. Name them the way customers do, not the way your infrastructure does.In the free page
- Uptime history90 days of daily bars. It shows a bad day is rare, or shows you it isn't.Needs a monitor
- Incidents with updatesWhat broke, when, and short dated updates until it's fixed. Plain words: no “degraded performance in us-east-1”.Needs a monitor
- Planned maintenanceAnnounced ahead, with a time window in UTC, so nobody mistakes it for an outage.Needs a monitor
- A way to subscribeAn email when something happens, so people stop refreshing the page.Needs a monitor
What to leave off: internal hostnames, error logs, revenue, anything that helps an attacker or worries a customer for no reason. BugOtter's status pages show uptime and incidents only, never errors, logs or revenue.
The free page covers the first two items, live. History, incidents, maintenance and subscribers need something watching all the time, which is what a monitor does.
Free options, honestly
This free link is fine for a quick public check. For a page you can stand behind during an outage, you want monitoring behind it.
| Feature | This free link | BugOtter status pages |
|---|---|---|
| The basics | ||
| Price | Free, no account | Included in every plan, from $10/mo billed yearly |
| Sites per page | Up to 5 | One page per app, with its own parts |
| Monitoring | ||
| How it checks | Only when someone opens it | Around the clock, every minute on Builder and Pro |
| Checked from | BugOtter's server, one place | Three regions |
| Alerts you when it's down | No | Yes |
| On the page | ||
| Uptime history (90-day bars) | No | Yes |
| Incidents and your updates | No | Yes |
| Planned maintenance | No | Yes |
| Email subscribers | No | Yes |
| Your brand | ||
| Your own domain | No | On Pro |
| "Powered by BugOtter" mark | Shown | Shown, removable on Pro |
| Shows up in search | No (noindex) | Yes |
BugOtter isn't the only free option. Other monitoring tools give you a hosted status page on their free plans too, and they're worth a look:
- Better Stack includes one status page and 10 monitors on its free plan.
- Instatus has a free plan with a public status page, monitors and up to 200 email subscribers. Your own domain starts on a paid plan.
- UptimeRobot includes one basic status page and 50 monitors checked every 5 minutes on its free plan. Your own domain starts on a paid plan.
Free plans checked Nov 4, 2026, on betterstack.com/pricing, instatus.com/pricing and uptimerobot.com/pricing. Plans change; check their pages before you choose.
How the free page works
You type your sites
Up to five names and addresses. They're packed into the link. Nothing is saved on BugOtter.Someone opens the link
BugOtter's server sends one request to each address, 6 seconds at most. Private network addresses are refused.They see the answer
Working, slow or down, with the HTTP status and how long it took.
To keep it fair for everyone, each address is checked at most once a minute however many people open the page, and one network can only cause a limited number of fresh checks. The page is marked noindex, so search engines leave it out.
Want the full version? Status pages in the docs shows parts, updates, subscribers, your own domain and the README badge. The uptime calculator turns “99.9%” into minutes of downtime, and the site check looks for leaked keys and missing headers.
Questions
Is this status page really free?
Yes. There's no account, no trial and no card. You type up to 5 sites and get a link. It stays free because it's simple: it checks your sites only when someone opens the page, and it stores nothing.
Does the free status page alert me when my site goes down?
No. It only checks when someone opens it, so nobody is watching in between. If your site goes down at 3am, you find out when a user tells you. For alerts you need a monitor that checks on a schedule, like BugOtter, which emails you (or pings Telegram, Slack, Discord and more) the moment a check fails.
Where is my list of sites stored?
In the link itself. The names and addresses are packed into the ?s= part of the URL. BugOtter keeps no copy, so if you lose the link, make a new one. Anyone with the link can see the names and addresses you typed, so only add sites you're happy to show.
How does the page check my site?
When someone opens the page, BugOtter's server sends one GET request to each address, follows up to five redirects, and waits up to 6 seconds. An answer under 400 is Working, a slow answer (over 3 seconds) is Slow, and an error, a 4xx or 5xx status or no answer is Down. Results are reused for up to a minute, so a busy page doesn't hammer your server.
Can I use my own domain for the free status page?
No. The free page always lives on bugotter.com. BugOtter's real status pages can run on your own address, like status.yourapp.com, on Pro.
Will the free status page show up on Google?
No. Generated pages are marked noindex, because they're yours to share, not ours to rank. People reach them through the link you give them.
What should I check: my homepage or a health endpoint?
Both, if you have an API. The homepage tells you the site loads. A health endpoint such as /api/health tells you the server and database answer. Name them plainly (Website, API, Checkout) so a worried customer knows which part is broken.
What's the difference from a BugOtter status page?
A BugOtter status page is fed by monitoring that runs around the clock (every minute on Builder and Pro, every 5 min on Starter), from three regions. It shows 90 days of uptime bars, incidents with your updates, planned maintenance, and lets visitors subscribe by email. It comes with every plan.
A status page that knows before your users do.
14 days of everything, no card needed. Plans from $10 a month, billed yearly.