About
Beacon is run by four people who got tired of status pages that go blank exactly when something is wrong.
Where the probes run
| Location | Provider | IPv4 | Role |
|---|---|---|---|
| Warsaw, PL | local transit | yes | primary probe |
| Frankfurt, DE | local transit | yes | primary probe |
| Amsterdam, NL | local transit | yes | tie-breaker |
A component is marked down only when two of the three agree. That single rule removes most of
the false alarms people quit other tools over. If you need to allow-list us, the current probe
addresses are published at /api/v1/probes and change with 30 days notice.
What we deliberately do not do
No on-call scheduling, no paging escalations, no incident-command workflow. Those are separate products and better ones exist; Beacon sends a webhook and gets out of the way. We also do not do "uptime badges" for marketing pages — an uptime number without the history behind it is decoration, not information.
Data
| What | Where | Kept |
|---|---|---|
| Probe results | EU only | 13 months |
| Incident text | EU only | indefinitely, it is public anyway |
| Subscriber emails | EU only | until unsubscribe |
| Access logs of the public page | EU only | 7 days |
No analytics scripts on hosted pages. A status page that loads six trackers is a status page that fails when the tracker fails.