Part of the NS1 Filter Chain™, traffic management filters help you shuffle, weight, prioritize, sort, and select answers based on the metadata and options that you define.

You can use the following traffic management filters within your Filter Chain configuration:
This filter sorts or selects answers based on the lowest "cost" metadata value. Use this filter to always select the least expensive answer or use it with the Pulsar Stabilize filter to always select the least expensive option as long as it is within the best-performing option threshold you define. By default, this filter orders all answers from the lowest to the highest cost.
Note
If you enable the "Select answers instead of sorting" option, only the answer(s) with the lowest cost are returned.
This filter arranges answers based on their priority metadata value. It sorts them from the highest priority (i.e., a value of "1" is the highest priority) to the lowest priority. This filter is often used in conjunction with filters like the Up filter to implement DNS failover.
If you enable the "Select answers instead of sorting" option, then only the answer(s) with the highest priority are returned.
This filter eliminates all but the first N (number) answers in the response. Use this filter with others like the Shuffle or Weighted Shuffle filters to implement a round-robin or weighted round-robin approach to the number of responses that you return. By default, this filter will eliminate all by one answer.
This filter arranges answers uniquely based on the requester's IP address. The order of answers in the response remains the same for the same requesting client. Use this filter with the Select First N filter to return only the first N (number) of answers to the same client (as opposed to returning the entire list).
If you enable the "Apply stickiness by subnet (not by individual IP)" option, then requests in the same IPv4 or IPv6 subnet receive the same output. Enable this option to ensure users balanced across multiple recursors get the same answer.
Note
If you need to configure weighted answers with "sticky" behavior, use the Weighted Sticky Shuffle filter instead.
Note
Refer to the article about Sticky filters for more information.
This filter arranges answers uniquely based on the requester IP address, and then groups all answers together by region. Use this filter with the Select First N filter to always return the same answers from the same region to the same client.
This filter does not do any geo-targeting or global server load balancing. It sorts regions randomly but consistently for each user. Answers with no defined region are considered to be in the same (empty) region.
If you enable the "Apply stickiness by subnet (not by individual IP)" option, then requests coming from the same IPv4 or IPv6 subnet receive the same output. Enable this option to ensure that users balanced across multiple recursors get the same answer.
Note
Refer to the article about Sticky filters for more information.
This filter rearranges answers randomly based on the "weight" metadata value. Answers with a higher weight value are returned first more often. Use this filter with the Select First N filter to return one or more answers with probability proportional to their weights.
Note
If you need "sticky" behavior, use the Weighted Stucky Shuffle filter instead.
This filter combines the behavior of the Sticky Shuffle and Weighted Shuffle filters to randomly shuffle answers based on the weight metadata field consistently across the same source IP address.
Note
Any changes made to the answers or their assigned "weight" will cause this filter to reshuffle answers — even for a repeat requester.
If you select "Apply stickiness by subnet (not by individual IP), then requests in the same IPv4 or IPv6 subnet receive the same output. Select this option to ensure that users balanced across multiple recursors get the same answer.
Note
Refer to the article about Sticky filters for more information.