Every protocol that matters
HTTP and HTTPS, raw TCP ports, ICMP ping, and DNS resolution: one monitor type for every layer of your stack.
Uptime Monitoring
Know the second
Know the second
it goes down.
HTTP, TCP, ICMP and DNS checks as fast as every 30 seconds, with a transient failure retried in place before anything is recorded, so one bad packet never pages you at 3am.
Free tier included
No credit card
2-minute setup
Uptime checks that earn their alerts.
A failure that looks like a network hiccup is retried immediately, in place, before any result is written. No flapping, no false pages. Just the truth about whether your users can reach you.
One US region, stated plainly
Checks run from AWS us-east-1. Additional check locations are on the roadmap and are not available today, and we would rather say that than imply a network of probes we do not operate.
As fast as every 30 seconds
Tighten the cadence on critical endpoints and relax it elsewhere, configurable per monitor, down to 30-second intervals.
Retried before it pages
A reset, a refused connection, a TLS abort or a resolver hiccup is retried in place before any result is recorded, so a one-off bad packet never becomes an alert.
Assertions, not just 200s
Require a status code, a response time ceiling, a keyword in the body, or a valid JSON path. A 200 that serves the wrong page still fails.
Alerts the moment it breaks
Route to Slack, Discord, Teams, Telegram, email, SMS, webhooks, or your on-call schedule, all included.
Confirmation, not noise
A bad packet shouldn't
A bad packet shouldn't
wake you up.
Most monitoring tools page you the instant a single check fails. We don't. A transport failure that looks transient is retried in place first, before any result is written, so the alerts you get are the ones that are actually real.
- Transient transport failures retried before any result is recorded
- Configurable retry logic and confirmation thresholds
- Automatic recovery detection and auto-resolve
checkout-api RecoveredLIVE
INCIDENTS · 30D1
MTTR4m 12s
FALSE PAGES0
attempt 1conn reset
attempt 2conn reset
attempt 396ms
recordedsuccess
Set up in minutes
Point us at a URL.
Point us at a URL.
That's the whole setup.
Paste a URL, pick your cadence and your assertions, and the first check runs immediately. No agents, no DNS changes, no waiting. Add a monitor from the dashboard or the REST API.
- No agent and no code change to monitor an endpoint
- Bulk-import monitors from a CSV or the REST API
- Provision and manage every monitor via JSON over HTTPS
add a monitor$ curl -X POST https://api.siteqwality.com/http/job \
-H "Authorization: Bearer $SQ_TOKEN" \
-d '{"uri":"https://api.acme.com/health","method":"GET","run_interval_seconds":60,"timeout_ms":10000}'
✓ monitor live · first check scheduled
-H "Authorization: Bearer $SQ_TOKEN" \
-d '{"uri":"https://api.acme.com/health","method":"GET","run_interval_seconds":60,"timeout_ms":10000}'
✓ monitor live · first check scheduled
30s
fastest configurable check interval
100%
of transient transport failures retried before recording
8+
alert channels, included on every plan
$0
free tier, no credit card needed to start
FAQ
On a 30-second cadence, a confirmed failure typically reaches you within a minute, the time it takes to re-check so the alert is real.
HTTP and HTTPS, raw TCP port checks, ICMP ping, and DNS resolution. You can also assert on status codes, response times, response-body keywords, and JSON paths.
A transient transport failure is retried in place before any result is recorded, so a reset or a resolver hiccup that succeeds on the retry never reaches you at all. A response that genuinely fails is recorded as a failure.
No agent, no SDK, no DNS changes. Paste a URL and the first check runs immediately. You can also manage monitors programmatically via the REST API.
Yes. The free tier includes uptime monitoring with no credit card. Add capacity and faster cadences only as you grow.
Related features
Start free. No credit card.
Uptime, cron, synthetic, logs, RUM, incidents, and status pages. Free tier on every product.