A method, comprising: generating, responsive to receiving at a load balancer and from a client a request to set up a primary transmission control protocol, TCP, subflow for a multipath transmission control protocol, MPTCP, connection and an indication that the client supports MPTCP, by the load balancer a key to be used to generate a token uniquely identifying the MPTCP connection from other MPTCP connections and generating, by the load balancer, the token using the key so that a token space is divided using consistent hashing to guarantee a uniqueness of the token and also so that every one of a plurality of load balancers can compute a result of token space division so that this load balancer knows any other load balancer's token range; routing, by the load balancer, MPTCP connections and their corresponding TCP subflows toward one or more selected backends, wherein each MPTCP connection is routed to a single one of a plurality of backend and is able to comprise at least primary and secondary TCP subflows, and wherein routing the MPTCP connections comprises performing, in response to setting up the primary TCP subflow of the MPTCP connection, load balancing of the MPTCP connection to select a selected one of the plurality of backends for the MPTCP connection; and tracking, by the load balancer, the MPTCP connections and their corresponding TCP subflows to enable routing of the MPTCP connections and their corresponding TCP subflows to the corresponding selected backends, the tracking comprising inserting in memory the key, information uniquely identifying the primary TCP subflow, a corresponding identification of the specified backend for subsequent routing of the TCP subflows to the backend, and the token. generating, responsive to receiving at a load balancer and from a client a request to set up a primary transmission control protocol, TCP, subflow for a multipath transmission control protocol, MPTCP, connection and an indication that the client supports MPTCP, by the load balancer a key to be used to generate a token uniquely identifying the MPTCP connection from other MPTCP connections and generating, by the load balancer, the token using the key so that a token space is divided using consistent hashing to guarantee a uniqueness of the token and also so that every one of a plurality of load balancers can compute a result of token space division so that this load balancer knows any other load balancer's token range; routing, by the load balancer, MPTCP connections and their corresponding TCP subflows toward one or more selected backends, wherein each MPTCP connection is routed to a single one of a plurality of backend and is able to comprise at least primary and secondary TCP subflows, and wherein routing the MPTCP connections comprises performing, in response to setting up the primary TCP subflow of the MPTCP connection, load balancing of the MPTCP connection to select a selected one of the plurality of backends for the MPTCP connection; and tracking, by the load balancer, the MPTCP connections and their corresponding TCP subflows to enable routing of the MPTCP connections and their corresponding TCP subflows to the corresponding selected backends, the tracking comprising inserting in memory the key, information uniquely identifying the primary TCP subflow, a corresponding identification of the specified backend for subsequent routing of the TCP subflows to the backend, and the token.