# Where Does My Call Go? Measuring Google Meet, Zoom, and Microsoft Teams on Starlink

DevFeed: [Where Does My Call Go? Measuring Google Meet, Zoom, and Microsoft Teams on Starlink](<https://devfeed.tech/articles/where-does-my-call-go-measuring-google-meet-zoom-and-microsoft-teams-on-starlink-104195.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.35874>)

Author: Kousar Malekinasab, Mostafa Abdollah, Jinwei Zhao, Jianping Pan

Published: 2026-10-28T04:00:00Z

Content type: news

Language: en

Sources: [arXiv: Networking](<https://devfeed.tech/sources/arxiv-networking.md>)

Topics: [Network architectures](<https://devfeed.tech/topics/network-architectures.md>), [Internet Traffic](<https://devfeed.tech/topics/internet-traffic.md>), [Google Meet](<https://devfeed.tech/topics/google-meet.md>), [Microsoft Teams](<https://devfeed.tech/topics/microsoft-teams.md>), [zoom](<https://devfeed.tech/topics/zoom.md>)

Tags: [cs-ni](<https://devfeed.tech/tags/cs-ni.md>), [google](<https://devfeed.tech/tags/google.md>), [leo](<https://devfeed.tech/tags/leo.md>), [low-earth-orbit](<https://devfeed.tech/tags/low-earth-orbit.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [microsoft-teams](<https://devfeed.tech/tags/microsoft-teams.md>), [performance](<https://devfeed.tech/tags/performance.md>), [starlink](<https://devfeed.tech/tags/starlink.md>), [zoom](<https://devfeed.tech/tags/zoom.md>)

## AI overview

Measurements from a Canada-wide testbed and over 24 hours of in-flight experiments found that Google Meet tends to select service points closer to Starlink's serving PoP, Zoom uses a regional selection pattern, and Microsoft Teams often stays tied to fixed service points. During in-flight PoP handovers, traffic egress can shift mid-session; platforms respond differently, sometimes choosing suboptimal service points and increasing round-trip time. The abstract suggests these results reflect a mismatch between Starlink's changing egress and RTC selection mechanisms shaped by terrestrial networks, and motivate further measurement and LEO-optimized placement and selection.

## Source excerpt

arXiv:2610.35874v1 Announce Type: new Abstract: Low-Earth-Orbit (LEO) satellite networks are expanding broadband access, but major Real-Time Communication (RTC) platforms, including Google Meet, Zoom, and Microsoft Teams, still rely on service-point selection mechanisms that appear to be largely shaped by terrestrial-network assumptions. As a result, they may not consistently account for LEO-specific dynamics such as satellite topology and Point-of-Presence (PoP) changes, especially during in-flight connectivity. To characterize RTC service-point selection over Starlink, we measure RTC performance using a Canada-wide testbed and more than 24 hours of in-flight experiments. Our results show clear platform differences. Google Meet tends to align more closely with the serving PoP, consistent with broader observed edge coverage. Zoom follows a regional service-point selection pattern, while Microsoft Teams often remains tied to fixed service points. Moreover, we show that in-flight PoP handovers can shift traffic egress points mid-session, and that RTC platforms respond differently to these changes. In some cases, this interaction leads to suboptimal service-point selections and RTT inflation. Overall, our findings suggest that LEO connectivity can expose mismatches between Starlink egress dynamics and RTC service-point selection, motivating further measurement and LEO-optimized designs for service placement and selection.