Uptime and edge data are the difference between “the site is broken” and “the site has been broken for 4 hours and 17 minutes since 9:42pm.” SiteCMD pulls both so when an issue lands, you know whether your users are seeing it right now.

UptimeRobot

UptimeRobot connects via API key. The free tier of UptimeRobot is enough to use this integration meaningfully.

Setup

Sign in to UptimeRobot.
Go to My Settings (top right) and find API Settings.
Generate or copy the Main API Key (the one with read-only access works fine).
In SiteCMD, Settings → Integrations → UptimeRobot, click Connect.
Paste the API key.
Click Save.

You don’t need to specify which monitor to pull. SiteCMD reads all monitors on your account and matches them to your project URLs.

What it pulls

Current monitor status (up, down, paused, seems down)
30-day uptime ratio per monitor
Average response time
Response time history (recent series)
Downtime log (when each outage started and ended)

How it pairs with your URLs

UptimeRobot’s monitors are URL-based. SiteCMD matches monitors to your project URL with bidirectional contains so a monitor registered as https://example.com/ matches a project URL of https://example.com and vice versa. If you have URL-level differences (specific paths monitored separately), each gets its own row.

Where it shows up

Dashboard → Uptime card. Current status, 30-day uptime, recent response times.
Events timeline. Each outage and recovery becomes an event in the project’s unified timeline.
Issues page. Active outages appear as critical issues with the relevant scan findings (slow response, server errors) correlated on Core and above.

Cloudflare

Cloudflare connects via API token (Cloudflare’s modern auth, not the legacy global API key). You’ll create a scoped token in Cloudflare’s dashboard.

Setup

Sign in to your Cloudflare dashboard.
Click your profile icon → My Profile → API Tokens.
Click Create Token.
Use the Read all resources template, or create a custom token with at minimum:
- Zone → Analytics → Read for the zone you want SiteCMD to see.
Copy the token (you can only see it once).
In SiteCMD, Settings → Integrations → Cloudflare, click Connect.
Paste the API token.
Enter the Zone ID for the site you’re scanning. You’ll find this in the Cloudflare dashboard, on the zone’s overview page in the right sidebar.
Click Save.

What it pulls

Request and bandwidth totals over 30 days
Cache hit rate
Threats blocked (by Cloudflare’s WAF, bot management, etc.)
Unique visitors
Day-by-day breakdown

Why this matters

Cloudflare sits between your origin and your users. If Cloudflare’s cache hit rate drops, your origin is taking more traffic, which slows things down and costs more. If threats blocked spikes, someone is actively trying to break your site. Both are signals SiteCMD wants when interpreting a scan finding (“your response times got worse last week” pairs better with “cache hit rate dropped from 87% to 31% on the same day”).

What SiteCMD does not access

The token scopes are read-only and limited to analytics. SiteCMD can’t change DNS records, can’t modify firewall rules, can’t deploy Workers, and can’t access anything outside the zone you scoped the token to.

Disconnecting

Disconnect from SiteCMD’s settings to revoke our local copy of the token. To revoke the token entirely (so even a stolen copy can’t be used), delete it from Cloudflare’s API Tokens page.

Where the data shows up

Dashboard → Edge card. Cloudflare’s request volumes, cache hit rate, threats blocked.
Events timeline. Significant edge anomalies (cache hit rate collapse, traffic spike, threats spike) appear as events.

Privacy

Both UptimeRobot and Cloudflare requests go from your machine to their APIs directly. No SiteCMD server in between. SiteCMD stores aggregate metrics and event records locally for correlation; it doesn’t mirror your full Cloudflare logs or your full UptimeRobot monitor history.