Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Inemesit Affia <inemesitaffia@gmail.com>
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] Hairpin to 6939 Hurricane Electric for some Aviation users
Date: Fri, 14 Aug 2026 09:22:05 +0100	[thread overview]
Message-ID: <d58e9938-6090-4dcb-868a-8de1c153ac70@gmail.com> (raw)
In-Reply-To: <fee5095f-6ede-473e-8546-1c407b695c15@gmail.com>

174.244.236.0/22

I saw a speed test to an IP in this block from a user on United today

All routes from 6939, even from California to this prefix seem to go through *8529* with the associated latency of going all the way to Oman

      reply	other threads:[~2026-08-14  8:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-13  6:59 [Starlink] Re: Multiday connectivity issues in Kenya Ben Eastvold
2026-07-13  7:52 ` Inemesit Affia
2026-07-13 15:16   ` Jianping Pan
2026-07-14 11:52     ` Ben Eastvold
2026-07-14 14:48       ` Jianping Pan
2026-07-23 10:18         ` [Starlink] Re: Multiday connectivity issues in Kenya. Also, the bonded gateway Inemesit Affia
2026-08-14  8:22           ` Inemesit Affia [this message]

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=d58e9938-6090-4dcb-868a-8de1c153ac70@gmail.com \
    --to=inemesitaffia@gmail.com \
    --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