bgpreport

Network · data from 2026-11-12

AS205515 Telesystems Telecommunication Systems LLC

Registry name: Telesystems Telecommunication Systems LLC, RU · not in PeeringDB

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

Announced routes

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

77.121.14.0/24 No ROA RIR databaseRIPE 671 100% 68
77.123.224.0/20 No ROA RIR databaseRIPE 671 100% 68
77.123.240.0/21 No ROA RIR databaseRIPE 671 100% 68
77.123.248.0/24 No ROA RIR databaseRIPE 671 100% 68
77.123.249.0/24 No ROA RIR databaseRIPE 671 100% 68
77.123.250.0/24 No ROA RIR databaseRIPE 671 100% 68
77.123.251.0/24 No ROA RIR databaseRIPE 671 100% 68
194.39.249.0/24 No ROA RIR databaseRIPE 671 100% 68
77.121.32.0/19 No ROA RIR databaseRIPE 670 100% 68
77.123.192.0/19 No ROA RIR databaseRIPE 670 100% 68
77.123.252.0/22 No ROA RIR databaseRIPE 670 100% 68

AS-SET

AS205515 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 13 are in fix.csv.

  • ROA: none11
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none77.121.14.0/24No ROA covers it. Add a ROA for AS205515, maxLength 24.671 of 673
ROA: none77.123.224.0/20No ROA covers it. Add a ROA for AS205515, maxLength 20.671 of 673
ROA: none77.123.240.0/21No ROA covers it. Add a ROA for AS205515, maxLength 21.671 of 673
ROA: none77.123.248.0/24No ROA covers it. Add a ROA for AS205515, maxLength 24.671 of 673
ROA: none77.123.249.0/24No ROA covers it. Add a ROA for AS205515, maxLength 24.671 of 673
ROA: none77.123.250.0/24No ROA covers it. Add a ROA for AS205515, maxLength 24.671 of 673
ROA: none77.123.251.0/24No ROA covers it. Add a ROA for AS205515, maxLength 24.671 of 673
ROA: none194.39.249.0/24No ROA covers it. Add a ROA for AS205515, maxLength 24.671 of 673
ROA: none77.121.32.0/19No ROA covers it. Add a ROA for AS205515, maxLength 19.670 of 673
ROA: none77.123.192.0/19No ROA covers it. Add a ROA for AS205515, maxLength 19.670 of 673
ROA: none77.123.252.0/22No ROA covers it. Add a ROA for AS205515, maxLength 22.670 of 673

Route objects not announced

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

77.121.32.0/20RIPENo ROA
77.123.248.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.