Where it is raised
POST /api/v1/notification-channelsPATCH /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
- Retry the same request after a few seconds, backing off if it fails again.
- 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.