Backend.max_conn reached

We had a short period of time yesterday where Fastly was giving 503 with a response reason of “Backend.max_conn reached”. In this case the service is already configured with the maximum allowable value of 1000.

Is there an obvious way to avoid this error arising?

Hi @PaulRudin, I’d recommend that you reach out to support for help with this query as the reason that you would be seeing this largely depends on your service’s configuration.

1 Like