A status page your users can trust
Point Beacon at your endpoints, get a public page with real uptime history and an incident timeline. Checks run from three European locations, so a single bad route never shows up as an outage.
What you get
Honest history
Ninety days of per-service history on the page itself. No hiding a bad week behind a rolling average — every degraded interval stays visible.
Incident timeline
Post updates as the incident develops; subscribers get each one. The timeline stays published afterwards, which is what people actually come back to read.
Three probe locations
Warsaw, Frankfurt, Amsterdam. A service is marked down only when at least two of them agree, so transit trouble at one provider does not page you.
Your own domain
CNAME status.yourcompany.com to us and we issue the certificate. No mixed
content, no vendor banner across the top of your page.
Checks
| Type | What it does | Interval | Marked down after |
|---|---|---|---|
| HTTP / HTTPS | status code, body match, certificate expiry | 30 s | 2 failures, 2 locations |
| TCP port | connect and optional banner match | 30 s | 2 failures, 2 locations |
| Heartbeat | your cron pings us; silence is the alert | you decide | grace period + 1 min |
| Browser step | login flow, scripted, headless | 5 min | 2 consecutive failures |
Notifications
Email, webhook, Telegram and Slack. Subscribers pick per-service, so the people who only care about the API are not woken by a marketing-site blip. Notification history is kept for a year and is exportable.