From: Bruce Horrocks via ntg-context <ntg-context@ntg.nl>
To: ntg-context mailing list <ntg-context@ntg.nl>
Cc: Bruce Horrocks <ntg@scorecrow.com>
Subject: Re: [NTG-context] Super slow installation
Date: Wed, 31 May 2023 10:30:41 +0100 [thread overview]
Message-ID: <DFC64535-83F5-41FD-B9C8-98DC045B871D@scorecrow.com> (raw)
In-Reply-To: <CAANrE7oajpGCzQTnG9OCDx=NYs17dh-SMNppZsDY3+WB3gsQjg@mail.gmail.com>
On 31 May 2023, at 01:51, Thangalin <thangalin@gmail.com> wrote:
>
> From twelve99.net:
>
> If you’re interested in our IP city prefixes, we have a lookup table on our website: https://www.arelion.com/our-network/bgp-routing/bgp-communities Scroll down to “Origin + Communities” and expand that section. You can see that sea-b1 (your hop 8) is not in Brussels, but is our router in Seattle.
>
> My guess would be that the hostname “us-was” for Liberty Global (aorta.net) stands for U.S.A. and Washington D.C, not Warsaw. They’re probably using ICMP tunneling for their MPLS backbone, that’s why the ping times are weird for you.
Good point about the MPLS.
I was using https://www.geolocation.com/ to do the geolocation and it claims Warsaw but that - in hindsight - is wrong. So "us-was" is likely to be Washington as per the name and is also the device "taking the blame" for the entirety of the MPLS latency. Since that will include the transatlantic time the extra 75ms isn't quite so bad as it looks.
—
Bruce Horrocks
Hampshire, UK
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-05-31 14:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 23:03 Thangalin via ntg-context
2023-05-30 9:32 ` Hans Hagen via ntg-context
2023-05-30 13:06 ` Floris van Manen via ntg-context
2023-05-30 16:07 ` Thangalin via ntg-context
2023-05-30 16:14 ` Thomas A. Schmitz via ntg-context
2023-05-30 17:28 ` Thangalin via ntg-context
2023-05-30 17:33 ` Thangalin via ntg-context
2023-05-30 17:40 ` Aditya Mahajan via ntg-context
2023-05-30 17:59 ` Thangalin via ntg-context
2023-05-30 22:43 ` Bruce Horrocks via ntg-context
2023-05-31 0:51 ` Thangalin via ntg-context
2023-05-31 3:37 ` Max Chernoff via ntg-context
2023-05-31 9:30 ` Bruce Horrocks via ntg-context [this message]
2023-05-30 19:16 ` Jim via ntg-context
2023-05-30 20:25 ` Hans Hagen via ntg-context
2023-05-30 20:50 ` Thangalin via ntg-context
2023-05-30 20:59 ` Floris van Manen via ntg-context
2023-05-30 18:05 ` Floris van Manen via ntg-context
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DFC64535-83F5-41FD-B9C8-98DC045B871D@scorecrow.com \
--to=ntg-context@ntg.nl \
--cc=ntg@scorecrow.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;
as well as URLs for NNTP newsgroup(s).