Getting started
You'll have a check running from four continents in a couple of minutes.
1. Create your account
Open the console and choose Sign up. You'll need an email address and a password, plus a quick anti-bot challenge, and that's all there is to it.
Prefer not to manage a password? You can Sign up with Google or Sign up with GitHub instead. ZeroDrop creates your account from your verified provider email and signs you straight in; the same buttons let you sign back in later. See Account & security.
Once you're in you can harden the account whenever you like with two-factor authentication or a passkey. See Account & security.
2. Add your first check
From the Checks page, choose New check and pick a type:
- HTTP: paste the URL you want watched, for example
https://example.com/health. - SMTP: enter the mail server host (and port, if it isn't 25).
Everything else has a sensible default: a 60-second interval, a 200 expected status for HTTP, and probing from all active locations. You can change any of it now or later. See Checks for the full list of options.
Save, and ZeroDrop immediately schedules the check on every location.
3. Watch it come to life
Give it a minute. On the check's detail page you'll see:
- A per-location row for SFO, NYC, AMS and SYD, each with its latest result and response time.
- The current status:
ok,firing(down) orunknown. - Latency and uptime history.
A brand-new check may briefly show unknown until enough locations have reported. That's the fail-safe at work, not an error. Read why in Consensus & status.
4. Get notified
Alerts don't go anywhere until you add a destination. Create a notification channel (an email address or a webhook), verify it, and attach it to the check. From then on you'll be told the instant an incident opens or closes. Full details in Incidents & alerts.
Next steps
- Tune how quickly a check fires and resolves: Consensus & status
- Silence planned downtime: Maintenance windows
- Manage checks as code over the API: Account & security