Skip to content
Error codes · Rate limits, quotas & billing

RU-2004: Plan monitor limit reached

Creating this monitor would exceed the number of monitors your plan includes, so nothing was created.

Where it is raised

  • POST /api/v1/checks
  • PATCH /api/v1/checks/{id}
  • POST /api/v1/heartbeats
  • Keyed MCP endpoint, create tools

What triggers it

The create routes count the account's monitors against the plan allowance as the last step, after the body, interval, regions and target all passed. The message names the plan and the limit. Nothing is created and nothing is charged.

Example response

POST /api/v1/checks
HTTP 403

{
  "error": "Your <plan> plan allows up to <limit> monitors. Upgrade to add more.",
  "code": "RU-2004"
}

Common causes

  • The account is at its plan's monitor allowance.
  • Automation recreating monitors instead of reusing existing ones.

How to fix it

  1. Delete monitors you no longer need, or upgrade your plan for a larger allowance.
  2. Check for duplicate monitors created by automation before adding capacity.