Plan limits reference
Your account’s limits come from its plan (package). Plans and their numbers change over time, so this page describes what a plan controls and where to read your own numbers, rather than copying figures that would go stale. Current plans and prices are on the plan comparison at /en/payment/packages.
Read your exact limits
Section titled “Read your exact limits”- In the app: Billing -> Packages shows your plan, what it includes and how much you use.
- Through the API:
GET /account(scopeaccount:read) returnspackage.features(the entitlement map, with the same names a403 package_limiterror uses in itsfeaturefield),usage(used vs allowed per area),limits(for example the allowedintervalsandmaxBulkItems) andoverlimits(which areas are over).GET /account/usagereturns just the usage block. MCP:get_account,get_account_usage. GET /monitor/typewith a token shows, per monitor type, your minimum interval and whether you can create it.
What a plan controls
Section titled “What a plan controls”| Area | What is limited | Refusal when exceeded |
|---|---|---|
| Monitors | How many monitors you can have; whether extra monitors beyond that can be added for a fee or are blocked. | 403 package_limit (or create disabled with onOverlimit: "disable") |
| Check interval | The fastest interval, overall and per monitor type. | 422 invalid_interval (lists allowed values), 403 package_interval_conflict |
| Monitor types | Per-type counts, intervals, maximum page size, keyword and policy options. | 403 package_limit |
| Cron scheduling | Whether monitors can run on a cron schedule instead of an interval. | 403 package_limit |
| Assertions | How many assertion rules a monitor may carry (at most 20), and whether the previous-check family (previous., delta) is included. |
403 package_limit |
| DNS and TLS options | Choosing public or custom DNS resolvers; TLS policy switches and online revocation checks. | 403 package_limit |
| Attached sub-checks | Which of blacklist, SSL expiry, domain expiry and Web Risk can be attached to HTTP monitors. | 403 package_limit |
| Check log detail | How finely checks are logged (full log: 5-minute groups; otherwise 60-minute groups), and access to the full failing-check list of an incident. | 403 package_limit |
| Contacts | How many contacts, overall and per channel (some plans exclude voice calls, for example). | 403 package_limit |
| SMS and voice | The free message balance that comes with the plan and the credit level. Messages beyond it are paid from your balance. | 402 insufficient_balance |
| Reports | Which report frequencies (daily, weekly, monthly, quarterly, yearly) you can subscribe to. | 403 package_limit |
| Subaccounts | Whether you can invite subaccounts with their own rights. | 403 package_limit |
| API | Whether API access is included, and the per-minute and per-month call windows per scope. | Token creation refused; 429 quota_exceeded |
| Support | Whether the plan includes support. | - |
| Status pages | Pages, components per page, confirmed subscribers, SLA target / Google Analytics / no-index. | 403 package_limit - see status page plan limits |
Not limited by plan: maintenance windows (unlimited on every plan) and webhooks (20 per account on every plan).
Plan families
Section titled “Plan families”| Family | Shape |
|---|---|
| Free | A couple of monitors - for trying the product or watching a small site. |
| Solo / Personal | For one person with one or a few sites; Solo checks a single monitor every minute. |
| Webmaster | More monitors, faster intervals and more contacts; unlocks status page SLA and white-label settings. |
| Business | Team-sized monitor counts, more status pages, higher assertion caps, API access. |
| Enterprise | The largest monitor counts (several sizes), the most status pages and subscribers, API access. |
| 30-day trial | A time-limited plan with a high monitor count, for evaluating before you choose. |
When you go over a limit
Section titled “When you go over a limit”Limits gate what you can add. A downgrade does not delete anything:
- Monitors or contacts over the new limit are disabled (reported as
overlimited, and inGET /accountoverlimits) until you upgrade or remove enough of them. Their configuration is kept. - Settings the new plan does not include are kept but stop applying until you upgrade.
- Status pages keep working; components and subscribers over the limit are handled as described in status page plan limits.
- Existing API tokens keep working; new tokens need a plan with API access.