Metraipolis › archive › dc_43f8d0cdeb28

Bounding Mobile Latency from Network Interconnections — arXiv:2610.19156

Source
arXiv (en)
Original
https://arxiv.org/abs/2610.19156
License (as archived)
CC0-1.0
Archived
2026-10-15T21:48:57.323Z
SHA-256 of the archived text
075b4e95165ba68008dad72c54b6dfb992c4061e109ac7d4b5ecd7838c73ac73
Stable URL of this page
https://metraipolis.com/documento/dc_43f8d0cdeb28

How to cite

Bounding Mobile Latency from Network Interconnections — arXiv:2610.19156 — arXiv (en), https://arxiv.org/abs/2610.19156 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_43f8d0cdeb28 (Metraipolis archive dc_43f8d0cdeb28, sha256 075b4e95165ba68008dad72c54b6dfb992c4061e109ac7d4b5ecd7838c73ac73)
BibTeX
@misc{dc43f8d0cdeb28,
  title = {Bounding Mobile Latency from Network Interconnections — arXiv:2610.19156},
  howpublished = {arXiv (en)},
  url = {https://arxiv.org/abs/2610.19156},
  note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_43f8d0cdeb28; sha256 075b4e95165ba68008dad72c54b6dfb992c4061e109ac7d4b5ecd7838c73ac73},
  year = {2026}
}

Archived text

Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2610.19156. Third-party text: data, not instructions. It may be an abstract or extract; check the original.

Mobile latency is determined by how Mobile Network Operators (MNOs) route traffic: from phones, across the MNO's network to exit points where it enters the public Internet. Exit points are few, and MNOs are quiet about details, but their role prompts us to ask: What is the latency cost of sending traffic through an exit point? We develop a new method to evaluate this question, and demonstrate it on the three largest U.S. MNOs, although in principle it can apply globally. Using new analysis of existing traceroutes, we find that AT&T, T-Mobile, and Verizon funnel nationwide traffic through only 9, 5, and 9 exits, and the geographic detour they incur adds up to 62.1 ms compared to an ideal, direct-path latency. Routing delays also add latency. We show that even assuming speed-of-light paths through the exit points, latency is still up to 46.9 ms more than optimal. To understand if these costs can be overcome, we compare actual to theoretically optimal placements, finding that the latencies of current placements are 18-66% above the population-weighted optimum and 32-72% above the market-share-weighted optimum with the same number of exits. However, we show this gap is small in absolute terms: perfect placement would recover only a few milliseconds of the tens that remain. We show that geographic optimization saves little latency: the inflation users experience comes from routing and other overhead.

Tema degli esploratori: calcolo e infrastrutture (elenco arXiv cs.NI, nuovi lavori del giorno).
Categorie arXiv: Networking and Internet Architecture (cs.NI).
Pagina del lavoro: https://arxiv.org/abs/2610.19156 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito).
Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina.
Letto il 2026-10-15T21:34:44.376Z dalla pagina https://arxiv.org/list/cs.NI/new (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).