bgpreport

Network · data from 2026-11-12

AS402933 VOSMET - Vosmet

Registry name: VOSMET - Vosmet, US · not in PeeringDB

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

Announced routes

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

2a10:77c0::/29 Invalid: origin None 7 1%low visibility 3
2a10:7ac0::/29 Invalid: origin None 7 1%low visibility 3
2a13:b640::/29 Invalid: origin None 7 1%low visibility 3
2a13:dfc0::/29 Invalid: origin None 7 1%low visibility 3
2a0f:e3c0::/29 Invalid: origin None 1 0%low visibility 1
2a14:6ac0::/29 Invalid: origin None 1 0%low visibility 1
2a13:bfc0::/29 No ROA None 7 1%low visibility 3
2a13:c040::/29 No ROA None 7 1%low visibility 3
2a13:bec0::/29 Valid RIR databaseRIPE 634 100% 69
2a13:c440::/29 Valid RIR databaseRIPE 634 100% 69

AS-SET

AS402933 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: origin6
  • ROA: none2
  • Route object: none8
ChangePrefix or setDetailFull-table peers
ROA: origin2a10:77c0::/29An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS402933 should announce it, add a ROA for AS402933.7 of 636
Route object: none2a10:77c0::/29No route object for it. Add a route object with origin AS402933 in the RIR database for the space.7 of 636
ROA: origin2a10:7ac0::/29An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS402933 should announce it, add a ROA for AS402933.7 of 636
Route object: none2a10:7ac0::/29No route object for it. Add a route object with origin AS402933 in the RIR database for the space.7 of 636
ROA: origin2a13:b640::/29An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS402933 should announce it, add a ROA for AS402933.7 of 636
Route object: none2a13:b640::/29No route object for it. Add a route object with origin AS402933 in the RIR database for the space.7 of 636
ROA: origin2a13:dfc0::/29An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS402933 should announce it, add a ROA for AS402933.7 of 636
Route object: none2a13:dfc0::/29No route object for it. Add a route object with origin AS402933 in the RIR database for the space.7 of 636
ROA: origin2a0f:e3c0::/29An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS402933 should announce it, add a ROA for AS402933.1 of 636
Route object: none2a0f:e3c0::/29No route object for it. Add a route object with origin AS402933 in the RIR database for the space.1 of 636
ROA: origin2a14:6ac0::/29An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS402933 should announce it, add a ROA for AS402933.1 of 636
Route object: none2a14:6ac0::/29No route object for it. Add a route object with origin AS402933 in the RIR database for the space.1 of 636
ROA: none2a13:bfc0::/29No ROA covers it. Add a ROA for AS402933, maxLength 29.7 of 636
Route object: none2a13:bfc0::/29No route object for it. Add a route object with origin AS402933 in the RIR database for the space.7 of 636
ROA: none2a13:c040::/29No ROA covers it. Add a ROA for AS402933, maxLength 29.7 of 636
Route object: none2a13:c040::/29No route object for it. Add a route object with origin AS402933 in the RIR database for the space.7 of 636

Route objects not announced

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