From: Sebastian Moeller <moeller0@gmx.de>
To: Y via Bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] random window into other people's latency experience
Date: Wed, 10 Jun 2020 12:01:23 +0200 [thread overview]
Message-ID: <57759588-464F-446A-86C7-7085060BF17F@gmx.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1914 bytes --]
Dear All,
I use free thinkbroadband's, latency/availability monitoring (broadban quality monitoring BQM, free after a free registration*)service, which runs ICMP probes from a dedicated box in London IIRC against all registered IPv4-addresses/domain names. Yesterday, my dsl-modem and the DSLAM decided they do not like each other and the modem was in idle_request status for several hours from afternoon to evening. Interstingly the latency probe was continuing, but now not against may router, but against the german Telefonica/O2 customer who got my old dynamic IP address assigned:
<a title="Broadband Ping" href="https://www.thinkbroadband.com/broadband/monitoring/quality/share/889b0c5ebab7cd432400d55e6c414b6f6658e278-09-06-2020"><img alt="My Broadband Ping - sesaokjole" src="https://www.thinkbroadband.com/broadband/monitoring/quality/share/889b0c5ebab7cd432400d55e6c414b6f6658e278-09-06-2020.png" /></a>
As a belts AND suspenders measure I also try to attach an image, but am not sure whether the list will like that...
From 12:30 to ~21:00 on the plot my modem was out of sync and hence these probes must have been reflected from somebody else's router in Germany in the same ISP's network as my link. As the green, blue and yellow lines indicate that access link suffers much worse from variable latency (and from 19:30 - 21:00 also from some packet loss). I believe I have forgotten how bad internet access can be without competent AQM to make performance under load acceptable.
So here is to all who worked hard to diagnose, understand and to remedy bufferbloat.
Best Regards
Sebastian
*) This is similat to dslreports smokeping service, except it is closer for european users and it allows domain names instead of fixed IP-addresses and will by default run wiyhout a time limit, the reporting is not half as nice as with dslreports, but for free it is quite marvelous.
[-- Attachment #2.1: Type: text/html, Size: 3051 bytes --]
[-- Attachment #2.2: 889b0c5ebab7cd432400d55e6c414b6f6658e278-09-06-2020.png --]
[-- Type: image/png, Size: 239410 bytes --]
next reply other threads:[~2020-06-10 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 10:01 Sebastian Moeller [this message]
2020-06-10 20:41 ` Jonathan Foulkes
2020-06-11 22:57 ` Chris Wedgwood
2020-06-13 20:05 ` Sebastian Moeller
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=57759588-464F-446A-86C7-7085060BF17F@gmx.de \
--to=moeller0@gmx.de \
--cc=bloat@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