bgpreport

Network · data from 2026-11-12

AS12052 VFC - VF Services, Inc. Information Technology Services

Registry name: VFC - VF Services, Inc. Information Technology Services, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS12052, 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.

167.64.57.0/24 No ROA Nonecovered by 167.64.56.0/23 671 100% 67
167.64.24.0/24 No ROA Other IRR onlyRADB 671 100% 67
167.64.31.0/24 No ROA Other IRR onlyRADB 671 100% 67
167.64.32.0/24 No ROA Other IRR onlyRADB 671 100% 67
167.64.34.0/24 No ROA Other IRR onlyRADB 671 100% 67
167.64.43.0/24 No ROA Other IRR onlyRADB 671 100% 67
167.64.44.0/23 No ROA Other IRR onlyRADB 671 100% 67
167.64.46.0/24 No ROA Other IRR onlyRADB 671 100% 67
167.64.49.0/24 No ROA Other IRR onlyRADB 671 100% 67
167.64.72.0/22 No ROA Other IRR onlyRADB, RIPE-NONAUTH 671 100% 67
167.64.76.0/22 No ROA Other IRR onlyRADB 671 100% 67
167.64.85.0/24 No ROA Other IRR onlyRADB 671 100% 67
167.64.92.0/22 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
167.64.96.0/22 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
167.64.122.0/24 No ROA Other IRR onlyRADB 671 100% 67
167.64.153.0/24 No ROA Other IRR onlyRADB 671 100% 67
167.64.225.0/24 No ROA Other IRR onlyRADB 671 100% 67
167.64.227.0/24 No ROA Other IRR onlyRADB 671 100% 67
167.64.239.0/24 No ROA Other IRR onlyRADB 671 100% 67
167.64.243.0/24 No ROA Other IRR onlyRADB 671 100% 67
167.64.244.0/23 No ROA Other IRR onlyRADB 671 100% 67
167.64.247.0/24 No ROA Other IRR onlyRADB 671 100% 67
167.64.248.0/24 No ROA Other IRR onlyRADB 671 100% 67
167.64.249.0/24 No ROA Other IRR onlyRADB 671 100% 67

AS-SET

AS12052 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 80 are in fix.csv.

  • ROA: none24
  • Route object: none1
  • Route object: RIR23
  • Route object: not announced32
ChangePrefix or setDetailFull-table peers
ROA: none167.64.57.0/24No ROA covers it. Add a ROA for AS12052, maxLength 24.671 of 673
Route object: none167.64.57.0/24No route object for it. A route object for 167.64.56.0/23 with origin AS12052 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12052 in the RIR database for the space.671 of 673
ROA: none167.64.24.0/24No ROA covers it. Add a ROA for AS12052, maxLength 24.671 of 673
Route object: RIR167.64.24.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none167.64.31.0/24No ROA covers it. Add a ROA for AS12052, maxLength 24.671 of 673
Route object: RIR167.64.31.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none167.64.32.0/24No ROA covers it. Add a ROA for AS12052, maxLength 24.671 of 673
Route object: RIR167.64.32.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none167.64.34.0/24No ROA covers it. Add a ROA for AS12052, maxLength 24.671 of 673
Route object: RIR167.64.34.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none167.64.43.0/24No ROA covers it. Add a ROA for AS12052, maxLength 24.671 of 673
Route object: RIR167.64.43.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none167.64.44.0/23No ROA covers it. Add a ROA for AS12052, maxLength 23.671 of 673
Route object: RIR167.64.44.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none167.64.46.0/24No ROA covers it. Add a ROA for AS12052, maxLength 24.671 of 673
Route object: RIR167.64.46.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none167.64.49.0/24No ROA covers it. Add a ROA for AS12052, maxLength 24.671 of 673
Route object: RIR167.64.49.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none167.64.72.0/22No ROA covers it. Add a ROA for AS12052, maxLength 22.671 of 673
Route object: RIR167.64.72.0/22Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space.671 of 673
ROA: none167.64.76.0/22No ROA covers it. Add a ROA for AS12052, maxLength 22.671 of 673
Route object: RIR167.64.76.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none167.64.85.0/24No ROA covers it. Add a ROA for AS12052, maxLength 24.671 of 673
Route object: RIR167.64.85.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none167.64.92.0/22No ROA covers it. Add a ROA for AS12052, maxLength 22.671 of 673
Route object: RIR167.64.92.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none167.64.96.0/22No ROA covers it. Add a ROA for AS12052, maxLength 22.671 of 673
Route object: RIR167.64.96.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none167.64.122.0/24No ROA covers it. Add a ROA for AS12052, maxLength 24.671 of 673
Route object: RIR167.64.122.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none167.64.153.0/24No ROA covers it. Add a ROA for AS12052, maxLength 24.671 of 673
Route object: RIR167.64.153.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none167.64.225.0/24No ROA covers it. Add a ROA for AS12052, maxLength 24.671 of 673
Route object: RIR167.64.225.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none167.64.227.0/24No ROA covers it. Add a ROA for AS12052, maxLength 24.671 of 673
Route object: RIR167.64.227.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none167.64.239.0/24No ROA covers it. Add a ROA for AS12052, maxLength 24.671 of 673
Route object: RIR167.64.239.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none167.64.243.0/24No ROA covers it. Add a ROA for AS12052, maxLength 24.671 of 673
Route object: RIR167.64.243.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none167.64.244.0/23No ROA covers it. Add a ROA for AS12052, maxLength 23.671 of 673
Route object: RIR167.64.244.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none167.64.247.0/24No ROA covers it. Add a ROA for AS12052, maxLength 24.671 of 673
Route object: RIR167.64.247.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none167.64.248.0/24No ROA covers it. Add a ROA for AS12052, maxLength 24.671 of 673
Route object: RIR167.64.248.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none167.64.249.0/24No ROA covers it. Add a ROA for AS12052, maxLength 24.671 of 673
Route object: RIR167.64.249.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

Route objects with origin AS12052 whose prefix no peer sees AS12052 announce. Many are kept on purpose (backup routes, space announced only in some places).

167.64.3.0/24RADBNo ROA
167.64.29.0/24RADBNo ROA
167.64.30.0/24RADBNo ROA
167.64.56.0/23RADBNo ROA
167.64.60.0/22NTTCOM, RADBNo ROA
167.64.60.0/23NTTCOM, RADBNo ROA
167.64.60.0/24NTTCOM, RADBNo ROA
167.64.61.0/24NTTCOM, RADBNo ROA
167.64.62.0/23NTTCOM, RADBNo ROA
167.64.62.0/24NTTCOM, RADBNo ROA
167.64.63.0/24NTTCOM, RADBNo ROA
167.64.71.0/24RADBNo ROA
167.64.72.0/23RADBNo ROA
167.64.74.0/24RADBNo ROA
167.64.92.0/23NTTCOM, RADBNo ROA
167.64.92.0/24NTTCOM, RADBNo ROA
167.64.93.0/24NTTCOM, RADBNo ROA
167.64.94.0/23NTTCOM, RADBNo ROA
167.64.94.0/24NTTCOM, RADBNo ROA
167.64.95.0/24NTTCOM, RADBNo ROA
167.64.96.0/23NTTCOM, RADBNo ROA
167.64.96.0/24NTTCOM, RADBNo ROA
167.64.97.0/24NTTCOM, RADBNo ROA
167.64.98.0/23NTTCOM, RADBNo ROA
167.64.98.0/24NTTCOM, RADBNo ROA
167.64.99.0/24NTTCOM, RADBNo ROA
167.64.143.0/24RADBNo ROA
167.64.148.0/24RADBNo ROA
167.64.151.0/24RADBNo ROA
167.64.152.0/24RADBNo ROA
167.64.156.0/23RADBNo ROA
167.64.185.0/24RADBNo ROA

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.