TraceCrowd beta
FAQ

Questions we’ve been asked.

If something’s missing, email us — a human replies.

Product

3 questions

How is this different from UptimeRobot / Pingdom / Better Stack?

It’s opinionated and compact. No status pages, no synthetic transactions, no “AI root-cause” panels. Just uptime, alerts, and incidents. Cheaper per monitor, no per-seat upsell, no contract to sign. If you need the full enterprise suite, those are better.

What does a check actually verify?

By default: the response status is in 200–299. You can tighten it — require a specific status, require a keyword in the body, check SSL validity, set custom headers, pick GET/HEAD/POST, and choose whether to follow redirects.

Does it work for internal services?

Anything reachable from the public internet works, including endpoints behind auth headers or IP allowlists. For VPC-only endpoints, email us — we can talk through options.

Alerts & reliability

3 questions

Where do the checks run from?

Today: a single region in Europe. Multi-region (US / APAC) is next on the roadmap so a regional CDN hiccup doesn’t create false alarms.

How fast do I get paged?

Within seconds of a confirmed failed check. On a 1-min interval your worst case is roughly 60s detection + alert delivery. Slack and webhooks go out instantly; email is bounded by your provider and is usually sub-second.

Who gets notified when something breaks?

Whoever you attach to the monitor: email contacts and any Slack or webhook integrations. Routes are per-monitor, so a staging blip doesn’t wake the production on-call.

Pricing & account

1 question

What’s it cost?

Free during beta. Pricing will land when we exit beta — flat per-workspace, not per-seat. We promise to not make you talk to a salesperson. Details on the pricing page.

Still have questions?

Email a human. We answer quickly and don’t hand you off to a chatbot.