From: Richard Mortimer <richm@oldelvet.org.uk>
To: Dave Taht <dave.taht@gmail.com>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] bufferbloat, packet loss, and latency in real/wartime?
Date: Fri, 4 Mar 2022 19:52:33 +0000 [thread overview]
Message-ID: <8326b72a-e965-9a6e-1a3d-387c36bbe40f@oldelvet.org.uk> (raw)
In-Reply-To: <CAA93jw5SJqyEF+eGT=v1wwehqw6RyZY4yh+RrnQSCzn=j1q0aw@mail.gmail.com>
On 04/03/2022 18:59, Dave Taht wrote:
> This is not the way I wanted to get data like this, but:
>
> https://www.washingtonpost.com/technology/2022/03/04/russia-ukraine-internet-cogent-cutoff/
>
> Suggestions for any sites collecting pingtimes, tcp acks, loss, or
> latency to the ukraine and russia, desired.
>
RIPE published a report a few days ago. Using RIPE Atlas to monitor
connectivity to the various AS involved.
https://labs.ripe.net/author/emileaben/the-ukrainian-internet/
Regards
Richard
prev parent reply other threads:[~2022-03-04 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 18:59 Dave Taht
2022-03-04 19:52 ` Richard Mortimer [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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8326b72a-e965-9a6e-1a3d-387c36bbe40f@oldelvet.org.uk \
--to=richm@oldelvet.org.uk \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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