Vigil

Uptime monitoring · multi-location · no installation

Know it's down
before they do.

Vigil checks your sites every minute from locations around the world, verifies real incidents, and tells you the moment something breaks — and the moment it recovers.

Monitor your first site — freeNo credit card. 1 monitor free.
live · 4 locations
htmlaps.dk182 ms
api.client-a.com94 ms
shop.client-b.dkDOWN 2m
cdn.client-c.io61 ms

fra ✓   nyc ✓   sgp ✓   cph ✓ — checked 14s ago

1,440

checks per monitor, per day

30 s

fastest check interval

verification before an alert

90 d

of uptime history, public

How it works

From zero to watched in five minutes

1

Add a monitor

Paste a URL, pick an interval and which channels to wake up. Defaults are sane; tuning is one screen.

2

Pick your locations

Choose which of our monitoring locations check it — close to your users, spread across continents, or simply all of them.

3

Get told the moment it matters

Confirmed incidents open with cause and affected regions, alerts fan out, and recovery closes the loop automatically.

incident log · shop.client-b.dk

[14:31:12Z] fra  check fail · timeout 10000ms
[14:31:40Z] fra  check fail · 2nd consecutive
[14:31:58Z] nyc  check fail · timeout 10000ms
[14:32:24Z] verifying · waiting for quorum
[14:32:31Z] incident confirmed from fra + nyc — alerting

[14:43:55Z] all locations report 200 OK
[14:43:55Z] resolved · downtime 11m 24s

Everything you need, nothing to babysit

01 / Verify

No false alarms, ever

A failure is confirmed by repeated checks from independent locations before anyone gets woken up. One flaky route in one datacenter is not an incident. And “up” means correct: assert status codes and page keywords, not just a reachable server.

02 / Worldwide

Checked from where your users are

Our monitoring locations span Europe, the Americas and Asia-Pacific. Pick which ones watch each site — nothing to install, ever.

03 / Alert

Alerts that reach you

Email, Slack, Discord, Microsoft Teams, ntfy, Pushover, iOS push — or a signed webhook into your own systems. Per-monitor routing, recovery notices, reminders until it's fixed, quiet hours for when you're off.

04 / Publish

Status pages clients trust

A clean public page per project with live state and 90 days of history. Post incident updates as you work the problem — investigating, identified, resolved. Visitors can subscribe for email updates.

05 / Maintain

Maintenance without noise

Flip a monitor into maintenance mode and deploy in peace. Checks keep recording, alerts stay quiet.

06 / Team

Built for teams

Invite teammates and clients with roles. Everyone sees the same truth: what is up, what is down, and since when.

07 / Heartbeat

Cron jobs and backups, watched

Heartbeat monitors flip the direction: your job pings Vigil after every run. When a ping doesn't arrive on schedule, an incident opens — a nightly backup can no longer fail silently.

08 / Certify

SSL expiry, never a surprise

Every HTTPS check records the certificate behind it. You're warned before it expires — two weeks ahead by default, long before a visitor ever sees a browser warning.

09 / Pocket

Vigil in your pocket

A native iOS app with your live dashboard, response-time charts and full monitor controls — and instant push notifications the moment something goes down or comes back up.

The monitoring network

Eight vantage points. Pick yours per monitor.

Every monitor is checked from the locations you select — close to your customers or spread across continents. An incident only counts when enough locations agree, so one hiccup in one region never wakes you up.

latencies shown to example.com

fra

Frankfurt

24 ms

ams

Amsterdam

31 ms

lon

London

38 ms

nyc

New York

87 ms

sfo

San Francisco

142 ms

sgp

Singapore

168 ms

syd

Sydney

201 ms

cph

Copenhagen

19 ms

The alert

Bad news, delivered well

Cause, affected regions, when it started — and a recovery message with the total downtime when it's over. Routed per monitor, so the right project pings the right channel.

Vigil app 14:32

🔴 shop.client-b.dk is DOWN

Cause: Timeout after 10000ms
Seen from: fra, nyc
Started: 14:32 UTC — details

🟢 shop.client-b.dk is back UP

Downtime: 11m 24s

EmailSlackDiscordTeamsntfyPushoveriOS pushWebhook + HMAC

The receipt

Proof of uptime, public by design

Each status page shows live state, 90 days of history and recent incidents — the page you send instead of writing the "everything is fine now" email.

All systems operational

client-a.com99.98% / 90d
shop.client-b.dk99.98% / 90d

monitored by Vigil

Pricing

Free to start, flat to grow

Free

€0 / month

  • ✓ 1 monitor, checked every minute
  • ✓ All alert channels
  • ✓ Public status page
  • ✓ Every probe location
Start free

Pro

€19 / month

  • ✓ Up to 100 monitors
  • ✓ Everything in Free
  • ✓ Unlimited status pages & teammates
  • ✓ Status pages on your own domain
  • ✓ Cancel anytime
Go Pro

Questions, answered

The fine print, minus the fine print

How is downtime verified?

Each location must see consecutive failures before it counts as down, and you choose how many locations must agree before an incident opens. A single timeout from a single region never pages anyone.

Where are the checks run from?

From our own monitoring locations across Europe, the Americas and Asia-Pacific. You choose per monitor which locations check it — or simply use all of them. Nothing to install on your side.

Do I need to change my site or install anything?

No. Vigil checks your site from the outside, exactly like a visitor's browser would. If you want firewall allow-listing, each location has a stable address.

Which alert channels are supported?

Email (SMTP), Slack, Discord and Microsoft Teams via incoming webhooks, push notifications through ntfy (including self-hosted) and Pushover, plus a generic webhook signed with HMAC-SHA256 for anything custom.

Can it watch cron jobs and backups too?

Yes — heartbeat monitors flip the direction. Your job pings a unique Vigil URL after every run; when a ping doesn't arrive on schedule, an incident opens and you're alerted, exactly like downtime.

Can clients see their own uptime?

Yes — publish a status page per project and share the link, or invite clients to the team with member access.

Is my data locked in?

No. A documented REST API exposes your monitors, incidents and check data, incidents stream out through signed webhooks as they happen, and every uptime number is visible in the dashboard and on your status pages.

Your sites are being visited right now. Are they up?

Find out in the next five minutes — and every minute after that.

Start monitoring free

no credit card · 1 monitor · all locations