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

RU-2012: Temporary server error

RealUptime could not finish the request because of a fault on our side, such as a database or internal service that did not answer in time. Nothing about the request itself was wrong, and the fault is recorded for us to look at.

Where it is raised

  • POST /api/v1/notification-channels
  • PATCH /api/v1/notification-channels/{id}
  • Keyed MCP endpoint: any tool handler that fails (a database error, an outage or delivery proxy that did not answer)
  • The GitHub App connection routes, when GitHub did not answer

What triggers it

A tool handler returned an error, or a call to GitHub failed. The text of the internal error is never sent, it is logged and recorded as an operational error instead. This is the one code in the registry that means the fault is on our side.

Example response

POST https://mcp.realuptime.io/mcp (tool call)
HTTP 503

{
  "error": "Something went wrong on our side. Try again in a few seconds.",
  "code": "RU-2012"
}

Common causes

  • A brief database or internal network interruption.
  • A deploy or restart on our side that was in progress when the request arrived.

How to fix it

  1. Retry the same request after a few seconds, backing off if it fails again.
  2. If it keeps failing for more than a few minutes, check status.realuptime.io or contact support@realuptime.io with the time of the request.

Related codes