Skip to main content

service_degraded

The service is operating in a degraded mode and temporarily rejected the request.

HTTPcodeRetryable?
503service_degradedyes

When it happens​

Two situations return this code:

  • Load-shedding or a degraded dependency. Skipo is shedding load to protect itself, or a component it depends on is degraded — for example the replay-protection store that records the nonce of every signed operation, so POST /v2/orders and POST /v2/withdrawals can return it too.
  • Trading paused. A Skipo operator temporarily paused quoting and trading, or the liquidity provider cannot price this request right now. This affects POST /v2/quotes, GET /v2/markets/{market}/price and POST /v2/orders; read endpoints keep working.

How to resolve it​

Wait the number of seconds in the Retry-After header, if present, before retrying; if the error persists, back off exponentially. For POST /v2/orders, request a new quote (POST /v2/quotes) first: the previous one will have expired. On signed operations, re-sign every retry with a new nonce.

Example​

{
"type": "https://docs.skipo.com/errors/service_degraded",
"title": "Service degraded",
"status": 503,
"code": "service_degraded",
"retryable": true,
"detail": "Pricing or trading is temporarily unavailable for this request. Retry after the number of seconds in the Retry-After header."
}

Back to the error catalog · See the error format.