The router filter implements HTTP forwarding. It will be used in almost all HTTP proxy scenarios that Envoy is deployed for. The filter’s main job is to follow the instructions specified in the configured route table. In addition to forwarding and redirection, the filter also handles retry, statistics, etc.

  "type": "decoder",
  "name": "router",
  "config": {
    "dynamic_stats": "..."
(optional, boolean) Whether the router generates dynamic cluster statistics. Defaults to true. Can be disabled in high performance scenarios.

HTTP headers

The router responds to various HTTP headers both on the egress/request path as well as on the ingress/response path. They are documented in this section.


This is the time in milliseconds the router expects the request to be completed. Envoy sets this header so that the upstream host receiving the request can make decisions based on the request timeout, e.g., early exit. This is set on internal requests and is either taken from the x-envoy-upstream-rq-timeout-ms header or the route timeout, in that order.


If a retry policy is in place, setting this header controls the number of retries that Envoy will perform on the request’s behalf. If the header is not specified and there is no route configuration Envoy will perform a single retry. A few notes on how Envoy does retries:

  • The route timeout (set via x-envoy-upstream-rq-timeout-ms or the route configuration) includes all retries. Thus if the request timeout is set to 3s, and the first request attempt takes 2.7s, the retry (including backoff) has .3s to complete. This is by design to avoid an exponential retry/timeout explosion.
  • Envoy uses a fully jittered exponential backoff algorithm for retries with a base time of 25ms. The first retry will be delayed randomly between 0-24ms, the 2nd between 0-74ms, the 3rd between 0-174ms and so on.
  • If max retries is set both by header as well as in the route configuration, the maximum value is taken when determining the max retries to use for the request.


Setting this header on egress requests will cause Envoy to attempt to retry failed requests. The value that the header is set to indicates the retry policy. One or more policies can be specified using a ‘,’ delimited list. The supported policies are:


Envoy will attempt a retry if the upstream server responds with any 5xx response code, or does not respond at all (disconnect/reset/etc.). (Includes connect-failure and refused-stream)


Envoy will attempt a retry if a request is failed because of a connection failure to the upstream server (connect timeout, etc.). (Included in 5xx)


Envoy will attempt a retry if the upstream server responds with a retriable 4xx response code. Currently, the only response code in this category is 409.

  • NOTE: Be careful turning on this retry type. There are certain cases where a 409 can indicate that an optimistic locking revision needs to be updated. Thus, the caller should not retry and needs to read then attempt another write. If a retry happens in this type of case it will always fail with another 409.
Envoy will attempt a retry if the upstream server resets the stream with a REFUSED_STREAM error code. This reset type indicates that a request is safe to retry. (Included in 5xx)

The number of retries can be controlled via the x-envoy-max-retries header or via the route configuration.

Note that retry policies can also be applied at the route level.

By default, Envoy will not perform retries unless you’ve configured them per above.


Setting this header on egress requests will cause Envoy to emit upstream response code/timing statistics to a dual stat tree. This can be useful for application level categories that Envoy doesn’t know about. The output tree is documented here.


If an upstream host sets this header, the router will use it to generate canary specific statistics. The output tree is documented here.


Setting this header on egress requests will cause Envoy to set a 204 response code (instead of 504) in the event of a request timeout. The actual value of the header is ignored; only its presence is considered. See also x-envoy-upstream-rq-timeout-ms.


Setting this header on egress requests will cause Envoy to override the route configuration. The timeout must be specified in millisecond units. See also x-envoy-upstream-rq-per-try-timeout-ms.


Setting this header on egress requests will cause Envoy to set a per try timeout on routed requests. This timeout must be <= the global route timeout (see x-envoy-upstream-rq-timeout-ms) or it is ignored. This allows a caller to set a tight per try timeout to allow for retries while maintaining a reasonable overall timeout.


Contains the time in milliseconds spent by the upstream host processing the request. This is useful if the client wants to determine service time compared to network latency. This header is set on responses.


The router outputs many statistics in the cluster namespace (depending on the cluster specified in the chosen route). See here for more information.

The router filter outputs statistics in the http.<stat_prefix>. namespace. The stat prefix comes from the owning HTTP connection manager.

Name Type Description
no_route Counter Total requests that had no route and resulted in a 404
no_cluster Counter Total requests in which the target cluster did not exist and resulted in a 404
rq_redirect Counter Total requests that resulted in a redirect response
rq_total Counter Total routed requests

Virtual cluster statistics are output in the vhost.<virtual host name>.vcluster.<virtual cluster name>. namespace and include the following statistics:

Name Type Description
upstream_rq_<*xx> Counter Aggregate HTTP response codes (e.g., 2xx, 3xx, etc.)
upstream_rq_<*> Counter Specific HTTP response codes (e.g., 201, 302, etc.)
upstream_rq_time Timer Request time milliseconds


The router filter supports the following runtime settings:

Base exponential retry back off time. See here for more information. Defaults to 25ms.
upstream.maintenance_mode.<cluster name>
% of requests that will result in an immediate 503 response. This overrides any routing behavior for requests that would have been destined for <cluster name>. This can be used for load shedding, failure injection, etc. Defaults to disabled.
% of requests that are eligible for retry. This configuration is checked before any other retry configuration and can be used to fully disable retries across all Envoys if needed.