A distributed load balancer system, comprising: a plurality of load balancer nodes (110A-110n), wherein at least two of the plurality of load balancer nodes are configured as ingress servers, and wherein at least two of the plurality of load balancer nodes are configured as flow tracker nodes; a plurality of server nodes (130A-130m); and a router configured to distribute packet flows from one or more clients to the ingress servers according to a hashed multipath routing technique; wherein each ingress server is configured to: receive a packet in a packet flow from a client via the router; determine that the ingress server does not have a mapping for the packet flow to any of the plurality of server nodes; determine at least one flow tracker node for the packet flow according to a consistent hash function applied to source and destination address information of the packet; obtain a mapping of a connection to a particular one of the plurality of server nodes for the packet flow from the at least one flow tracker node, based on determining that the ingress server does not have the mapping for the packet flow to any of the plurality of server nodes; and send one or more packets of the packet flow to the particular server node based on the obtained mapping. a plurality of load balancer nodes (110A-110n), wherein at least two of the plurality of load balancer nodes are configured as ingress servers, and wherein at least two of the plurality of load balancer nodes are configured as flow tracker nodes; a plurality of server nodes (130A-130m); and a router configured to distribute packet flows from one or more clients to the ingress servers according to a hashed multipath routing technique; wherein each ingress server is configured to: receive a packet in a packet flow from a client via the router; determine that the ingress server does not have a mapping for the packet flow to any of the plurality of server nodes; determine at least one flow tracker node for the packet flow according to a consistent hash function applied to source and destination address information of the packet; obtain a mapping of a connection to a particular one of the plurality of server nodes for the packet flow from the at least one flow tracker node, based on determining that the ingress server does not have the mapping for the packet flow to any of the plurality of server nodes; and send one or more packets of the packet flow to the particular server node based on the obtained mapping. receive a packet in a packet flow from a client via the router; determine that the ingress server does not have a mapping for the packet flow to any of the plurality of server nodes; determine at least one flow tracker node for the packet flow according to a consistent hash function applied to source and destination address information of the packet; obtain a mapping of a connection to a particular one of the plurality of server nodes for the packet flow from the at least one flow tracker node, based on determining that the ingress server does not have the mapping for the packet flow to any of the plurality of server nodes; and send one or more packets of the packet flow to the particular server node based on the obtained mapping.