Monitor from 6 continents
UpCanary checks your services from monitoring regions across the globe. Multi-region consensus eliminates false positives so you only get alerted for real outages.
Monitoring regions
Every check runs from the regions you select. By default, all 6 are active. 1 credit = 1 check, regardless of how many regions run it. No per-region surcharge.
US Central
Iowa, USA
Covers North America. Ideal baseline for US-hosted infrastructure, CDNs, and SaaS applications.
South America East
São Paulo, Brazil
Covers Latin America. Detects routing issues and CDN edge failures specific to the South American continent.
Europe West
Belgium
Covers EU and surrounding regions. Critical for GDPR-compliant services and European customer bases.
Asia South
Mumbai, India
Covers South and Central Asia. Identifies performance issues on high-latency routes common in the region.
Asia Northeast
Tokyo, Japan
Covers East Asia and Pacific Rim. Essential for services targeting Japan, Korea, and surrounding markets.
Australia Southeast
Sydney, Australia
Covers Oceania and the southern Pacific. Catches issues with undersea cable routing and regional CDN nodes.
Multi-region consensus
An alert only fires when 2 or more regions independently confirm the service is down. This eliminates false positives from transient network issues, BGP hiccups, or CDN edge failures.
How it works
Check runs from all selected regions
Each region independently sends a request to your service and records the result.
Results are correlated
UpCanary compares results across regions. A single failure is treated as a potential regional blip.
Alert fires only on consensus
When 2+ regions confirm the outage, the alert fires and your status page updates automatically.
Consensus in practice
| Regions down | Alert? | Reason |
|---|---|---|
| 0 of 6 | No | All clear |
| 1 of 6 | No | Likely a regional blip |
| 2 of 6 | Yes | Confirmed outage |
| 3+ of 6 | Yes | Widespread outage |
Without consensus, a temporary packet loss event on a single network path would trigger a false alert. With consensus, only real outages reach your team and your users.
Why single-region monitoring fails
Monitoring from just one location means any network blip between that location and your server triggers a false alarm. Here is what can cause a single region to fail while your service is perfectly healthy.
Transient packet loss
A brief routing issue between the monitoring node and your server. Self-resolves in seconds, but triggers an alert anyway.
CDN edge failure
One CDN edge node goes down while the rest of the world is served correctly. Single-region monitoring sees a full outage.
BGP routing hiccup
A BGP change reroutes traffic through a slower or failing path for one region. Other regions are completely unaffected.
DNS resolution failure
A regional DNS resolver has a brief caching or upstream issue. Your service is up, but one location can't resolve it temporarily.
Monitoring protocols
Every protocol runs from all selected regions simultaneously. Combine multiple check types to get complete coverage of your infrastructure.
HTTP / HTTPS
Monitor websites and APIs. Validates status codes, response times, SSL certificates, and response body content.
- Status code validation
- Response time thresholds
- Content body matching
- Custom headers and auth
TCP
Check that any TCP port is accepting connections. Databases, mail servers, game servers, custom services.
- Port availability checks
- Connection timeout detection
- Response time measurement
- Any port, any service
DNS
Verify DNS resolution returns expected records. Catch propagation issues and misconfigurations early.
- A, AAAA, CNAME, MX records
- Propagation tracking
- Expected value validation
- Multiple record types
Ping (ICMP)
Basic host reachability checks for any IP address or hostname. The simplest way to verify a server is online.
- Host reachability
- Round-trip latency
- Packet loss detection
- IP or hostname
SSL Certificate
Get alerted before your SSL certificate expires. Included free with every plan, checked once per day.
- Expiry date monitoring
- Configurable warning thresholds
- Chain validation
- Free with all plans
Domain Expiry
Never let a domain expire accidentally. UpCanary checks your domain registration and alerts you before renewal.
- Registration expiry alerts
- Configurable thresholds
- WHOIS data tracking
- Free with all plans
Check intervals
Configure how often each monitor runs. Shorter intervals mean faster detection but consume more credits. Longer intervals are great for services where a few minutes of delay is acceptable.
| Interval | Checks/day | Credits/month |
|---|---|---|
| 30 seconds | 2,880 | ~86,400 |
| 1 minute | 1,440 | ~43,200 |
| 5 minutes | 288 | ~8,640 |
| 15 minutes | 96 | ~2,880 |
| 1 hour | 24 | ~720 |
No per-region pricing
Unlike other monitoring providers that charge per region or limit region access to higher tiers, UpCanary includes all 6 monitoring regions at no extra cost.
1 credit = 1 check
Regardless of whether you select 1 region or all 6, a single check consumes exactly 1 credit. Multi-region consensus is free. SSL and domain expiry checks are free. You should default to all regions for maximum coverage and false-positive protection.
Example: 10 monitors, 1-minute interval
10 monitors × 1,440 checks/day = 14,400 credits/day = ~432,000 credits/month. With the Pro credit package ($30 for 1.5M credits), that costs about $8.64/month in credits.
Stop lying to your users.
Start building trust.
Get honest, automated status pages powered by real monitoring. Sign up today and get 200,000 free credits to start monitoring.
Free plan available · No credit card required · Setup in under 5 minutes