bgpreport

Network · data from 2026-11-12

AS26499 VATECH-DCMETRO

Registry name: VATECH-DCMETRO - Virginia Polytechnic Institute and State Univ., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS26499, 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.
38.68.224.0/20 No ROA Other IRR onlyRADB 673 100% 68
45.3.96.0/20 No ROA Other IRR onlyRADB 673 100% 68
45.3.112.0/23 No ROA Other IRR onlyRADB 673 100% 68
38.68.252.0/24 No ROA Other IRR onlyRADB 672 100% 67
2607:b400:800::/40 No ROA Other IRR onlyRADB 636 100% 70
2607:b400:800::/48 No ROA Other IRR onlyRADB 636 100% 70
2607:b400:a04::/48 No ROA Other IRR onlyRADB 636 100% 70

AS-SET

AS26499's PeeringDB record names no 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 14 are in fix.csv.

  • ROA: none7
  • Route object: RIR7
ChangePrefix or setDetailFull-table peers
ROA: none38.68.224.0/20No ROA covers it. Add a ROA for AS26499, maxLength 20.673 of 673
Route object: RIR38.68.224.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none45.3.96.0/20No ROA covers it. Add a ROA for AS26499, maxLength 20.673 of 673
Route object: RIR45.3.96.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none45.3.112.0/23No ROA covers it. Add a ROA for AS26499, maxLength 23.673 of 673
Route object: RIR45.3.112.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.68.252.0/24No ROA covers it. Add a ROA for AS26499, maxLength 24.672 of 673
Route object: RIR38.68.252.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2607:b400:800::/40No ROA covers it. Add a ROA for AS26499, maxLength 40.636 of 636
Route object: RIR2607:b400:800::/40Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2607:b400:800::/48No ROA covers it. Add a ROA for AS26499, maxLength 48.636 of 636
Route object: RIR2607:b400:800::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2607:b400:a04::/48No ROA covers it. Add a ROA for AS26499, maxLength 48.636 of 636
Route object: RIR2607:b400:a04::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

Every route object with origin AS26499 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.