Uptime monitoring without the false alarms.

On the EU control plane: the database, dashboard, incident history and status pages. Probes outside the EU execute checks and report results back. They hold no database credentials and store nothing themselves. Data you send to an application you connect, such as an AI assistant over MCP, goes wherever that application runs.

No. Nothing runs on your servers. Give Uptime Beacon a URL, a host and port, or a host to ping, and our probes check it from the locations you pick. Anything that answers on the public internet can be monitored, as long as it is yours or you have permission to monitor it.

A check fails when the request errors or times out, returns a status code you did not ask for, is missing the text you told it to expect, or fails a JSON assertion. A TCP check fails when the port refuses the connection, and a ping check when no reply comes back. An incident opens after the number of failures in a row you set, three by default, and where a monitor has more than one location, only once a second location has seen the same thing. A heartbeat monitor is down when your job does not check in on time, or checks in to say it failed.

On Starter and above, start a maintenance window on the monitor, from 5 minutes to 7 days. Checks keep running and are recorded, but they do not count against uptime, no incident opens and nobody is paged. The status page shows the monitor as under maintenance.

Yes, on Pro and above. A private page opens only from its own link, which carries a secret token, and tells search engines not to index it. You can hand it to a customer without it turning up in search results. Private pages are not served on a custom domain.

Not with a check from our probes. They run on the public internet, so the endpoint has to be reachable from there, and private and internal addresses are refused. A job inside your network can still report in through a heartbeat monitor, on Starter and above, as long as it can make an outgoing HTTPS request. At Enterprise scale we will design a setup around your network, including dedicated probes on allowlistable IPs and locations we don't run yet. Talk to us.

Read your monitors, incidents, check history, heartbeats, certificate and domain watches and plan usage, and diagnose a failing monitor region by region. If you allow changes for a team, it can also create, edit, pause and resume monitors, acknowledge or close incidents, start a maintenance window and add heartbeats and watches. Nothing can be deleted over MCP. It works on every plan, Free included, with the same roles and plan limits as the dashboard. Add https://app.uptimebeacon.eu/mcp to your assistant and sign in. No API key is needed.

Yes. The free plan has no fee and no fixed term: five monitors checked every five minutes from EU Central, one alert channel (email or Slack), one public status page and five expiry watches each for certificates and domains. Upgrade when you want more locations or a faster interval.