Send Outages-discussion mailing list submissions to
outages-discussion@outages.org
To subscribe or unsubscribe via the World Wide Web, visit
https://puck.nether.net/mailman/listinfo/outages-discussion
or, via email, send a message with subject or body 'help' to
outages-discussion-requ...@outages.org
You can reach the person managing the list at
outages-discussion-ow...@outages.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Outages-discussion digest..."
Today's Topics:
1. Re: [outages] GTT daily congestion in Europe (Lukas Tribus)
2. Re: [outages] GTT daily congestion in Europe (Brian Turnbow)
3. Re: [outages] [EXTERNAL] Ping to Google 8.8.8.8
(Chapman, Brad (NBCUniversal))
----------------------------------------------------------------------
Message: 1
Date: Fri, 4 Feb 2022 15:45:21 +0100
From: Lukas Tribus <lu...@ltri.eu>
To: CJ <cjwri...@gmail.com>
Cc: outages-discussion@outages.org
Subject: Re: [Outages-discussion] [outages] GTT daily congestion in
Europe
Message-ID:
<cacc_my8_5cyecehpnpay6mf7jdgt8h4sfvmcljmr8whsp8f...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
On Fri, 4 Feb 2022 at 15:28, CJ <cjwri...@gmail.com> wrote:
>
> The congestion might be on the reverse path.
> Can you get a trace route in the opposite direction?
Moving to -discussions.
I can exclude that because:
- I did fully analyze the issue, including clarifying the direction
with reverse MTRs
- some traffic was rerouted on the opposite direction: ZERO success
- some traffic was rerouted on the mention direction: FULL success
I did not share every single data point available to me in this post,
because that was not the point.
Thanks,
Lukas
------------------------------
Message: 2
Date: Fri, 4 Feb 2022 15:07:23 +0000
From: Brian Turnbow <b.turn...@twt.it>
To: Lukas Tribus <lu...@ltri.eu>, CJ <cjwri...@gmail.com>
Cc: "outages-discussion@outages.org" <outages-discussion@outages.org>
Subject: Re: [Outages-discussion] [outages] GTT daily congestion in
Europe
Message-ID: <ef801b5166e445c7888ef73725376...@twt.it>
Content-Type: text/plain; charset="us-ascii"
Hi,
> > The congestion might be on the reverse path.
> > Can you get a trace route in the opposite direction?
>
> Moving to -discussions.
>
> I can exclude that because:
>
> - I did fully analyze the issue, including clarifying the direction with
> reverse
> MTRs
> - some traffic was rerouted on the opposite direction: ZERO success
> - some traffic was rerouted on the mention direction: FULL success
>
> I did not share every single data point available to me in this post, because
> that
> was not the point.
I can confirm.
Example from Mil to Fra
If sent using loopback address with return via NTT all is good
RP/0/RP0/CPU0:NCS-55A2-CALDERA-1#trace 85.10.242.181 source l0
Fri Feb 4 16:01:21.446 CET
Type escape sequence to abort.
Tracing the route to 85.10.242.181
1 xe-0-2-3.cr2-mil3.ip4.gtt.net (46.33.66.5) 1 msec 1 msec 1 msec
2 ae9.cr6-fra2.ip4.gtt.net (141.136.110.41) 16 msec 16 msec 16 msec
3 ip4.gtt.net (154.14.78.154) 20 msec 19 msec 20 msec
4 core11.nbg1.hetzner.com (213.239.245.249) 22 msec 23 msec 22 msec
5 spine12.cloud1.nbg1.hetzner.com (213.239.239.142) 23 msec
spine12.cloud1.nbg1.hetzner.com (213.239.239.122) 24 msec
spine12.cloud1.nbg1.hetzner.com (213.239.239.142) 23 msec
using the interface IP that is GTT space with return via GTT we can easily see
delay.
RP/0/RP0/CPU0:NCS-55A2-CALDERA-1#trace 85.10.242.181
Fri Feb 4 16:01:36.548 CET
Type escape sequence to abort.
Tracing the route to 85.10.242.181
1 xe-0-2-3.cr2-mil3.ip4.gtt.net (46.33.66.5) 1 msec 2 msec 1 msec
2 ae9.cr6-fra2.ip4.gtt.net (141.136.110.41) 22 msec 17 msec 16 msec
3 ip4.gtt.net (154.14.78.154) 45 msec 57 msec 63 msec
4 core12.nbg1.hetzner.com (213.239.245.253) 66 msec 67 msec 69 msec
5 spine12.cloud1.nbg1.hetzner.com (213.239.239.122) 101 msec
spine12.cloud1.nbg1.hetzner.com (213.239.239.142) 71 msec
Brian
------------------------------
Message: 3
Date: Tue, 8 Feb 2022 21:25:36 +0000
From: "Chapman, Brad (NBCUniversal)" <brad.chap...@nbcuni.com>
To: Mike Bolitho <mikeboli...@gmail.com>, James Host <jh...@vultr.com>
Cc: "outages-discussion@outages.org" <outages-discussion@outages.org>
Subject: Re: [Outages-discussion] [outages] [EXTERNAL] Ping to Google
8.8.8.8
Message-ID:
<by5pr14mb341369d008ca6cd6b4f9471beb...@by5pr14mb3413.namprd14.prod.outlook.com>
Content-Type: text/plain; charset="windows-1252"
There?s always a relevant XKCD ...
https://xkcd.com/1361/
[Google Announcement]
alt text: ?the less popular 8.8.4.4 is slated for discontinuation.?
From: Outages <outages-boun...@outages.org> on behalf of Mike Bolitho via
Outages <outa...@outages.org>
Date: Tuesday, February 8, 2022 at 12:58 PM
To: James Host <jh...@vultr.com>
Cc: outa...@outages.org <outa...@outages.org>
Subject: Re: [outages] [EXTERNAL] Ping to Google 8.8.8.8
Yes, it has been this way for at least a decade. DNS are not polling servers.
- Mike Bolitho
On Tue, Feb 8, 2022, 1:29 PM James Host via Outages
<outa...@outages.org<mailto:outa...@outages.org>> wrote:
Is it that atypical for these public-facing services to drop ICMP when they get
hot? I'd not consider it an indicator of service down unless you're getting
SRVFAILs
James Host
Architect - CDN Platform
E: jh...@vultr.com<mailto:jh...@vultr.com>
On Tue, Feb 8, 2022 at 12:01 PM Christopher Conley via Outages
<outa...@outages.org<mailto:outa...@outages.org>> wrote:
This happens occasionally on 8.8.8.8 and 8.8.4.4. We used to use these IPs as
Internet reachability tests for determining failover to backup circuits and
moved away from it after the first occurrence of this happening.
--
Christopher Conley
Systems Administrator | Fors Marsh Group
1010 N. Glebe Rd, Suite 510
Arlington, VA 22201
From: Outages <outages-boun...@outages.org<mailto:outages-boun...@outages.org>>
On Behalf Of Justin Krejci via Outages
Sent: Tuesday, February 8, 2022 2:34 PM
To: outa...@outages.org<mailto:outa...@outages.org>
Subject: [EXTERNAL] [outages] Ping to Google 8.8.8.8
Seeing some hosts and not others get no reply to ICMP pings from the
Minneapolis, MN area. I checked using HE's looking glass, 1 of their 2
Minneapolis routers gets no replies. Since many use and assume 8.8.8.8 is
invincible, this has now started setting off monitoring alerts. DNS queries so
far seem unaffected.
_______________________________________________
Outages mailing list
outa...@outages.org<mailto:outa...@outages.org>
https://puck.nether.net/mailman/listinfo/outages<https://urldefense.com/v3/__https:/puck.nether.net/mailman/listinfo/outages__;!!PIZeeW5wscynRQ!_6DznWz59EUajVB5RUIgnh_dDTkmlmyqa133tEfpyWNCbSPYKQDa0WuFqu79Uz-tPQ$>
_______________________________________________
Outages mailing list
outa...@outages.org<mailto:outa...@outages.org>
https://puck.nether.net/mailman/listinfo/outages<https://urldefense.com/v3/__https:/puck.nether.net/mailman/listinfo/outages__;!!PIZeeW5wscynRQ!_6DznWz59EUajVB5RUIgnh_dDTkmlmyqa133tEfpyWNCbSPYKQDa0WuFqu79Uz-tPQ$>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/outages-discussion/attachments/20220208/aa1bef72/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 19172 bytes
Desc: image001.png
URL:
<https://puck.nether.net/pipermail/outages-discussion/attachments/20220208/aa1bef72/attachment.png>
------------------------------
Subject: Digest Footer
_______________________________________________
Outages-discussion mailing list
Outages-discussion@outages.org
https://puck.nether.net/mailman/listinfo/outages-discussion
------------------------------
End of Outages-discussion Digest, Vol 144, Issue 1
**************************************************
