Skip to Content
XebraDocs
Errors

upstream_unavailable

503 Upstream unavailable.

HTTP 503. type: https://docs.xebra.exchange/errors/upstream_unavailable

What it means

A chain's RPC or Circle's API could not be read just now, or Circle reports the route as down. This is never a verdict on a transfer: a status that could not be read does not mean the transfer failed.

What to do

Wait for the Retry-After header (10 seconds) and ask again. If detail says Circle is not carrying transfers on the route, do not start one until it is back.

Example

{
  "type": "https://docs.xebra.exchange/errors/upstream_unavailable",
  "title": "Upstream unavailable",
  "status": 503,
  "detail": "…",
  "code": "upstream_unavailable"
}

Every error has this shape. See Errors for how to handle them.

On this page