Status · Plans and data
Limits
A Status plan sets two things: how many monitors a project may have, and how often each can be checked. Everything else is the same on every plan.
Limits by plan
Loading the limits…
Monitors
Every monitor of the project counts, HTTP checks and heartbeats alike, paused ones too. A removed monitor doesn't. The project's sidebar shows how many it has against its plan's.
Past the limit, a new monitor is refused, whether you add it on its page or a deploy's list brings it, and the message says how many the plan has room for. A list that swaps one monitor for another still fits, because it's counted as a whole: the monitors added by hand and every one listed.
The monitors you have keep being checked. A smaller plan takes none away: a project over its new limit keeps them all, and can add more once it's under it again.
Checks at least every
This is the shortest time between two checks of one HTTP check: 30 seconds, 1 minute or 5 minutes. On the form, the intervals shorter than your plan allows are shown with the plan's name, and can't be chosen. In a deploy's list, a shorter interval is refused, and a monitor with none is checked as often as the plan allows.
After a move to a smaller plan, the checks that ran more often than it allows run at its shortest from then on. Heartbeats aren't affected: their job decides when they're called.
When a payment fails or a subscription ends
- A payment failed: everything goes on working, and the project's pages say by when to pay.
- The subscription ended: the project is read-only. Its monitors are no longer checked, nothing new can be added, a deploy's list is refused with
402, and the public page says it isn't available. Everything comes back once Status is bought again.
Plans, payments and cancelling are handled at id.my-beast.com, under the workspace's subscription. The terms say how developer services renew and end.
Limits on every plan
| What | Limit |
|---|---|
| Check timeout | 10 seconds for the whole answer |
| "The answer contains" | Looked for in the first 512 KB, up to 200 characters |
| Heartbeat period | 1 minute to 10,080 minutes (a week), with a grace of up to 1,440 minutes (a day) |
| Pings | 60 a minute per heartbeat; the last 10 KB of a ping's output kept |
| Webhook endpoints | 10 per project, 5 seconds to answer |
| API requests | 120 a minute per server secret |
| Monitors in one list | 200 per PUT /monitors |
| Maintenance window | Up to 240 minutes from the API, up to a week on the Maintenance page |
| Server secrets | 5 active at once per project, so two can overlap while you replace one |