Frequently Asked Questions

Packs make monitoring simple and predictable. Each pack bundles a fixed number of observations (43,200 = one site × one region × one-minute checks × 30 days). An observation is one reading about one thing you monitor: a check we ran from one region, or one your own code sent us. Instead of worrying about per-request billing, users think in terms of "How much do I want to watch continuously?"

Every account includes a small free pack allocation each month. As long as usage stays within that limit, there's no charge. If usage exceeds the free quota, billing is based on additional packs consumed.

Purchased packs increase your balance immediately. They're consumed automatically as your monitoring runs. Balance history and monthly usage clearly show how free quota and paid packs were applied.

Packs abstract away raw observation counts. They align with real-world usage — monitoring one site per region with one-minute intervals. One unit covers everything: our checks and the heartbeats or events you send yourself are priced the same, so adding your own signals needs no new maths. It's also developer‑friendly: balances, history, and usage can be tracked via API and UI.

If your balance reaches zero, monitoring for your sites will automatically stop. To resume checks, simply top up your balance by purchasing more packs. This ensures clear usage limits and prevents unexpected overages.

Monitoring results are retained for 60 days by default. After that, they're automatically removed to keep the service efficient and predictable.