Backend
A First Look at Starlink Maritime on Cruise Ships
arXiv cs.NI0 views
arXiv:2611.07191v1 Announce Type: new Abstract: Low-Earth-Orbit (LEO) satellite networks are reshaping maritime connectivity, offering much lower latency and higher capacity than traditional geostationary (GEO) links. As a single user terminal (UT) cannot serve hundreds to thousands of passengers, a cruise ship often deploys several UTs behind an onboard multi-WAN router for aggregated capacity and load balancing. Consequently, passenger connectivity depends not only on the satellite links but also on how the router distributes sessions among UTs. In this paper, we measure Starlink maritime connectivity on two cruise ships of different scales, Utopia of the Seas near the Bahamas in December 2025 and Silver Muse in the Adriatic Sea in July 2026, combining UT telemetry, inside-out measurements from a passenger device, and outside-in measurements from cloud servers near Starlink Points of Presence (PoPs). We find that the onboard network, rather than the satellite links, largely determines the passenger experience, as cruise lines rate limit each passenger device. Moreover, the public IP address of a passenger device changes not only at PoP handovers but also within the same PoP. Furthermore, while the country code reported by the UT reflects the maritime jurisdiction of the ship, the serving PoP follows neither this jurisdiction nor geographic proximity alone, suggesting factors beyond the distance-based PoP boundaries observed in Starlink aviation. To the best of our knowledge, this is the first systematic study of Starlink on commercial cruise ships, complementing prior land mobile and in-flight measurements.
Source:https://arxiv.org/abs/2611.07191PreviousReDrone5G: Field Trial Evaluation of Remote UAV Media and Control over Public and Private 5G NetworksNextIRIS: Intelligent Random Access with Integrated Shared Learning for Decentralized LEO Direct-to-Satellite Uplinks
Related posts
Alpie Seed: A 9B Coding Model That Runs Offline on Your Laptop
0dev.to AI
Ollama vs vLLM: Death Battle 🥊 - 2026
0dev.to AWS
We replaced our deploy keys with OIDC and every repository in the organisation could deploy our website
0dev.to AWS
Debugging agentcore browser deploys from Windows
0dev.to AWS
AWS Kiro Bots Are Always-On Coding Agents With a Memory — Here's What's Actually New
0dev.to AWS
Our despatch job stopped at the first empty answer from SQS and left parcels for the next day
0dev.to AWS