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

RU-2009: Server allowance exhausted

Every server the account's Monitor plan covers already has an agent registered, so a new agent was not registered and no token was issued.

On the wire

Ships with HTTP status 403, carrying "code": "RU-2009" in the response body alongside the human-readable error message. Existing fields are never replaced by the code: it is additive.

Common causes

  • Agents registered for servers that were later retired and never revoked.
  • Automation registering a new agent on every deploy instead of reusing its token.

How to fix it

  1. Revoke an agent you no longer use from Monitoring settings, then retry.
  2. Or contact support to raise the limit on extra servers.

Related codes

  • RU-2004: Plan monitor limit reached

Still stuck?

Ask support and mention RU-2009: the code pins down the exact refusal path, so you skip the diagnostic back-and-forth.