Know the moment it breaks.

Real alerts, honest pricing, and a status page your clients can trust.

Watch: a monitor is about to go down
dashboard.statusfox.app
StatusFox
Dashboard
Monitors
Status Pages
Alerts
Settings
All HTTP Ping DNS SSL
+ Add Monitor
99.97%
Overall Uptime
47/50
Monitors Active
142ms
Avg Response
0
Incidents
NameMonitorStatusUptimeRespTrendInt.Rgn
API
api.example.com/health
UP
99.99%
142ms
30s
FR1
Shop
shop.example.com
UP
99.97%
89ms
60s
VA1
Pay
payments.example.com/api
UP
100%
156ms
15s
TK1
CDN
cdn.example.com/assets
UP
100%
23ms
60s
FR1
DB
db.example.com:5432
UP
99.95%
8ms
30s
VA1
Auth
auth.example.com/oauth
UP
99.98%
210ms
30s
TK1
Verifying from 3 regions...
🇩🇪 Frankfurt
🇯🇵 Tokyo
🇺🇸 Virginia
3/3 confirmed — Alert sent
Incident Alert
payments.example.com is DOWN
Sent to #incidents + PagerDuty
just now

Your monitoring tool is lying to you.

Noisy monitors train your team to ignore them. You mute the channel, raise the thresholds, settle into a wait-and-see habit. Then a real outage slips through. The answer is not louder alerts, it is alerts that follow a rule you can trust.

With typical monitoring
Alert fires api.example.com latency > 500ms
Team ignores it 12th alert today, probably another false positive
Another alert fires Same endpoint, different threshold. Still ignored.
Slack channel muted Can't focus with constant noise, notifications silenced
REAL OUTAGE, 47 min later a customer tweets about it
VS
With StatusFox
Alert fires Same endpoint detected down
Verified from 3 regions Confirmed real — not a false positive
Team responds Slack and email fire the moment it is confirmed
Resolved before customers notice
Paste and go

Paste your cURL. You're monitoring.

Copy a request from your browser devtools and paste it. We read the URL, method, headers, and auth tokens straight from it, and your monitor is live.

dashboard.statusfox.app
All HTTP Ping
+ Add Monitor
2/50
Monitors
99.98%
Avg Uptime
116ms
Avg Response
0
Incidents
NameMonitorStatusUptimeRespTrend
No monitors yet, paste a cURL to get started
API
api.example.com/health
UP
100%
142ms
WWW
shop.example.com
UP
99.97%
89ms
PAY
payments.example.com/api
UP
100%
156ms
Add Monitor
Paste a cURL command or enter a URL — we'll auto-detect everything
Cancel
Add Monitor
Monitor Active — Checking every 30s from 3 regions
Status Pages

Beautiful status pages your customers actually trust.

Public status pages with real uptime history and a clear incident timeline, updated as checks run. Embed one anywhere with a single script tag, or send customers a link.

StatusFox StatusFox
All Systems Operational
API Operational
Website Operational
CDN Degraded
Database Operational
Recent Incidents
CDN edge nodes experiencing elevated latency Investigating
Some users may experience slower asset loading. Our team is actively working with the CDN provider to resolve this.
Opened Apr 9, 14:23 UTC · Last update 2m ago
Alerts you can act on

Know exactly when, and exactly why.

Every alert follows a rule you can read: an incident opens when all 3 regions confirm the outage, and one success resolves it. Route it to Slack, email, or any webhook, with more channels on the way.

Incident Detected · api.example.com is DOWN
Alert routed to every channel you connect
Slack
Sent
Email
Sent
Webhook
Sent
White-Label

Your clients think you built it. You didn't.

Put your clients' status pages on your own domain, with your logo, your colors, and branded PDF reports. They see your brand, not ours.

status.acmecorp.com
Acme Corp
System Status
All Systems Operational
99.98% Uptime
142ms Avg Response
2 Incidents
4m 11s Avg Resolution
API Gateway
Operational
Web Application
Operational
Database Cluster
Degraded
CDN & Assets
Operational
Incident Management

From first failed check to resolved.

Every incident gets a timeline you can read: the checks that failed, when the alert went out, and when a successful check resolved it. It is the same record your status page shows your customers.

INC-2847: api.example.com unreachable
Resolved
14:23:01
Detected — 3/3 regions confirmed downtime
14:23:32
Alert sent — Slack #incidents, PagerDuty on-call
14:24:15
Acknowledged by @sarah.chen
14:26:40
Fix deployed — Rolling restart completed
14:27:05
Verification — 3/3 regions reporting healthy
14:27:12
Resolved — Total downtime: 4m 11s
Response Time
Developer-First

A REST API and signed webhooks. Build on top of us.

Create and manage monitors through a clean REST API. Every webhook is HMAC-signed, so you can verify each payload before you act on it. Wire StatusFox into the pipeline you already deploy with.

Terminal
# Create a monitor with one API call
curl -X POST https://api.statusfox.app/v1/monitors \
  -H "Authorization: Bearer sf_..." \
  -d '{
    "name": "Production API",
    "url": "https://api.example.com/health",
    "interval": 30
  }'
Response 201 Created
{
  "id": "mon_a1b2c3d4",
  "status": "active",
  "next_check": "2026-04-09T14:30:00Z"
}

Simple, transparent pricing

Commercial use on every plan. Channels included, not metered.

FREE

$0 /mo

5 monitors 1-minute checks 1 status page Email and Slack alerts 90-day history
Start Monitoring

STARTER

$19 /mo

25 monitors 30-second checks Custom domains Advanced alerting 1-year history
Start Monitoring

AGENCY

$249 /mo

Unlimited monitors 15-second checks Multi-team support Custom SLA reporting Priority onboarding & support SSO & audit logs
Start Monitoring

Common questions

Everything you need to know.

Every alert follows a rule you can read. A failed check is verified from 3 independent regions, and the incident opens when all 3 confirm the outage. One successful check resolves it, so a single blip will not page you.

As often as every 15 seconds on paid plans and every 60 seconds on the free plan. You set the interval per monitor.

Yes. Commercial use is allowed on every plan, including free.

Free includes 5 monitors, Starter includes 25, Pro includes 100, and Agency is unlimited.

Yes. Bring your monitors, URLs, and check intervals in one step.

Any HTTP or HTTPS endpoint, with custom methods, headers, request bodies, and expected status codes.

Stop ignoring your alerts.
Start trusting them.

Honest pricing, alerts you can act on, and a status page your clients can believe.