Limits and allowances
What each plan includes, what add-ons cost and where up4 stops runaway use. The numbers come from the product itself and can change; the terms are binding.
What each plan includes
| Starting credit | Pay as you go | Team | Agency | |
|---|---|---|---|---|
| Monitors | 50 | No plan limit | 100 | 500 |
| Scheduled jobs | 20 | No plan limit | 100 | 1,000 |
| Status pages | 3 | No plan limit | 10 | 500 |
| Alert channels | 20 | No plan limit | 50 | 100 |
| Regions per monitor | 4 | 4 | 4 | 4 |
| History kept, days | 62 | 62 | 90 | 365 |
| Team members | No limit | No limit | No limit | No limit |
| Custom status page domains | None | Metered by day | 1 | 10 |
| E-mail subscribers on status pages | 100 | 250 included, more metered | 1,000 | 1,500 |
| Incident screenshots a month | Metered | Metered | 500 | 2,500 |
| Add-ons | No | No | Yes | Yes |
Checks, check-ins and, on pay as you go, screenshots are metered; what costs money says how. Team includes usage worth €180 a month and Agency €600, both at list price.
After a first payment, pay as you go has no limit on the number of monitors, scheduled jobs, status pages and alert channels. A paid pay-as-you-go Company can have 10 published status pages without a business feature at once. The subscriber import for status pages waits for the first payment.
When a plan's check budget is used up, up4 blocks only new load: new monitors, shorter intervals and more regions. Running monitors keep their interval, and no overage is charged. Credit and plans.
Add-ons
Add-ons raise one limit of a Team or Agency plan in fixed packs. Book them under Add-ons. Pay as you go and the starting credit do not book packs; they meter the same things instead. Only owners and administrators can book.
| Add-on | One pack | Per month, net |
|---|---|---|
| Custom domains | 1 domain | €2 |
| E-mail subscribers | 1,000 subscribers | €5 |
| Incident screenshots | 1,000 screenshots a month | €5 |
| Monitors | 50 monitors | €4 |
| Scheduled jobs | 100 scheduled jobs | €4 |
| Checks | 10 million checks a month (list value €90) | €8 |
- Each kind takes up to 20 packs and is one line on the invoice.
- More takes effect at once. You pay the prorated amount for the rest of the billing period with your saved payment method after one confirmation. A reduction applies when the paid period ends and you can take it back until then. There is no refund.
- With a yearly plan a pack costs its yearly price, ten monthly prices for twelve months.
- Screenshot and check packs count for the UTC calendar month, prorated in the month you book them. Capacity packs for domains, subscribers, monitors and jobs are there in full at once.
- Over a limit, for example after reducing packs, nothing is deleted and running monitors keep running. Adding more of that kind waits until you are under the limit or book a pack.
- A declined card leaves the change pending until you pay the invoice. The plan keeps running and no grace mode starts.
- Packs end with the subscription. On a switch between Team and Agency the packs are adjusted to what the new plan does not already include.
- Status pages are not sold in packs. Agency has no price per page, only the plan limit above.
Protection limits
A protection limit stops a runaway script, a loop or a typo from harming the service or other customers. It is not a price and does not cut what your plan includes. Normal use stays well below. When you reach one, that action is declined with a message that names the limit.
Select Request a higher limit in that message to ask for a higher one. It opens a support message with your Company and the limit filled in. Add a line on what you need it for.
Tests and Check now
| Starting credit | Pay as you go | Team | Agency | |
|---|---|---|---|---|
| Wait between two tests of one alert channel | 30 seconds | |||
| Channel tests and test alerts per Company, a day | 100 | |||
| Alert channels reached by one test alert | 10 | |||
| Check now runs per Company, a day | 500 | |||
| Check now runs at the same time | 3 | |||
| Check now runs per Company, a minute | 10 | |||
Reports and storage
| Starting credit | Pay as you go | Team | Agency | |
|---|---|---|---|---|
| Report schedules | 50 | 50 | 100 | 500 |
| Recipients across all schedules | 500 | 500 | 1,000 | 5,000 |
| Manual report runs per Company, a day | 20 | 20 | 20 | 100 |
| Attachments and report files together | 2 GiB | 2 GiB | 5 GiB | 25 GiB |
| Attachments per incident | 25 | |||
| Views of one report share link, an hour | 60 | |||
| Size of one attachment | 10 MB | |||
| New share links expire after | 90 days, unless you choose to keep them | |||
Alert plans and alert floods
| Starting credit | Pay as you go | Team | Agency | |
|---|---|---|---|---|
| Steps per Alert plan | 10 | |||
| Targets per step | 50 | |||
| Alert deliveries per Company and hour before further alerts arrive as one summary | 1,000 | 1,000 | 1,000 | 5,000 |
| Status changes of one scheduled job an hour before its alerts are bundled | 6 | |||
Integrations and invitations
| Starting credit | Pay as you go | Team | Agency | |
|---|---|---|---|---|
| Webhook subscriptions | 50 | 1,000 | 50 | 1,000 |
| API keys | 100 | |||
| External status sources | 50 | 50 | 50 | 500 |
| Webhook tests per Company, a day | 100 | |||
| Webhook redeliveries per Company, a day | 100 | |||
| Invitations sent per Company, a day | 25 | 100 | 100 | 100 |
| Wait before resending an invitation | 2 minutes | |||
Incident screenshots
| Starting credit | Pay as you go | Team | Agency | |
|---|---|---|---|---|
| Capture attempts per Company, a day (successes and failures) | 100 | 100 | 100 | 500 |
| After repeated failures | 3 failed captures in a row pause screenshots of that monitor for 6 hours | |||
In grace mode
After a balance runs out, grace mode keeps monitoring running at one check every 5 minutes for 7 days. A few actions are narrower in that time.
- Channel tests, test alerts and Check now are limited to 10 a day each.
- Attachments, manual report runs, AI features, webhook tests and redeliveries, subscriber imports and incident screenshots are switched off. Scheduled reports keep running.
- Check-ins of scheduled jobs share one pot of 288 stored check-ins per job and UTC day. A further check-in is answered as ignored, is neither stored nor billed, and still counts as a sign of life, so no false outage appears.
Status page mail and subscribers
These rules keep mail to your subscribers calm under load. Nothing is dropped silently: the status page always shows the current state, and a mail that cannot be sent within 24 hours expires.
| Interim updates per subscription and incident | one per 30 minutes, carrying the newest state |
| Notifying entries per page | 10 an hour, in a burst up to 5 |
| Mails to one subscription in 24 hours before the rest goes out as one summary | 20 |
| Confirmation mail for the same address and page | at most every 2 minutes and 3 times in 24 hours |
| Open confirmations of one address across all pages | 5 |
| New recipients per Company and hour | 100 on the starting credit, 1,000 after a first payment; above it the mail goes out in a later hour |
| Subscriber import | up to 10,000 rows and 2 MiB, one at a time per Company |
Request rates
A request over a rate limit is answered with status 429. The API adds a Retry-After header. Developers find the details under rate limits in the API docs.
| Who or what | Per minute | Burst |
|---|---|---|
| One API key or browser session | 1,200 | 300 |
| One IP address, all other requests | 3,000 | 300 |
| Check-ins of one scheduled job, per IP address | 120 | 20 |
| Sign-in and second factor, per IP address | 10 | 10 |
| Sign-up, e-mail sign-in link and password reset, per IP address | 5 | 5 |
| Status page subscribe, per IP address | 10 | 5 |
| Check now, per Company | 10 | 10 |
Fixed maximums
| Wait between two steps of an Alert plan, at least | 1 minute |
| Repeats of an Alert plan, at most | 8 |
| Monitor import (paste URLs, file or API) | up to 500 rows and 2 MB per import |
| Request timeout of a monitor | default 30 seconds, at most 1 minute |
| Shortest interval of a monitor that uses POST, PUT, PATCH or DELETE | 1 minute |
| Shortest expected interval of a scheduled job | 30 seconds |
The shortest check interval of a plan and the regions a monitor can use are shown in the monitor form; they depend on your plan. Watch a website.
Was this page helpful?