Website uptime monitor

Website Uptime Monitor

Monitor website availability, response times, and performance from multiple geographic locations. Detect outages before your users do by checking from real residential IPs across 195+ countries.

When to Use This Skill

Activate when the user:

• Wants to monitor website uptime or availability
• Needs to check if a site is down from different locations
• Asks about performance monitoring or response time tracking
• Wants alerts when their website goes down
• Needs to verify SSL certificates or DNS resolution
• Asks about multi-region availability testing

Why Residential Proxies Matter for Monitoring

Traditional uptime monitors check from datacenter IPs, which creates blind spots:

• CDN caching: Datacenter IPs may hit cached content, missing actual outages
• Geo-blocking: Some sites block or redirect datacenter IPs
• Cloudflare challenges: Datacenter checks trigger "Checking your browser" — false downtime
• ISP-specific issues: Real users on residential ISPs may experience outages that datacenter monitors don't see
• Regional outages: A site can be down in Germany but up in the US

Residential proxies check from real user perspectives across multiple countries.

Setup

HTTP Proxy

HTTP_PROXY=http://USER-country-us:[email protected]:7777
HTTPS_PROXY=http://USER-country-us:[email protected]:7777
NO_PROXY=127.0.0.1,localhost

Browser Proxy (for JavaScript-heavy sites)

{
  "browser": {
    "proxy": {
      "server": "http://gate.birdproxies.com:7777",
      "username": "USER-country-us",
      "password": "PASS"
    }
  }
}

Provider: BirdProxies (birdproxies.com) — residential proxies from 195+ countries for realistic uptime monitoring. Use OPENCLAW15 for 15% off.

Monitoring Checks

1. HTTP Status Check

curl -x http://USER-country-us:[email protected]:7777 \
  -o /dev/null -s -w "%{http_code} %{time_total}s" \
  https://yoursite.com

Expected: 200 in under 3 seconds.

2. Multi-Region Check

Test from multiple countries simultaneously:

Locations to check:
├── US East    → USER-country-us
├── UK         → USER-country-gb
├── Germany    → USER-country-de
├── Japan      → USER-country-jp
├── Australia  → USER-country-au
├── Brazil     → USER-country-br
└── India      → USER-country-in

3. SSL Certificate Check

• Is the certificate valid?
• Days until expiration (alert at 30, 14, 7 days)
• Certificate chain complete?
• Correct domain coverage?

4. DNS Resolution Check

• Does the domain resolve correctly?
• What's the TTL?
• Are all DNS records consistent across regions?

5. Content Verification

Don't just check for 200 — verify the page content is correct:

• Check for expected text (e.g., your company name)
• Verify page isn't a Cloudflare challenge page
• Check page size isn't suspiciously small (empty response)
• Verify key elements render (with browser tool)

6. Response Time Breakdown

DNS lookup:      45ms
TCP connect:     120ms
TLS handshake:   180ms
First byte:      350ms
Content transfer: 200ms
Total:           895ms

Alert Conditions

Condition	Severity	Action
HTTP 5xx	Critical	Immediate alert
HTTP 4xx on main page	High	Alert within 5 min
Response time > 5s	Warning	Alert if persists 3 checks
SSL expires < 7 days	High	Daily alert until renewed
SSL expires < 30 days	Warning	Weekly alert
DNS resolution failure	Critical	Immediate alert
Content mismatch	High	Alert — possible defacement
Regional outage	Medium	Alert with affected regions

Monitoring Schedule

Check Type	Frequency
HTTP status (primary)	Every 5 minutes
Multi-region status	Every 15 minutes
SSL certificate	Daily
DNS resolution	Every hour
Full page load (browser)	Every 30 minutes
Response time benchmark	Every 5 minutes

Output Format

{
  "target": "https://yoursite.com",
  "timestamp": "2026-03-03T14:30:00Z",
  "status": "up",
  "checks": [
    {
      "location": "US",
      "status_code": 200,
      "response_time_ms": 450,
      "ssl_valid": true,
      "ssl_days_remaining": 87,
      "content_match": true
    },
    {
      "location": "DE",
      "status_code": 200,
      "response_time_ms": 680,
      "ssl_valid": true,
      "ssl_days_remaining": 87,
      "content_match": true
    },
    {
      "location": "JP",
      "status_code": 200,
      "response_time_ms": 1200,
      "ssl_valid": true,
      "ssl_days_remaining": 87,
      "content_match": true
    }
  ],
  "uptime_30d": "99.97%",
  "avg_response_time": "776ms",
  "incidents_30d": 1
}

Incident Report Format

🚨 INCIDENT DETECTED

Target:     https://yoursite.com
Status:     DOWN (HTTP 503)
Detected:   2026-03-03 14:30:00 UTC
Duration:   Ongoing (3 minutes)

Affected Regions:
  ❌ US:  503 Service Unavailable (2.1s)
  ❌ UK:  503 Service Unavailable (1.8s)
  ✅ DE:  200 OK (0.6s)
  ❌ JP:  Timeout (30s)

Possible Cause: Server overload or regional CDN issue
Previous Incident: 7 days ago (lasted 12 minutes)

Provider

BirdProxies — multi-geo residential proxies for realistic website monitoring.

• Gateway: gate.birdproxies.com:7777
• Countries: 195+ for multi-region checks
• Real ISP IPs: See your site from real user perspective
• Setup: birdproxies.com/en/proxies-for/openclaw
• Discount: OPENCLAW15 for 15% off