Limits
This page lists the limits you can run into in EvoHub. Each product page explains its own in context; the link in each row goes there.
Rate limits
| What | Limit |
|---|---|
| API requests | Counted per API key (or, without a key, per IP address) over a 10-second window: about 100 requests per second. Over it, the answer is 429 RATE_LIMITED with Retry-After: 10. See Rate limits. |
| Alert ingest and heartbeat pings | Not rate limited, so a burst of alerts during an outage is never dropped for being too many. |
| Failed sign-ins | After 5 wrong passwords, the account is locked for 15 minutes. See Sign in. |
| Changelog GitHub release imports | 10 imports an hour per changelog. See Import GitHub releases. |
Sizes
| What | Limit |
|---|---|
| Alert ingest body | 1 MiB; larger is refused with 413. See How ingest works. |
| Uptime check response | The first 1 MB of the body is read. See HTTP and keyword options. |
| Status page, docs site and changelog logos | PNG, JPEG or WebP up to 2 MB. |
| Docs site files | Images up to 5 MB (SVG and ICO 1 MB), PDFs up to 20 MB; 500 MB and 2,000 files per site. See Files and images. |
| Docs import | A .zip of up to 50 MB. See Import and export. |
| Changelog images | PNG, JPEG, WebP, GIF or SVG up to 5 MB each. See Writing entries. |
| Voice template | 200 characters. See Customize what the call says. |
| Support ticket subject | 200 characters. |
Per-product limits
| Product | Limit |
|---|---|
| Organizations | One account can own up to 5 organizations. See Organizations and teams. |
| On-Call | An escalation step tries a target up to 10 times; a policy repeats up to 5 times. Up to 20 rules in your notification schedule. A maintenance window lasts at most 30 days. See Escalation policies and Notifications. |
| Uptime | Checks every 15 seconds at the most often, with a timeout of up to 60 seconds; up to 10 assertions per monitor. See Uptime overview. |
| Status Pages | One custom domain per page; up to 5 header links; A page per group allows up to 3 groups. See Status Pages. |
| Docs | Up to 20 versions and 10 extra languages per site, 200 snippets per version. See Docs overview. |
| Changelog | Up to 30 categories per changelog, 5 categories and 10 tags per entry, 10 notification destinations, 5 header links, 20 allowed sites for the iframe. The widget shows the 10 newest entries. See Writing entries and Reaching readers. |
| EvoTrail | A custom date range covers up to 366 days; an audit export carries up to 100,000 events. See EvoTrail overview. |
How long data is kept
| Data | Kept for |
|---|---|
| Resolved alerts, with their notification and timeline records | 1 year, then deleted automatically |
| Incidents, postmortems and on-call configuration | As long as the account exists |
| Uptime check results | 90 days (daily figures: 400 days) |
| Board cards | Until you archive or delete them; archived cards are deleted 2 years after archiving |
| Audit trail: changes | 365 days |
| Audit trail: day-to-day activity, such as moving a card | 90 days |
| IP addresses and browser details on audit events | 90 days |
| Docs, changelog and status page visit figures | Each site's own setting: 30, 90 or 180 days, 1 year or 2 years |
| Docs page feedback | 2 years |
| Account data | While your account exists, and 30 days after you delete it |
| Billing and usage records that make up invoices | As long as tax and accounting law requires |
Privacy and your data and EvoTrail have the full lists, and the Privacy Notice takes precedence over both.

