Verizon no BGP route to some of AS38365 (182.61.200.0/24)

Thu Jul 21 16:39:55 UTC 2022

Well that shows my assertion was probably wrong.

Given the geopolitical situation between the US and China, along with
certain government orders, could likely infer this is intentional.

On Thu, Jul 21, 2022 at 12:33 PM Paul Rolland <rol at witbe.net> wrote:

> Hello,
>
> On Thu, 21 Jul 2022 12:20:37 -0400 (EDT)
> Jon Lewis <jlewis at lewis.org> wrote:
>
> > I looked at this a little last night, but didn't have time to write an
> > email about it.  Verizon has a lookingglass:
> >
> > https://www.verizon.com/business/why-verizon/looking-glass/
> >
> > which you can use to see that Verizon has no route covering
> 182.61.200.0.
> > Looking at routeviews, I see routes for 182.61.200.0/22,
> > and 182.61.200.0/21, but no path via Verizon.
>
> Just tested using:
>   Region: Asia Pacific
>   Location: HKG
>   Show BGP route
>   Net: 182.61.200.0
>
> and the answer is:
>
> 182.61.200.0/22 (2 entries, 1 announced)
>         *BGP    Preference: 170/-101
>                 Age: 4w0d 22:32:07      Metric: 10      Metric2: 500502
>                 Announcement bits (4): 0-KRT 3-RT 8-BGP_RT_Background
> 9-Resolve tree 4
>                 AS path: (65336) 4134 23724 38365 I  (Atomic Originator)
>                 Communities:
>                 Localpref: 100
>
> Paul
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20220721/b3a3c2a3/attachment.html>