Quick Start

First site monitored from the Console in a couple of minutes. No terminal, no config files, no credit card.

1. Sign in

Open the Console and sign in with email or Sign in with Apple. The dashboard opens with active incidents up top, a live overview, and monitors below.

Existing email and password accounts open through Sign in with Apple once the account email is verified. Until then the sign-in screen says so; signing in with the password and verifying the email resolves the conflict.

2. Add the first monitor

Choose New monitor, paste the site's URL, and create the monitor. The URL is the only required field. Our engine picks a sensible check type and starts checking every 30 seconds from regions around the world, right away.

Monitors cover more than web pages: API endpoints, raw TCP hosts, DNS records and ICMP pings. The defaults are sensible, so create first and tune later. Every option is in Monitor a site.

3. Read the real status

Open the new monitor from the dashboard:

• A live verdict, reconciled from our checks, the provider's status page and crowd reports, instead of a single lucky ping.
• A latency breakdown (DNS, TLS, time-to-first-byte, transfer) that explains why a response is slow, beyond that the response is slow.
• Uptime, percentiles and history, where blips stand out.

4. Set up alerts

Monitors matter when someone hears about them. Open Contacts, add a contact and verify the contact. latency then sends an alert when something changes, and again on recovery.

• Email is on every plan and webhooks from Hobby up; SMS, Slack and Discord are on paid plans.
• By default a couple of failed checks get confirmed before an incident opens, so a single flaky request never pages anyone. For alerts on the very first failure, toggle Alert on first failure on the monitor. Full details in Alerts.

5. Watch dependencies

Sites rarely go down alone. Add the services underneath (Stripe, the CDN, the database host) and our probes watch those providers alongside owned services, so a provider's bad day never arrives as a surprise. Any host can be inspected on the public inspector.

---

What next?

• How monitoring works: check types, regions, and how verdicts are reconciled.
• Alerts: contacts, routing, thresholds and fast retry.
• Telemetry: first event, log or trace, shown beside monitors.
• iOS app on the App Store: the status board on iPhone, with push alerts.

Terminal first?

Our CLI is open source, and a public API covering everything in the console is coming soon.