bgpreport

Network · data from 2026-11-12

AS62366 STOLICA Net

Registry name: STOLICA-AS Stolica Telecom Ltd., RU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS62366, 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.
45.139.18.16/29 No ROA Nonecovered by 45.139.18.0/23 1 0%low visibility 1
45.139.18.64/29 No ROA Nonecovered by 45.139.18.0/23 1 0%low visibility 1
45.139.18.80/29 No ROA Nonecovered by 45.139.18.0/23 1 0%low visibility 1
45.139.17.0/24 No ROA RIR databaseRIPE 671 100% 68
45.139.18.0/23 No ROA RIR databaseRIPE 671 100% 68
146.158.76.0/24 Valid Nonecovered by 146.158.76.0/23 671 100% 68
146.158.77.0/24 Valid Nonecovered by 146.158.76.0/23 671 100% 68
93.171.135.0/24 Valid RIR databaseRIPE 671 100% 68
95.46.1.0/24 Valid RIR databaseRIPE 671 100% 68
146.158.76.0/23 Valid RIR databaseRIPE 671 100% 68

AS-SET

AS62366'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 10 are in fix.csv.

  • ROA: none5
  • Route object: none5
ChangePrefix or setDetailFull-table peers
ROA: none45.139.18.16/29No ROA covers it. Add a ROA for AS62366, maxLength 29.1 of 673
Route object: none45.139.18.16/29No route object for it. A route object for 45.139.18.0/23 with origin AS62366 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS62366 in the RIR database for the space.1 of 673
ROA: none45.139.18.64/29No ROA covers it. Add a ROA for AS62366, maxLength 29.1 of 673
Route object: none45.139.18.64/29No route object for it. A route object for 45.139.18.0/23 with origin AS62366 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS62366 in the RIR database for the space.1 of 673
ROA: none45.139.18.80/29No ROA covers it. Add a ROA for AS62366, maxLength 29.1 of 673
Route object: none45.139.18.80/29No route object for it. A route object for 45.139.18.0/23 with origin AS62366 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS62366 in the RIR database for the space.1 of 673
ROA: none45.139.17.0/24No ROA covers it. Add a ROA for AS62366, maxLength 24.671 of 673
ROA: none45.139.18.0/23No ROA covers it. Add a ROA for AS62366, maxLength 23.671 of 673
Route object: none146.158.76.0/24No route object for it. A route object for 146.158.76.0/23 with origin AS62366 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62366 in the RIR database for the space.671 of 673
Route object: none146.158.77.0/24No route object for it. A route object for 146.158.76.0/23 with origin AS62366 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62366 in the RIR database for the space.671 of 673

Route objects not announced

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