Uptime checks that explain the failure.

Q: How often can a monitor check?

As often as every 30 seconds on paid plans, and every 3 minutes on the free plan. Query and heartbeat monitors keep whole-minute schedules.

Q: Which check types are there?

HTTP and query monitors are on every plan. Heartbeat, keyword, TLS certificate, TCP, DNS, domain, and mail server checks are on Team and up.

Q: How does Squasher avoid false alarms?

You set how many failed checks in a row open an incident. A monitor can check from up to 6 locations and fail only when enough of them agree, and a single-location failure is confirmed from a second location first.

Q: What does a failed check keep?

The HTTP status and headers, the first 2 KB of a text body, the DNS, TCP, and TLS timings, and which locations failed. Cookies, tokens, and keys are removed before it is stored.

Q: Can a monitor watch my own data, not only a URL?

Yes. A query monitor compares a number from your data with a threshold: error logs a minute, request latency, ingest delay, a metric, or Web Vitals. You can backtest it over the last day or week first.

Q: Which checks are not offered?

Ping, UDP, and browser or scripted page checks. Monitors run on an edge network without ICMP, UDP, or a browser. Use a TCP check for a port and an HTTP or keyword check for a page. You cannot run a check by hand.

Monitors check your endpoints, jobs, and data. A failure opens an incident with the evidence of the failed check, and recovery resolves it.

Start free

Free plan. No credit card required.

app.squasher.ai/acme/checkout-api/monitors

acmecheckout-apiMonitors

Search⌘ K

checkout errors

Healthy

Query monitor · error logs on checkout-api per minute · fails above 20.

Last 18 minutesThreshold 20

Recent evaluations

Failed at 14:06 · incident openedRecovered at 14:31 · incident resolved

Example query monitor

Checks for what can break.

Endpoints, certificates, ports, records, jobs, and your own telemetry.

HTTP and keyword
Status code, response time, and a word that must or must not be in the body.
TLS and domains
Certificate validity and expiry, DNS records, and domain resolution, on Team and up.
Heartbeats
Your cron job calls a URL. A missed or failed run fails the monitor, on Team and up.
Query monitors
A threshold on error logs, latency, metrics, or Web Vitals, with a backtest first.
Checks every 30 seconds
On paid plans. From up to 6 locations, with a quorum before an incident opens.
Incidents on their own
Failure and recovery thresholds open and resolve the incident and notify your routes.

The failed check keeps its evidence.

An HTTP or keyword failure stores what a responder would check first.

DNS lookup, TCP connect, and TLS handshake times, with the certificate.
The HTTP status, the response headers, and the first 2 KB of the body.
Which locations failed, and the latest failure on the incident.
Credentials, cookies, and tokens removed before anything is stored.

Failure evidence

checkout-api
pricing
web
webhooks
30 checks · 3 regions1 failed · incident opened

SEV-2checkout-api: error burstInvestigatingIdentifiedResolved
SEV-3Webhook deliveries failing with 502Monitoring
SEV-4Slow pricing queryResolved

Example monitors and incidents.

Monitors drive the status page.

Link a status page component to a monitor, and the page follows each check.

Each component shows 90-day uptime and response times.
A monitor can publish its incident after a delay that you set.
Subscribers get the update by email.

Status pages

app.squasher.ai/acme/checkout-api/status-pages

acmecheckout-apiStatus pages

Search⌘ K

status.acme.com

Public

Status page for checkout-api.

All systems operational

Checkout	Operational
Payments	Operational
Web app	Operational
Webhooks	Operational

Example project and data

What works today, and what does not.

Uptime monitoring is live on every plan. Some check types are not offered.

HTTP and query monitors

Today: Yes
Notes: Every plan

Heartbeat, keyword, TLS, TCP, DNS

Today: Yes
Notes: on Team and up

Several check locations

Today: Yes
Notes: Up to 6, by plan

Ping and UDP checks

Today: No
Notes: Use a TCP check for a port

Browser or scripted checks

Today: No
Notes: Use an HTTP or keyword check

Run a check on demand

Today: No
Notes: Checks run on their schedule

What Uptime Monitoring That Opens Incidents with Evidence covers today, and what is in beta or not built yet.
Feature	Today	Notes
HTTP and query monitors	Yes	Every plan
Heartbeat, keyword, TLS, TCP, DNS	Yes	on Team and up
Several check locations	Yes	Up to 6, by plan
Ping and UDP checks	No	Use a TCP check for a port
Browser or scripted checks	No	Use an HTTP or keyword check
Run a check on demand	No	Checks run on their schedule

Checked against the product on 2026-10-20.

Add a monitor in three steps.

Start from a template, add a heartbeat for your jobs, and route the incidents.

Create a monitor

The http-health template checks a URL for a 200 response.

squasher monitors create-from-template --project "$SQUASHER_PROJECT_ID" http-health \  --inputs '{"url":"https://example.com/health"}'

Create a monitor

Add a heartbeat for a job
Call the heartbeat URL at the end of each run, on Team and up.
```
curl -fsS https://api.squasher.ai/v1/heartbeats/<token>
```
Route the incidents
Send them to Slack, Teams, Telegram, email, a webhook, or PagerDuty.
Notification routing

Paste into your coding agent

Install Squasher for this project. If Squasher skills or MCP are not configured in this agent environment, run `bash <(curl -fsSL https://squasher.ai/install.sh) --agents -y`. Then read https://skills.squasher.ai/squasher-onboard/SKILL.md, map every runnable app/service/worker/frontend/agent in the repo, choose the matching Squasher SDK, log drain, OTLP, or Agent SDK path, initialize with SQUASHER_API_KEY and SQUASHER_PROJECT_ID from environment variables, send one real verification event, and report the files changed plus the verification step. Do not hardcode or reveal real API keys.

bash <(curl -fsSL https://squasher.ai/install.sh) --agents -y

Questions, answered.

How often can a monitor check?

As often as every 30 seconds on paid plans, and every 3 minutes on the free plan. Query and heartbeat monitors keep whole-minute schedules.

Which check types are there?

HTTP and query monitors are on every plan. Heartbeat, keyword, TLS certificate, TCP, DNS, domain, and mail server checks are on Team and up.

How does Squasher avoid false alarms?

You set how many failed checks in a row open an incident. A monitor can check from up to 6 locations and fail only when enough of them agree, and a single-location failure is confirmed from a second location first.

What does a failed check keep?

The HTTP status and headers, the first 2 KB of a text body, the DNS, TCP, and TLS timings, and which locations failed. Cookies, tokens, and keys are removed before it is stored.

Can a monitor watch my own data, not only a URL?

Yes. A query monitor compares a number from your data with a threshold: error logs a minute, request latency, ingest delay, a metric, or Web Vitals. You can backtest it over the last day or week first.

Which checks are not offered?

Ping, UDP, and browser or scripted page checks. Monitors run on an edge network without ICMP, UDP, or a browser. Use a TCP check for a port and an HTTP or keyword check for a page. You cannot run a check by hand.

On squasher.ai

In the docs

Reliability

Priced by volume, never by seat.

Start free. Invite the whole team. AI triage is included on every plan.

Compare every plan

Free

For side projects, evals, and internal tools.

$0/ month

No card needed. No overage charges.

10K errors
5 GB telemetry
1K replays
150K monitor checks

Included

AI triage on new issues
500 AI credits / month (an investigation uses 50)
1 project

Pro

For small production apps that want one tool, not five.

$29/ month

Flat price. No per-seat fees.

150K errors
100 GB telemetry
10K replays
2.6M monitor checks

Everything in Free, plus

3,000 AI credits / month (an investigation uses 50)
5 projects
30 monitors with 30-second checks

Team

Scale

For high-volume teams with security, procurement, and support needs.

$299/ month

Flat price. No per-seat fees.

3M errors
1 TB telemetry
150K replays
21.6M monitor checks

Everything in Team, plus

30,000 AI credits / month (an investigation uses 50)
250 monitors with 30-second checks
Priority support

Need more volume, a security review, or custom terms? Get in touch.

Know before your customers do.

Add one HTTP monitor and see the first check in a few minutes.

Start free

Free plan. No credit card required.

Uptime checks that explain the failure.

Checks for what can break.

HTTP and keyword

TLS and domains

Heartbeats

Query monitors

Checks every 30 seconds

Incidents on their own

The failed check keeps its evidence.

Monitors drive the status page.

What works today, and what does not.

HTTP and query monitors

Heartbeat, keyword, TLS, TCP, DNS

Several check locations

Ping and UDP checks

Browser or scripted checks

Run a check on demand

Add a monitor in three steps.

Create a monitor

Add a heartbeat for a job

Route the incidents

Questions, answered.

How often can a monitor check?

Which check types are there?

How does Squasher avoid false alarms?

What does a failed check keep?

Can a monitor watch my own data, not only a URL?

Which checks are not offered?

Keep exploring.

On squasher.ai

In the docs

Reliability

Priced by volume, never by seat.

Free

Pro

Team

Scale

Know before your customers do.