OpenStatus · Rate Limits

Openstatus Rate Limits

OpenStatus Cloud governs usage primarily through per-plan resource limits rather than published per-second REST throttles. The dominant constraints are the number of monitors, the minimum check frequency (periodicity), the number of status pages and components, the available regions, and data retention, all of which scale by subscription tier. The on-demand /check endpoint is intended for ad-hoc use and is subject to fair-use limits. Self-hosted deployments under AGPL-3.0 are bounded only by the operator's own infrastructure.

Openstatus Rate Limits is the machine-readable rate-limit profile for OpenStatus on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 6 rate-limit definitions, measuring monitors, interval, pages, regions, and months.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Monitoring, Synthetic Monitoring, Uptime, Status Pages, and Rate Limiting.

6 Limits Throttle: 429
MonitoringSynthetic MonitoringUptimeStatus PagesRate LimitingQuotasThrottling

Limits

Monitors workspace
monitors
per-plan (1 Hobby, 20 Starter, 50 Pro/Scale)
Maximum number of active monitors, set by subscription tier.
Check Frequency monitor
interval
per-plan (10m Hobby, 1m Starter, 30s Pro/Scale)
Minimum periodicity between automated checks, set by tier.
Status Pages workspace
pages
per-plan (1 Hobby/Starter, 5 Pro, 10 Scale)
Additional pages available at +$20/mo on paid plans.
Regions monitor
regions
per-plan (6 of 28 Starter, 28 of 28 Pro/Scale)
Number of the 28 global probe regions a monitor may run from.
Data Retention workspace
months
per-plan (3 Starter, 12 Pro, 24 Scale)
Retention window for check results and history.
On-Demand Checks workspace
requests
fair use
The /check endpoint is intended for ad-hoc runs; subject to fair-use limits.

Policies

Plan-Based Limits
Quotas raise as workspaces move from Hobby to Starter, Pro, Scale, and Enterprise.
Self-Hosting
Self-hosted AGPL-3.0 deployments set their own limits, bounded by operator infrastructure.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/openstatus-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.