bgpreport

Network · data from 2026-11-12

AS25515 CTCNET-AS PJSC Rostelecom

Registry name: CTCNET-AS PJSC Rostelecom, RU · not in PeeringDB

20IPv4 routes 100.0% RPKI valid · 65.0% with a route object
5IPv6 routes 20.0% RPKI valid · 20.0% with a route object
4RPKI invalid 0 origin · 4 maxLength
0No ROA 11 with no route object for this origin
4Low visibility seen by under 10% of full-table peers
14Route objects not announced registered with origin AS25515, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS25515, 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.
2a00:56c0:40d:4::/64 Invalid: maxLength Nonecovered by 2a00:56c0:40d::/48 1 0%low visibility 1
2a00:56c0:40d:5::/64 Invalid: maxLength Nonecovered by 2a00:56c0:40d::/48 1 0%low visibility 1
2a00:56c0:40d:8002::/64 Invalid: maxLength Nonecovered by 2a00:56c0:40d::/48 1 0%low visibility 1
2a00:56c0:40d:8004::/64 Invalid: maxLength Nonecovered by 2a00:56c0:40d::/48 1 0%low visibility 1
77.51.176.0/21 Valid Other origin onlycovered by 77.51.0.0/16 672 100% 67
77.51.184.0/21 Valid Other origin onlycovered by 77.51.0.0/16 672 100% 67
77.51.192.0/21 Valid Other origin onlycovered by 77.51.0.0/16 672 100% 67
77.51.200.0/21 Valid Other origin onlycovered by 77.51.0.0/16 672 100% 67
77.51.208.0/21 Valid Other origin onlycovered by 77.51.0.0/16 672 100% 67
77.51.216.0/21 Valid Other origin onlycovered by 77.51.0.0/16 672 100% 67
77.51.224.0/21 Valid Other origin onlycovered by 77.51.0.0/16 672 100% 67
77.51.0.0/16 Valid RIR databaseRIPE 672 100% 67
85.94.0.0/19 Valid RIR databaseRIPE 672 100% 67
89.109.192.0/18 Valid RIR databaseRIPE 672 100% 67
90.154.120.0/21 Valid RIR databaseRIPE 672 100% 67
91.188.223.0/24 Valid RIR databaseRIPE 672 100% 67
95.72.0.0/15 Valid RIR databaseRIPE 672 100% 67
146.19.98.0/24 Valid RIR databaseRIPE 672 100% 67
185.141.236.0/23 Valid RIR databaseRIPE 672 100% 67
185.202.109.0/24 Valid RIR databaseRIPE 672 100% 67
193.3.188.0/24 Valid RIR databaseRIPE 672 100% 67
213.140.224.0/19 Valid RIR databaseRIPE 672 100% 67
217.107.96.0/21 Valid RIR databaseRIPE 672 100% 67
217.107.104.0/23 Valid RIR databaseRIPE 672 100% 67
2a00:56c0:40d::/48 Valid RIR databaseRIPE 635 100% 68

AS-SET

AS25515 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 29 are in fix.csv.

  • ROA: maxLength4
  • Route object: none11
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: maxLength2a00:56c0:40d:4::/64ROA 2a00:56c0:40d::/48 AS25515 has maxLength 48; the route is a /64. Raise the maxLength, or add a ROA for 2a00:56c0:40d:4::/64.1 of 636
Route object: none2a00:56c0:40d:4::/64No route object for it. A route object for 2a00:56c0:40d::/48 with origin AS25515 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS25515 in the RIR database for the space.1 of 636
ROA: maxLength2a00:56c0:40d:5::/64ROA 2a00:56c0:40d::/48 AS25515 has maxLength 48; the route is a /64. Raise the maxLength, or add a ROA for 2a00:56c0:40d:5::/64.1 of 636
Route object: none2a00:56c0:40d:5::/64No route object for it. A route object for 2a00:56c0:40d::/48 with origin AS25515 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS25515 in the RIR database for the space.1 of 636
ROA: maxLength2a00:56c0:40d:8002::/64ROA 2a00:56c0:40d::/48 AS25515 has maxLength 48; the route is a /64. Raise the maxLength, or add a ROA for 2a00:56c0:40d:8002::/64.1 of 636
Route object: none2a00:56c0:40d:8002::/64No route object for it. A route object for 2a00:56c0:40d::/48 with origin AS25515 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS25515 in the RIR database for the space.1 of 636
ROA: maxLength2a00:56c0:40d:8004::/64ROA 2a00:56c0:40d::/48 AS25515 has maxLength 48; the route is a /64. Raise the maxLength, or add a ROA for 2a00:56c0:40d:8004::/64.1 of 636
Route object: none2a00:56c0:40d:8004::/64No route object for it. A route object for 2a00:56c0:40d::/48 with origin AS25515 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS25515 in the RIR database for the space.1 of 636
Route object: none77.51.176.0/21Route objects for it name AS12389. A route object for 77.51.0.0/16 with origin AS25515 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25515 in the RIR database for the space.672 of 673
Route object: none77.51.184.0/21Route objects for it name AS12389. A route object for 77.51.0.0/16 with origin AS25515 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25515 in the RIR database for the space.672 of 673
Route object: none77.51.192.0/21Route objects for it name AS12389. A route object for 77.51.0.0/16 with origin AS25515 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25515 in the RIR database for the space.672 of 673
Route object: none77.51.200.0/21Route objects for it name AS12389. A route object for 77.51.0.0/16 with origin AS25515 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25515 in the RIR database for the space.672 of 673
Route object: none77.51.208.0/21Route objects for it name AS12389. A route object for 77.51.0.0/16 with origin AS25515 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25515 in the RIR database for the space.672 of 673
Route object: none77.51.216.0/21Route objects for it name AS12389. A route object for 77.51.0.0/16 with origin AS25515 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25515 in the RIR database for the space.672 of 673
Route object: none77.51.224.0/21Route objects for it name AS12389. A route object for 77.51.0.0/16 with origin AS25515 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25515 in the RIR database for the space.672 of 673

Route objects not announced

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

62.233.47.0/24RIPEValid
77.51.232.0/21RIPEInvalid: maxLength
77.51.240.0/22RIPEInvalid: maxLength
77.51.244.0/23RIPEInvalid: maxLength
77.51.246.0/24RIPEInvalid: maxLength
77.51.248.0/24RIPEInvalid: maxLength
77.51.251.0/24RIPEInvalid: maxLength
85.94.2.0/23RIPEInvalid: maxLength
85.94.4.0/22RIPEInvalid: maxLength
85.94.8.0/22RIPEInvalid: maxLength
85.94.12.0/22RIPEInvalid: maxLength
85.94.26.0/23RIPEInvalid: maxLength
89.109.232.0/21RIPEInvalid: maxLength
89.109.248.0/21RIPEInvalid: maxLength

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.