bgpreport

Network · data from 2026-11-12

AS3375 MCI-ASN - Verizon Business

Registry name: MCI-ASN - Verizon Business, US · not in PeeringDB

8IPv4 routes 0.0% RPKI valid · 0.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
8No ROA 8 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS3375, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS3375, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
165.122.32.0/20 No ROA None 672 100% 67
165.122.192.0/18 No ROA None 672 100% 67
166.37.194.0/23 No ROA None 672 100% 67
166.37.200.0/21 No ROA None 672 100% 67
166.37.208.0/20 No ROA None 672 100% 67
166.37.218.0/23 No ROA None 672 100% 67
166.37.232.0/21 No ROA None 672 100% 67
166.37.240.0/20 No ROA None 672 100% 67

AS-SET

AS3375 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 16 are in fix.csv.

  • ROA: none8
  • Route object: none8
ChangePrefix or setDetailFull-table peers
ROA: none165.122.32.0/20No ROA covers it. Add a ROA for AS3375, maxLength 20.672 of 673
Route object: none165.122.32.0/20No route object for it. Add a route object with origin AS3375 in the RIR database for the space.672 of 673
ROA: none165.122.192.0/18No ROA covers it. Add a ROA for AS3375, maxLength 18.672 of 673
Route object: none165.122.192.0/18No route object for it. Add a route object with origin AS3375 in the RIR database for the space.672 of 673
ROA: none166.37.194.0/23No ROA covers it. Add a ROA for AS3375, maxLength 23.672 of 673
Route object: none166.37.194.0/23No route object for it. Add a route object with origin AS3375 in the RIR database for the space.672 of 673
ROA: none166.37.200.0/21No ROA covers it. Add a ROA for AS3375, maxLength 21.672 of 673
Route object: none166.37.200.0/21No route object for it. Add a route object with origin AS3375 in the RIR database for the space.672 of 673
ROA: none166.37.208.0/20No ROA covers it. Add a ROA for AS3375, maxLength 20.672 of 673
Route object: none166.37.208.0/20No route object for it. Add a route object with origin AS3375 in the RIR database for the space.672 of 673
ROA: none166.37.218.0/23No ROA covers it. Add a ROA for AS3375, maxLength 23.672 of 673
Route object: none166.37.218.0/23No route object for it. Add a route object with origin AS3375 in the RIR database for the space.672 of 673
ROA: none166.37.232.0/21No ROA covers it. Add a ROA for AS3375, maxLength 21.672 of 673
Route object: none166.37.232.0/21No route object for it. Add a route object with origin AS3375 in the RIR database for the space.672 of 673
ROA: none166.37.240.0/20No ROA covers it. Add a ROA for AS3375, maxLength 20.672 of 673
Route object: none166.37.240.0/20No route object for it. Add a route object with origin AS3375 in the RIR database for the space.672 of 673

Route objects not announced

Every route object with origin AS3375 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.