Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Ulrich Speidel <u.speidel@auckland.ac.nz>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Fwd: Here is the first edition of the report: Will LEO Satellite Direct-to-Cellular Networks Make Traditional Mobile Networks Obsolete?
Date: Wed, 29 Jan 2025 12:30:22 -0800 (PST)	[thread overview]
Message-ID: <o8n921o7-9831-1451-40p6-66o006n6q9sr@ynat.uz> (raw)
In-Reply-To: <d9b93dba-4e89-4d62-8ebd-6a46b928bee7@auckland.ac.nz>

[-- Attachment #1: Type: text/plain, Size: 562 bytes --]

Ulrich Speidel wrote:

> But let's assume you have all that in place. Now where do you go to try it 
> all out? This isn't the US. One NZ's terrestrial network covers almost 
> everywhere with people or roads. Look for yourself: 
> https://one.nz/network/coverage/

At least here in the US, you can find lots of places where the coverage maps say 
you have coverage, but your phone will drop out.

I know 8 lane freeway locations in the Los Angeles area that have spots where 
you have no coverage. look for hills and try the different sides of them.

David Lang

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
Starlink mailing list
Starlink@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/starlink

  reply	other threads:[~2025-01-29 20:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <021301db71d0$96340750$c29c15f0$@strandconsult.dk>
     [not found] ` <002f01db7248$9721d430$c5657c90$@strandconsult.dk>
2025-01-29 12:29   ` Hesham ElBakoury
2025-01-29 13:09     ` Vint Cerf
2025-01-30  3:27       ` Mike Puchol
2025-01-30  4:15         ` Ulrich Speidel
2025-01-29 14:05     ` David Lang
2025-01-29 20:24       ` Ulrich Speidel
2025-01-29 20:30         ` David Lang [this message]
2025-01-29 21:17           ` Ulrich Speidel
2025-02-04 23:30         ` Ulrich Speidel
2025-02-04  8:24       ` David Lang

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=o8n921o7-9831-1451-40p6-66o006n6q9sr@ynat.uz \
    --to=david@lang.hm \
    --cc=starlink@lists.bufferbloat.net \
    --cc=u.speidel@auckland.ac.nz \
    /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