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

RU-2001: Too many failed authentication attempts

Your address sent too many requests that failed authentication in a short window, so realuptime stopped checking keys from it for a minute. Successful, authenticated traffic is never counted here.

Where it is raised

  • Checks: 14 routes
  • Metrics: 1 route
  • Status Pages: 11 routes
  • Notification Channels: 6 routes
  • Incidents: 4 routes
  • Maintenance: 3 routes
  • Errors: 8 routes
  • Agents: 6 routes
  • Keyed MCP endpoint, which also sends Retry-After: 60

What triggers it

Each refused authentication (RU-1001, RU-1002, RU-1007) adds one to a counter for the caller's address. At 30 failures in a minute the address is refused here before its key is even looked at, and the window rolls over after a minute. Requests that authenticate are never added.

Example response

GET /api/v1/checks
HTTP 429
Retry-After: 60

{
  "error": "Too many failed authentication attempts. Wait a minute and try again.",
  "code": "RU-2001",
  "docs": "https://realuptime.io/kb/errors/ru-2001"
}

Common causes

  • A client retrying in a tight loop with a bad or missing key.
  • A misconfigured deployment where many instances share one broken credential.

How to fix it

  1. Stop the retry loop first: retrying does not clear the limit.
  2. Fix the credential (see RU-1001 and RU-1002), wait a minute, then resume.

Related codes