bgpreport

Network · data from 2026-11-12

AS12700 Komertsiyno Virobnitcha Firma "VEKTOR"

Registry name: SC-VEKTOR-AS Komertsiyno Virobnitcha Firma "VEKTOR" LLC, UA · PeeringDB

14IPv4 routes 100.0% RPKI valid · 42.9% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No 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 AS12700, seen from no peer

Announced routes

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

31.131.32.0/24 Valid Nonecovered by 31.131.32.0/21 210 31% 52
31.131.33.0/24 Valid Nonecovered by 31.131.32.0/21 210 31% 52
31.131.34.0/24 Valid Nonecovered by 31.131.32.0/21 210 31% 52
31.131.35.0/24 Valid Nonecovered by 31.131.32.0/21 210 31% 52
31.131.36.0/24 Valid Nonecovered by 31.131.32.0/21 210 31% 52
31.131.37.0/24 Valid Nonecovered by 31.131.32.0/21 210 31% 52
31.131.38.0/24 Valid Nonecovered by 31.131.32.0/21 210 31% 52
31.131.39.0/24 Valid Nonecovered by 31.131.32.0/21 210 31% 52
31.131.32.0/21 Valid RIR databaseRIPE 671 100% 67
91.202.240.0/24 Valid RIR databaseRIPE 671 100% 67
91.202.241.0/24 Valid RIR databaseRIPE 671 100% 67
91.202.242.0/24 Valid RIR databaseRIPE 671 100% 67
91.202.243.0/24 Valid RIR databaseRIPE 671 100% 67
91.202.240.0/22 Valid RIR databaseRIPE 669 99% 67

AS-SET

AS12700'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 8 are in fix.csv.

  • Route object: none8
ChangePrefix or setDetailFull-table peers
Route object: none31.131.32.0/24No route object for it. A route object for 31.131.32.0/21 with origin AS12700 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12700 in the RIR database for the space.210 of 673
Route object: none31.131.33.0/24No route object for it. A route object for 31.131.32.0/21 with origin AS12700 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12700 in the RIR database for the space.210 of 673
Route object: none31.131.34.0/24No route object for it. A route object for 31.131.32.0/21 with origin AS12700 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12700 in the RIR database for the space.210 of 673
Route object: none31.131.35.0/24No route object for it. A route object for 31.131.32.0/21 with origin AS12700 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12700 in the RIR database for the space.210 of 673
Route object: none31.131.36.0/24No route object for it. A route object for 31.131.32.0/21 with origin AS12700 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12700 in the RIR database for the space.210 of 673
Route object: none31.131.37.0/24No route object for it. A route object for 31.131.32.0/21 with origin AS12700 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12700 in the RIR database for the space.210 of 673
Route object: none31.131.38.0/24No route object for it. A route object for 31.131.32.0/21 with origin AS12700 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12700 in the RIR database for the space.210 of 673
Route object: none31.131.39.0/24No route object for it. A route object for 31.131.32.0/21 with origin AS12700 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12700 in the RIR database for the space.210 of 673

Route objects not announced

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