How many regions check by default, and does it matter?

The default is multiple geographic regions. Multi-region checks defend against false alarms from a single region's network being briefly broken; if all checks must agree before alerting, you trade a small delay-to-alert for a large reduction in noise. Set the required-down threshold thoughtfully: 3 of 5 regions down is a useful middle ground.

Does the check origin's IP need to be allowlisted?

If your endpoint is firewalled, yes — DO Uptime checks come from specific IP ranges that you can allowlist. For public-facing endpoints exposed to the internet, the IPs are reachable without special configuration. DigitalOcean publishes the current check-source IP ranges in their documentation.

DO Uptime Check Builder

MonitoringDigitalOcean

Build DigitalOcean uptime monitoring checks with HTTP/HTTPS/TCP probes and latency alerts.

Last verified: May 2026

DigitalOcean Uptime Monitoring Configuration

Build DigitalOcean uptime monitoring check configurations with HTTP/HTTPS/TCP checks, multi-region probes, latency alerts, and SSL expiry notifications.

Required Fields

checks

{
  "checks": [
    {
      "name": "Website Homepage",
      "type": "https",
      "target": "https://example.com",
      "regions": ["us_east", "eu_west", "se_asia"],
      "enabled": true
    },
    {
      "name": "API Health",
      "type": "https",
      "target": "https://api.example.com/health",
      "regions": ["us_east", "us_west", "eu_west", "se_asia"],
      "enabled": true
    },
    {
      "name": "Database Connectivity",
      "type": "tcp",
      "target": "db.example.com:5432",
      "regions": ["us_east"],
      "enabled": true
    }
  ],
  "alerts": [
    {
      "check_name": "Website Homepage",
      "name": "Website Down Alert",
      "type": "down_global",
      "threshold": 3,
      "period": "2m",
      "comparison": "greater_than",
      "notifications": {
        "email": ["ops@example.com", "oncall@example.com"],
        "slack": [
          {
            "channel": "#incidents",
            "url": "https://hooks.slack.com/services/T00/B00/xxxx"
          }
        ]
      }
    },
    {
      "check_name": "API Health",
      "name": "API Latency Alert",
      "type": "latency",
      "threshold": 500,
      "period": "5m",
      "comparison": "greater_than",
      "notifications": {
        "email": ["ops@example.com"]
      }
    },
    {
      "check_name": "Website Homepage",
      "name": "SSL Expiry Alert",
      "type": "ssl_expiry",
      "threshold": 30,
      "comparison": "less_than",
      "notifications": {
        "email": ["ops@example.com"]
      }
    }
  ]
}

Generated Output

Output will appear here...

See It in Action

Your e-commerce site went down for 12 minutes on a Saturday night and nobody noticed until morning emails started arriving. The internal Kubernetes liveness probes were green — the application was running, but Cloudflare's origin certificate had expired and external clients were getting TLS errors. You set up DO Uptime checks against the public hostname from three regions, with TLS validation enabled, and route alerts to PagerDuty. Next time a certificate problem hits, you get a page within 5 minutes from outside the perimeter.

What This Tool Does

DigitalOcean Uptime Monitoring runs synthetic checks from multiple global regions against an HTTP, HTTPS, or TCP endpoint and alerts when checks fail. The DO Uptime Check Builder produces complete check definitions — target URL, expected status, latency threshold, regions to check from, and alert routing — and surfaces the relationship between check frequency, region count, and what 'down' actually means.

Technical Details

The builder collects the check name, target URL, check type (HTTP, HTTPS, TCP, ping), expected status (200 or a custom list), regions to check from, frequency (1-15 minutes), and notification policy. It validates the URL is reachable and the configuration is consistent (HTTPS requires a TLS endpoint; TCP requires a port). Output is a `digitalocean_uptime_check` Terraform resource plus associated alert policies.

Common Use Cases

1Setting up external uptime checks for a public-facing site that complement internal health checks running inside the cluster.
2Tuning a check that fires false alarms when a single region's internet path is briefly disrupted by adding a 'down in N of M regions' policy.
3Adding latency-budget checks that alert when response time exceeds 2 seconds even though the endpoint is technically returning 200.
4Documenting external uptime checks for a status-page or SLA-reporting workflow.

Common Questions

How many regions check by default, and does it matter?: The default is multiple geographic regions. Multi-region checks defend against false alarms from a single region's network being briefly broken; if all checks must agree before alerting, you trade a small delay-to-alert for a large reduction in noise. Set the required-down threshold thoughtfully: 3 of 5 regions down is a useful middle ground.
Does the check origin's IP need to be allowlisted?: If your endpoint is firewalled, yes — DO Uptime checks come from specific IP ranges that you can allowlist. For public-facing endpoints exposed to the internet, the IPs are reachable without special configuration. DigitalOcean publishes the current check-source IP ranges in their documentation.

Expert Tips

TIP

Don't check `/` — pick a route that exercises the dependency chain you actually care about. A check that hits `/api/health` and verifies a database round-trip catches problems a static-page check would miss.

TIP

Pair uptime checks with status-code AND latency thresholds. An endpoint returning 200 with a 30-second response time is functionally down for users, but a status-only check would call it healthy.

Was this tool helpful?

Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.