Is Verizon core network broken? Can someone reach out to Verizon core network team so that they can look into why so many networks are missing?
sumple at gmail.com
Fri Jul 23 13:53:55 UTC 2021
Verizon Executive Relations team reached out to their network team and the
finding is that Tencent is not announcing the prefixes to them.
Result: Verizon is not going to pursue this.
On Wed, Jul 21, 2021 at 12:11 PM Stephane Bortzmeyer <bortzmeyer at nic.fr>
> On Wed, Jul 21, 2021 at 11:35:35AM -0400,
> S Umple <sumple at gmail.com> wrote
> a message of 61 lines which said:
> > <VZ INET router>#
> > 126.96.36.199/8 is variably subnetted, 2835 subnets, 14 masks
> > 188.8.131.52/16 <empty>
> > 184.108.40.206/16 is variably subnetted, 3 subnets, 2 masks
> > route-views.routeviews.org>
> > 220.127.116.11/8 is variably subnetted, 3247 subnets, 19 masks
> > 18.104.22.168/8 is variably subnetted, 2571 subnets, 18 masks
> > 22.214.171.124/16 is variably subnetted, 113 subnets, 5 masks
> > Anyone able to validate my findings, and/or take this issue to higher VZ
> > support?
> Testing with the RIPE Atlas probes show that 126.96.36.199 (which is
> pingable) is not reachable at all from AS 701. But it still has
> reachability problems from other networks in the world, with many
> timeouts (but the problem at 701 is more radical).
> At least 188.8.131.52/16 and 184.108.40.206/23 seems to be seen in many
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NANOG