Yes, definitely Comcast-wide. And I should have realized that was almost
certainly true earlier. I did look at the Comcast looking glass listed at
PeeringDB and even saw the problem, but didn't put 2-and-2 together at the
time. All I saw was that the path for the IPv4 prefix for m-root,
202.12.27.0
Same here in East Central Illinois. v4 fails; v6 works.
Trace stops in Chicago.
On 8/26/24 03:54, Thomas Wodarek wrote:
I'm getting similar results on residential Comcast up here in Michigan,
US (Comcast's Heartland region). Checking from a Google Cloud vm in
Iowa, US, I was able to reach m.
I'm getting similar results on residential Comcast up here in Michigan, US
(Comcast's Heartland region). Checking from a Google Cloud vm in Iowa, US,
I was able to reach m.root-servers.net via both v4 and v6, but it looks
like it's routing to the Sao Paulo cluster in both cases (looking at
https:/
3 matches
Mail list logo
