A device comprising: one or more processors; memory storing a first version of a list of peer identifiers corresponding to a set of peer devices that have registered with a plurality of peer matching nodes for peer matching services associated with a content identifier (218, 222); and one or more modules stored on the memory and executable by the one or more processors to: identify a first set of changes to the first version of the list of peer identifiers, the first set of changes occurring at a particular peer matching node of the plurality of peer matching nodes, an individual change in the first set of changes including an addition of a new peer identifier to the first version of the list of peer identifiers based at least in part on a reception of a new request from a new peer device to register with the particular peer matching node for peer matching services associated with the content identifier; generate first information representative of the first set of changes to the first version of the list of peer identifiers; send, to a hub that is configured to update a second version of the list of peer identifiers based on a second set of changes that occur across at least two of the plurality of peer matching nodes for peer matching services associated with the content identifier (218, 222), the first information representative of the first set of changes to the first version of the list of peer identifiers; receive, from the hub, second information representative of the second set of changes to the second version of the list of peer identifiers; update the first version of the list of peer identifiers based at least in part on the second information received from the hub; and provide the first version of the list of peer identifiers to at least one peer device that has registered with the particular peer matching node. one or more processors; memory storing a first version of a list of peer identifiers corresponding to a set of peer devices that have registered with a plurality of peer matching nodes for peer matching services associated with a content identifier (218, 222); and one or more modules stored on the memory and executable by the one or more processors to: identify a first set of changes to the first version of the list of peer identifiers, the first set of changes occurring at a particular peer matching node of the plurality of peer matching nodes, an individual change in the first set of changes including an addition of a new peer identifier to the first version of the list of peer identifiers based at least in part on a reception of a new request from a new peer device to register with the particular peer matching node for peer matching services associated with the content identifier; generate first information representative of the first set of changes to the first version of the list of peer identifiers; send, to a hub that is configured to update a second version of the list of peer identifiers based on a second set of changes that occur across at least two of the plurality of peer matching nodes for peer matching services associated with the content identifier (218, 222), the first information representative of the first set of changes to the first version of the list of peer identifiers; receive, from the hub, second information representative of the second set of changes to the second version of the list of peer identifiers; update the first version of the list of peer identifiers based at least in part on the second information received from the hub; and provide the first version of the list of peer identifiers to at least one peer device that has registered with the particular peer matching node. identify a first set of changes to the first version of the list of peer identifiers, the first set of changes occurring at a particular peer matching node of the plurality of peer matching nodes, an individual change in the first set of changes including an addition of a new peer identifier to the first version of the list of peer identifiers based at least in part on a reception of a new request from a new peer device to register with the particular peer matching node for peer matching services associated with the content identifier; generate first information representative of the first set of changes to the first version of the list of peer identifiers; send, to a hub that is configured to update a second version of the list of peer identifiers based on a second set of changes that occur across at least two of the plurality of peer matching nodes for peer matching services associated with the content identifier (218, 222), the first information representative of the first set of changes to the first version of the list of peer identifiers; receive, from the hub, second information representative of the second set of changes to the second version of the list of peer identifiers; update the first version of the list of peer identifiers based at least in part on the second information received from the hub; and provide the first version of the list of peer identifiers to at least one peer device that has registered with the particular peer matching node.