From: David Lang <david@lang.hm>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink no longer available to the Ukrainian army?
Date: Fri, 14 Oct 2022 05:45:33 -0700 (PDT) [thread overview]
Message-ID: <65rp9416-298q-33n8-6p20-6195sqp691oq@ynat.uz> (raw)
In-Reply-To: <8735bqpq1r.wl-jch@irif.fr>
you need to provide the rest of the information, namely that Russia is actively
jamming communications. Elon Musk said that so far it had not been very
effective against Starlink, but had knocked out viasat.
Said jamming could easily account for any outages.
David Lang
On Fri, 14 Oct 2022, Juliusz Chroboczek via Starlink wrote:
> Date: Fri, 14 Oct 2022 14:06:56 +0200
> From: Juliusz Chroboczek via Starlink <starlink@lists.bufferbloat.net>
> Reply-To: Juliusz Chroboczek <jch@irif.fr>
> To: starlink@lists.bufferbloat.net
> Subject: [Starlink] Starlink no longer available to the Ukrainian army?
>
> As some of you recall, Elon Musk recently posted a tweet in which he
> recommends that Ukraine should capitulate to Russia. Andrij Melnyk, the
> Ukrainian Ambassador to Germany, replied in two words.
>
> https://twitter.com/melnykandrij/status/1576977000178208768
>
> A few days later, Musk announced that Starlink would no longer pay its
> fraction of the cost of deploying Starlink terminals with the Ukrainian
> Army, and that the US government, if it so wishes, should foot the bill.
>
> https://twitter.com/officejjsmart/status/1580782290849759232
>
> Perhaps unrelated, there are reports of Starlink outages in Ukraine.
>
> https://www.ft.com/content/9a7b922b-2435-4ac7-acdb-0ec9a6dc8397
>
> -- Juliusz
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
next prev parent reply other threads:[~2022-10-14 12:45 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 12:06 Juliusz Chroboczek
2022-10-14 12:45 ` David Lang [this message]
2022-10-14 13:05 ` Juliusz Chroboczek
2022-10-14 13:11 ` David Lang
2022-10-14 14:17 ` Mike Puchol
2022-10-14 18:26 ` Juliusz Chroboczek
2022-10-14 20:44 ` Mike Puchol
2022-10-16 17:31 ` Steve Stroh
2022-10-16 17:56 ` Dave Taht
2022-10-16 18:28 ` Vint Cerf
2022-10-14 12:51 ` Mike Puchol
2022-10-14 13:13 ` Juliusz Chroboczek
2022-10-14 14:15 ` Mike Puchol
2022-10-14 16:05 ` Juliusz Chroboczek
2022-10-14 17:13 ` Kurtis Heimerl
2022-10-14 17:28 ` David Lang
2022-10-14 18:16 ` Juliusz Chroboczek
2022-10-14 18:32 ` Larry Press
2022-10-14 19:32 ` Benjamin Henrion
2022-10-14 19:35 ` David Lang
2022-10-14 20:07 ` David Lang
2022-10-14 22:29 ` Dave Taht
2022-10-15 16:51 ` Larry Press
2022-10-16 6:42 ` Sebastian Moeller
2022-10-16 8:45 ` Bruce Perens
2022-10-16 16:31 ` Dave Taht
2022-10-16 17:00 ` Sebastian Moeller
2022-10-16 19:55 ` Brandon Butterworth
2022-10-16 20:25 ` Bruce Perens
2022-11-02 3:50 ` [Starlink] 25 years of open source - where we went wrong, and how to fix it Dave Taht
2022-10-14 19:13 ` [Starlink] Starlink no longer available to the Ukrainian army? tom
2022-10-14 19:41 ` David Lang
2022-10-14 20:09 ` Dave Taht
2022-10-16 17:50 ` Steve Stroh
2022-10-16 17:57 ` Nathan Owens
2022-10-16 18:01 ` Dave Taht
2022-10-16 18:29 ` Vint Cerf
2022-10-16 18:33 ` David Lang
2022-10-16 18:44 ` Sebastian Moeller
2022-10-16 19:03 ` Brandon Butterworth
2022-10-16 19:37 ` Ulrich Speidel
2022-10-16 19:51 ` David Lang
2022-10-16 20:37 ` Michael Richardson
2022-10-16 20:52 ` Bruce Perens
2022-10-16 22:17 ` Brandon Butterworth
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=65rp9416-298q-33n8-6p20-6195sqp691oq@ynat.uz \
--to=david@lang.hm \
--cc=jch@irif.fr \
--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