bgpreport

Network · data from 2026-11-12

AS9113 VLANT-AS VLANT LLC

Registry name: VLANT-AS VLANT LLC, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9113, 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.
2a01:548::/44 No ROA Nonecovered by 2a01:548::/32 634 100% 68
2a01:548:10::/44 No ROA Nonecovered by 2a01:548::/32 634 100% 68
77.236.32.0/19 No ROA RIR databaseRIPE 672 100% 67
77.236.32.0/20 No ROA RIR databaseRIPE 672 100% 67
77.236.48.0/20 No ROA RIR databaseRIPE 672 100% 67
185.206.204.0/22 No ROA RIR databaseRIPE 672 100% 67
2a01:548::/32 No ROA RIR databaseRIPE 635 100% 68

AS-SET

AS9113 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 9 are in fix.csv.

  • ROA: none7
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: none2a01:548::/44No ROA covers it. Add a ROA for AS9113, maxLength 44.634 of 636
Route object: none2a01:548::/44No route object for it. A route object for 2a01:548::/32 with origin AS9113 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9113 in the RIR database for the space.634 of 636
ROA: none2a01:548:10::/44No ROA covers it. Add a ROA for AS9113, maxLength 44.634 of 636
Route object: none2a01:548:10::/44No route object for it. A route object for 2a01:548::/32 with origin AS9113 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9113 in the RIR database for the space.634 of 636
ROA: none77.236.32.0/19No ROA covers it. Add a ROA for AS9113, maxLength 19.672 of 673
ROA: none77.236.32.0/20No ROA covers it. Add a ROA for AS9113, maxLength 20.672 of 673
ROA: none77.236.48.0/20No ROA covers it. Add a ROA for AS9113, maxLength 20.672 of 673
ROA: none185.206.204.0/22No ROA covers it. Add a ROA for AS9113, maxLength 22.672 of 673
ROA: none2a01:548::/32No ROA covers it. Add a ROA for AS9113, maxLength 32.635 of 636

Route objects not announced

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