bug: APISIX route sometimes returns 503 for Consul-discovered service

[theytc1007]

Current Behavior

I am using APISIX to discover services registered in Consul. I have a route configured to proxy requests to these services.

When I probe the Consul service directly (e.g., via its IP or Consul HTTP API), it always responds correctly. However, when I access the service through the APISIX route domain, the requests sometimes return HTTP 503.

When I probe directly to consul service, it always work. However, when probe from route domain it sometimes return code 503. I want to know why, how to aviod this problem?

Questions:

1. Why does APISIX return 503 even when the backend service is healthy according to Consul?
2. How can I configure APISIX to avoid these intermittent 503 errors?

Any advice or best practices would be appreciated.

My apisix version is 3.13.0.

Expected Behavior

No response

Error Logs

No response

Steps to Reproduce

config.yaml:

Environment

• APISIX version 3.13.0

[theytc1007]

When I probe the service directly via Consul, for example:

curl :/v1/health/service/my_service?token=<my_token>

it never fails.

[Baoyuantop]

Duplicate of #12398