DevOps Kong

Kong: Failure to get a peer from the ring-balancer

Ever seen this error when calling a kong endpoing or making an http request served by kong:

HTTP/1.1 503 Service Temporarily Unavailable
Connection: keep-alive
Content-Length: 59
Content-Type: application/json; charset=utf-8
Date: Wed, 28 Aug 2019 08:08:01 GMT
Server: kong/0.14.1

    "message": "failure to get a peer from the ring-balancer"

What does it mean?

It means that kong – the api gateway (reverse proxy) – could not access any of the upstreams (upstream apis) or all of the upstream targets are unhealthy.

Kong could not connect to any of the backend services in the upstream pool.

Remember to ensure that at least one upstream is healthy. Unhealthy upstreams are ignored.