bgpreport

Network · data from 2026-11-12

AS201279 Loginov Vladislav

Registry name: AWAS-AS Loginov Vladislav, RU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS201279, 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.
2a0d:d940:3000::/36 No ROA None 1 0%low visibility 1
2a0b:4e07:a50::/48 Valid None 633 100% 69
2a0b:4e07:a60::/44 Valid None 633 100% 69
2a0b:4e07:a40::/44 Valid None 1 0%low visibility 1
217.60.240.0/24 Valid RIR databaseRIPE 673 100% 66
217.60.245.0/24 Valid RIR databaseRIPE 673 100% 66
2a0f:6282::/36 Valid RIR databaseRIPE 635 100% 69
2a0f:6282::/40 Valid RIR databaseRIPE 1 0%low visibility 1
2a0f:6282:100::/48 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

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

  • ROA: none1
  • Route object: none4
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2a0d:d940:3000::/36No ROA covers it. Add a ROA for AS201279, maxLength 36.1 of 636
Route object: none2a0d:d940:3000::/36No route object for it. Add a route object with origin AS201279 in the RIR database for the space.1 of 636
Route object: none2a0b:4e07:a50::/48No route object for it. Add a route object with origin AS201279 in the RIR database for the space.633 of 636
Route object: none2a0b:4e07:a60::/44No route object for it. Add a route object with origin AS201279 in the RIR database for the space.633 of 636
Route object: none2a0b:4e07:a40::/44No route object for it. Add a route object with origin AS201279 in the RIR database for the space.1 of 636

Route objects not announced

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

2a0f:6282::/48RIPEValid
2a0f:6282:1::/48RIPEValid
2a0f:6282:101::/48RIPEValid
2a0f:6282:102::/48RIPEValid

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.