Bad Routing

payup

AT&T taking the long route to QUAD9 in Kansas City instead of to the Dallas PoP where 9 announces with Arelion.

tracing route to dns9.quad9.net [9.9.9.9]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms dsldevice.attlocal.net [192.168.1.254]
2 4 ms 3 ms 3 ms 107-xx-xx-1.lightspeed.rcsntx.sbcglobal.net [107.xx.xx.x]
3 4 ms 3 ms 3 ms 71.xx-xx-xx
4 * * * Request timed out.
5 * 3 ms * 32.130.24.47
6 * * * Request timed out.
7 38 ms 35 ms 36 ms dls-bb2-link.ip.twelve99.net [62.115.138.64]
8 * * * Request timed out.
9 26 ms 28 ms 27 ms kanc-b2-link.ip.twelve99.net [62.115.138.75]
10 27 ms 27 ms 27 ms kanren-ic-370571.ip.twelve99-cust.net [62.115.154.143]
11 27 ms 27 ms 27 ms quad9.peer.net.kanren.net [164.113.205.226]
12 28 ms 27 ms 27 ms dns9.quad9.net [9.9.9.9]

Trace complete.

MarkRH

I get 12 hops as well if I force a IPv4 tracert:

tracert -4 -w 200 dns9.quad9.net
Tracing route to dns9.quad9.net [9.9.9.9]
over a maximum of 30 hops:

  1     *        3 ms    <1 ms  dsldevice.attlocal.net [192.168.1.254]
  2    18 ms    17 ms    17 ms  99-172-162-1.lightspeed.rcsntx.sbcglobal.net [99.172.162.1]
  3    63 ms    19 ms    18 ms  71.147.108.17
  4     *        *        *     Request timed out.
  5    71 ms     *        *     32.130.24.49
  6     *        *       71 ms  192.205.37.10
  7    71 ms    25 ms    25 ms  dls-bb2-link.ip.twelve99.net [62.115.138.64]
  8     *        *        *     Request timed out.
  9    98 ms    42 ms    41 ms  kanc-b2-link.ip.twelve99.net [62.115.138.75]
 10    88 ms    46 ms    42 ms  kanren-ic-370571.ip.twelve99-cust.net [62.115.154.143]
 11     *       55 ms    41 ms  quad9.peer.net.kanren.net [164.113.205.226]
 12    41 ms    41 ms    41 ms  dns9.quad9.net [9.9.9.9]

Trace complete.

An IPv6 tracert has 4 hops:

tracert -w 200 dns9.quad9.net

Tracing route to dns9.quad9.net [2620:fe::fe:9]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2    18 ms    23 ms    18 ms  2001:506:6000:13c:71:156:210:25
  3    19 ms    18 ms    18 ms  2001:506:6000:13c:71:156:210:14
  4    43 ms    44 ms    44 ms  dns9.quad9.net [2620:fe::fe:9]

Trace complete.

So, seems to just be affecting the IPv4 route at the moment.

nucleartx

It’s popped up again… Reddit media too

payup

Fastly de-peered with AT&T? Now seeing increased latency to anything hitting a Fastly endpoint. One of the oldest telecoms can’t manage a network. Reddit media refusing to load, twitch Thumbnails not appearing etc.

skinnyJM

I have also been experiencing intermittent sluggish media content loading as was also happening a couple months ago.

nucleartx

Driving me nuts today. Using unbound w/pihole. Not seeing any latency issues from tracert but the media is using Fastly.net CDN

nucleartx

Still having the issue, twelve99 to fastly. Going all the way up to Seattle.

skinnyJM

I have lately been having problems with this site loading. Is it also because of this same recurring issue?

SLC_96

skinnyJM I have lately been having problems with this site loading. Is it also because of this same recurring issue?

Yes, the peering between this site an AT&T gets severely congested from time to time.

skinnyJM

Here’s what I get on a regular basis.

nucleartx

Issue now seems to be appearing with www.redditstatic.com
Same twelve99.net poor peering

JRB-Ware

Anyone try a different DNS provider other than Fraud 9? I’ve found that provider to be mostly hype.

nucleartx

JRB-Ware I use PiHole with UnBound but have not tried different DNS on my network.

payup

JRB-Ware I did a ipconfig /flushdns and it seems to have fixed every issue. Images now loading as expected etc.

payup

I’ve actually had no issues recently! latency to 9.9.9.9 is back to 8-9ms and reddit content is loading quickly. Spectrum regularly had multi-day outages, never again. AT&T is vastly superior even with the routing issues.