UptimeVanguard

Getting Started

UptimeVanguard checks your sites from edge pollers in several regions and alerts you when an outage is confirmed.

What you can monitor

  • HTTP/HTTPS — status codes, methods, headers, bodies and response assertions
  • Ping — host reachability and round-trip time
  • DNS — alerts when records change from the first observed set
  • TLS certificates — expiry alerts and TLS scan findings
  • Heartbeats — cron and scheduled jobs that call a ping URL
  • Application health — spatie/laravel-health JSON endpoints
  • Broken links and mixed content — scheduled page scans
  • Performance — response-time degradation per HTTP check
  • Incidents and status pages — incident history, updates and hosted status pages

Quick Start

  1. Register and verify your email address. The trial lasts 7 days and includes 5 sites.
  2. Add a site and choose its checks and intervals.
  3. Add a notification channel in Settings and verify it (email) or link it (Telegram).
  4. Send a test notification to check the destination.

Adding Sites

  1. Open Sites and click Add Site
  2. Enter a public HTTP or HTTPS URL and a name
  3. Select the checks and how often each runs
  4. Save — the first checks are queued immediately

Intervals on the site form

  • HTTP: 1, 5, 10, 15 or 30 minutes, or 1 hour
  • Ping: 1, 5, 10, 15 or 30 minutes
  • DNS: 5, 15 or 30 minutes, or 1 hour
  • TLS certificate: 1, 6, 12 or 24 hours

Sites and checks →

Understanding Alerts

Site down

Sent when a second region confirms the failure for at least 60 seconds.

Performance degraded

Opt-in per HTTP check; compares recent response times with a baseline.

TLS, DNS and scans

Informational issue and resolved alerts; no downtime incident.

Incidents and quorum →

Notification Channels

11 channel types. Performance alerts are delivered by Email and Telegram only.

  • Email
  • Slack
  • Discord
  • Webhook
  • Telegram
  • PagerDuty
  • Microsoft Teams
  • Opsgenie
  • Google Chat
  • Pushover
  • Ntfy
Set up notification channels →

Guides

Heartbeats
Monitor cron and scheduled jobs with a ping URL
Laravel application health checks
Read spatie/laravel-health results
REST API v1
Endpoints, abilities and limits
API tokens
Create, scope and revoke tokens
Webhook payloads
JSON format and HMAC signature
Status pages
Hosted public status pages

FAQ

How often does UptimeVanguard check my sites?
You choose the interval per check. HTTP and ping checks can run every minute; the site form offers 1 to 60 minutes for HTTP, 1 to 30 minutes for ping, 5 to 60 minutes for DNS and 1 to 24 hours for TLS certificates. Through the API, intervals range from 60 to 86400 seconds.
What happens when a site goes down?
A failure from the primary region is confirmed by a second region. When both agree for at least 60 seconds, an incident opens and your channels are alerted. When the outage ends, the incident closes and a recovery alert is sent.
Can I monitor cron jobs?
Yes. Create a heartbeat and call its ping URL at the end of each successful run. An incident opens when no ping arrives within the interval plus the grace period.
Can I share uptime status with customers?
Yes. Create a status page in Settings, choose the services to show and share its /status URL.
How many sites can I monitor?
The trial lasts 7 days and includes 5 sites. On a paid plan, the limit is the number of sites you pay for. Open Billing to see your team's current allowance.
Is there an API?
Yes. The REST API v1 uses bearer tokens with scoped abilities and allows 60 requests per minute.

Still need help? Contact support