bgpreport

Network · data from 2026-11-12

AS204153 TELEKONIKA-AS JOINT-STOCK COMPANY "TELEPORT TELECOM"

Registry name: TELEKONIKA-AS JOINT-STOCK COMPANY "TELEPORT TELECOM", RU · not in PeeringDB

11IPv4 routes 0.0% RPKI valid · 36.4% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
11No ROA 7 with no route object for this origin
6Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS204153, seen from no peer

Announced routes

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

193.24.229.0/24 No ROA Nonecovered by 193.24.228.0/22 671 100% 67
86.110.15.0/26 No ROA Nonecovered by 86.110.15.0/24 1 0%low visibility 1
86.110.15.64/27 No ROA Nonecovered by 86.110.15.0/24 1 0%low visibility 1
86.110.15.96/27 No ROA Nonecovered by 86.110.15.0/24 1 0%low visibility 1
86.110.15.128/26 No ROA Nonecovered by 86.110.15.0/24 1 0%low visibility 1
86.110.23.0/26 No ROA Nonecovered by 86.110.23.0/24 1 0%low visibility 1
193.24.230.32/27 No ROA Nonecovered by 193.24.228.0/22 1 0%low visibility 1
86.110.13.0/24 No ROA RIR databaseRIPE 669 99% 68
86.110.15.0/24 No ROA RIR databaseRIPE 669 99% 68
86.110.23.0/24 No ROA RIR databaseRIPE 669 99% 68
193.24.231.0/24 No ROA RIR databaseRIPE 669 99% 68

AS-SET

AS204153 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 19 are in fix.csv.

  • ROA: none11
  • Route object: none7
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none193.24.229.0/24No ROA covers it. Add a ROA for AS204153, maxLength 24.671 of 673
Route object: none193.24.229.0/24No route object for it. A route object for 193.24.228.0/22 with origin AS204153 covers it (filters allowing more-specifics accept it). Add a route object with origin AS204153 in the RIR database for the space.671 of 673
ROA: none86.110.15.0/26No ROA covers it. Add a ROA for AS204153, maxLength 26.1 of 673
Route object: none86.110.15.0/26No route object for it. A route object for 86.110.15.0/24 with origin AS204153 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS204153 in the RIR database for the space.1 of 673
ROA: none86.110.15.64/27No ROA covers it. Add a ROA for AS204153, maxLength 27.1 of 673
Route object: none86.110.15.64/27No route object for it. A route object for 86.110.15.0/24 with origin AS204153 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS204153 in the RIR database for the space.1 of 673
ROA: none86.110.15.96/27No ROA covers it. Add a ROA for AS204153, maxLength 27.1 of 673
Route object: none86.110.15.96/27No route object for it. A route object for 86.110.15.0/24 with origin AS204153 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS204153 in the RIR database for the space.1 of 673
ROA: none86.110.15.128/26No ROA covers it. Add a ROA for AS204153, maxLength 26.1 of 673
Route object: none86.110.15.128/26No route object for it. A route object for 86.110.15.0/24 with origin AS204153 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS204153 in the RIR database for the space.1 of 673
ROA: none86.110.23.0/26No ROA covers it. Add a ROA for AS204153, maxLength 26.1 of 673
Route object: none86.110.23.0/26No route object for it. A route object for 86.110.23.0/24 with origin AS204153 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS204153 in the RIR database for the space.1 of 673
ROA: none193.24.230.32/27No ROA covers it. Add a ROA for AS204153, maxLength 27.1 of 673
Route object: none193.24.230.32/27No route object for it. A route object for 193.24.228.0/22 with origin AS204153 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS204153 in the RIR database for the space.1 of 673
ROA: none86.110.13.0/24No ROA covers it. Add a ROA for AS204153, maxLength 24.669 of 673
ROA: none86.110.15.0/24No ROA covers it. Add a ROA for AS204153, maxLength 24.669 of 673
ROA: none86.110.23.0/24No ROA covers it. Add a ROA for AS204153, maxLength 24.669 of 673
ROA: none193.24.231.0/24No ROA covers it. Add a ROA for AS204153, maxLength 24.669 of 673

Route objects not announced

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

193.24.228.0/22RIPENo ROA

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.