From: Larry Press <lpress@csudh.edu>
To: "starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: [Starlink] Starlink Internet service is good on SOME cruise ships
Date: Fri, 3 May 2024 22:07:03 +0000 [thread overview]
Message-ID: <BYAPR03MB38637053D7558945606AC123C21F2@BYAPR03MB3863.namprd03.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 985 bytes --]
Starlink Internet service is good on SOME cruise ships and bad on others because there are many sources of latency between a user on a ship and the Internet. My recent experience on a Seabourn cruise was good.
https://circleid.com/posts/20240501-starlink-service-is-great-on-some-cruise-ships
[https://circleid.com/images/member_photos/photo_7705.jpg]<https://circleid.com/posts/20240501-starlink-service-is-great-on-some-cruise-ships>
Starlink Service Is Great on (Some) Cruise Ships<https://circleid.com/posts/20240501-starlink-service-is-great-on-some-cruise-ships>
I recently used Starlink on a cruise along the coast of Northwest Africa, and I'll summarize my experience below, but first let me explain why I put some in the title of this post. I posted the following request on the Reddit Cruise group: "What has been your experience of Starlink Internet service on Seabourn or other cruise lines? How was latency? Do video chats work smoothly? Games? etc."
circleid.com
[-- Attachment #2: Type: text/html, Size: 3223 bytes --]
reply other threads:[~2024-05-03 22:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BYAPR03MB38637053D7558945606AC123C21F2@BYAPR03MB3863.namprd03.prod.outlook.com \
--to=lpress@csudh.edu \
--cc=starlink@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox