Your first monitor,
live in five minutes.
Create a check, keep the sensible defaults, switch on alerts, and learn to read what actually happened. By the end you have a live monitor watching one of your URLs — and telling you the moment it goes down.
Sign in
Create a free account at app.exit1.dev. That sign-in is your whole setup.
Nothing to install
exit1 runs every check from its own infrastructure. No agent, no script, no server of yours involved.
Free to start
Watch up to 10 checks free. Upgrade later for faster intervals, more checks, SMS alerts, and multi-region monitoring.
Five calm steps, start to signal.
Create your first check
A check is one thing you want to watch — a website, an API endpoint, a server port, a DNS record. Open Checks in the sidebar and click Add Check; a panel slides in from the right.
- 1Pick a check type. The icon strip at the top sets what you monitor. Web is the default and covers most cases.
- 2Enter the URL. For Web and API checks, choose the protocol (https:// is default) and type the rest, e.g. example.com.
- 3Name it. The display name fills in from the URL — edit it to whatever you’ll recognize on your dashboard.
- 4Click Add Check. It goes live immediately, and its online / offline status appears on the Checks page.
You’re done in four clicks. Sensible defaults are applied automatically — the steps below just show you how to fine-tune them.
Check types
Website and page availability — the default, and the right pick for most sites.
REST endpoints: assert status codes and response content.
Verify a URL redirects exactly where it should.
Port reachability for databases, mail, and game servers.
Host reachability over ICMP.
WebSocket handshake checks.
Watch DNS records for unexpected changes.
Track domain registration expiry — no uptime probing.
Set the basics
In the New Check panel — or later, by editing a check — expand Settings to reveal Schedule. Three small choices, and the defaults are good for almost everyone.
How often exit1 probes your URL — from a few seconds up to once a day. Shorter catches outages faster; the fastest intervals (down to 15 seconds) are on paid plans.
Checks run from Europe (Frankfurt) by default. Paid plans add America (Boston) to monitor closer to your users or compare regions.
The timezone used to format timestamps in your notifications. Leave it on UTC if you’re not sure.
Checks run on a shared schedule, so the interval is approximate — a “5 minute” check fires roughly every five minutes, not to the exact second.
Confirm real outages
Still inside Settings, the Alert behavior section decides how aggressively exit1 calls something down. Defaults are tuned for most people — reach for these only if you see false alarms or want stricter checking.
Immediate recheck
On by defaultWhen a probe fails, exit1 re-checks about 30 seconds later — so a one-off blip never wakes you.
Confirm down after
Default: 4Consecutive failed probes required before a check is marked offline. Raise it to quiet noise; lower it to alert sooner.
Max response time
Off by defaultMark a check down when a response takes longer than your threshold — catches “up, but painfully slow.”
Peer confirmation
On by defaultA suspected outage is double-checked from a second region before alerting. Leave it on unless your endpoint answers differently by geography.
API checks · HTTP configuration
For API checks, an extra HTTP section lets you set the request method (GET is best for uptime — some hosts block HEAD), expected status codes (e.g. 200, 201, 301-308), request headers and body, and response-text validation. exit1 treats 2xx and 3xx as up — and 401/403 count as up for protected endpoints.
Turn on alerts
Monitoring only helps if it tells you when something breaks. exit1 delivers alerts through several channels — each set up from the sidebar.
Down, up, SSL, and domain alerts straight to your inbox.
SMS
Paid plansText-message alerts for the incidents you can’t miss.
Webhooks
POST events to your own endpoint, Slack, Discord, or Teams.
Integrations
Pushover, PagerDuty, and Opsgenie.
Set up email alerts
- 1Open Emails from the sidebar.
- 2Your account email is added as a recipient automatically. Add or change recipients as needed.
- 3Choose which events to hear about — Down, Up, SSL warnings, and domain changes.
- 4New checks are included automatically, so your first check is already covered. Toggle per check or per folder.
- 5Click Send test to confirm a notification reaches your inbox.
Good to know
- Alerts fire only when a check changes state — up to down, or back again. No status-quo spam.
- Flap detection waits for the consecutive results you choose, so a flickering endpoint doesn’t flood you.
- Each channel has its own hourly budget to keep storms in check.
Prefer Slack or Discord? Open Webhooks, paste your webhook URL, and pick the same events. The same per-check controls apply.
Watch the logs
Once your check is running, you can see exactly what exit1 observed on every probe — and why an alert fired.
Each row is a single probe result — status (online, offline, paused, unknown), response time and HTTP code, the error reason on failure, and a full timing breakdown:
Filter by check, time range (last hour up to 60 days), and status to zero in on a specific incident.
For a real-time view, open Live to watch a continuously scrolling response-time chart for a single check — like a task-manager graph for your endpoint. Outages and recoveries land as markers on the timeline.
One quiet monitor, fully on watch.
Where to go next
Put your first URL on watch.
It takes about a minute. No credit card — 10 monitors free.
Questions? Reach us any time at connect@exit1.dev.