bgpreport

Network · data from 2026-11-12

AS206066 TELEDOM-AS Teledom LLC

Registry name: TELEDOM-AS Teledom LLC, RU · not in PeeringDB

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

Announced routes

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

2a0a:7540::/32 No ROA Nonecovered by 2a0a:7540::/29 636 100% 67
185.197.32.0/23 No ROA RIR databaseRIPE 673 100% 66
185.197.34.0/23 No ROA RIR databaseRIPE 673 100% 66
91.90.198.0/23 No ROA RIR databaseRIPE 671 100% 68
91.90.198.0/24 No ROA RIR databaseRIPE 671 100% 68
91.90.199.0/24 No ROA RIR databaseRIPE 671 100% 68
185.197.32.0/22 No ROA RIR databaseRIPE 671 100% 68
185.197.32.0/24 No ROA RIR databaseRIPE 671 100% 68
185.197.33.0/24 No ROA RIR databaseRIPE 671 100% 68
185.197.34.0/24 No ROA RIR databaseRIPE 671 100% 68
185.197.35.0/24 No ROA RIR databaseRIPE 671 100% 68
2a0a:7540::/48 No ROA RIR databaseRIPE 636 100% 69
2a0a:7540:1::/48 No ROA RIR databaseRIPE 636 100% 69
2a0a:7540:2::/48 No ROA RIR databaseRIPE 636 100% 69
2a0a:7540:3::/48 No ROA RIR databaseRIPE 636 100% 69
2a0a:7540::/29 No ROA RIR databaseRIPE 635 100% 69

AS-SET

AS206066 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 20 are in fix.csv.

  • ROA: none16
  • Route object: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2a0a:7540::/32No ROA covers it. Add a ROA for AS206066, maxLength 32.636 of 636
Route object: none2a0a:7540::/32No route object for it. A route object for 2a0a:7540::/29 with origin AS206066 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206066 in the RIR database for the space.636 of 636
ROA: none185.197.32.0/23No ROA covers it. Add a ROA for AS206066, maxLength 23.673 of 673
ROA: none185.197.34.0/23No ROA covers it. Add a ROA for AS206066, maxLength 23.673 of 673
ROA: none91.90.198.0/23No ROA covers it. Add a ROA for AS206066, maxLength 23.671 of 673
ROA: none91.90.198.0/24No ROA covers it. Add a ROA for AS206066, maxLength 24.671 of 673
ROA: none91.90.199.0/24No ROA covers it. Add a ROA for AS206066, maxLength 24.671 of 673
ROA: none185.197.32.0/22No ROA covers it. Add a ROA for AS206066, maxLength 22.671 of 673
ROA: none185.197.32.0/24No ROA covers it. Add a ROA for AS206066, maxLength 24.671 of 673
ROA: none185.197.33.0/24No ROA covers it. Add a ROA for AS206066, maxLength 24.671 of 673
ROA: none185.197.34.0/24No ROA covers it. Add a ROA for AS206066, maxLength 24.671 of 673
ROA: none185.197.35.0/24No ROA covers it. Add a ROA for AS206066, maxLength 24.671 of 673
ROA: none2a0a:7540::/48No ROA covers it. Add a ROA for AS206066, maxLength 48.636 of 636
ROA: none2a0a:7540:1::/48No ROA covers it. Add a ROA for AS206066, maxLength 48.636 of 636
ROA: none2a0a:7540:2::/48No ROA covers it. Add a ROA for AS206066, maxLength 48.636 of 636
ROA: none2a0a:7540:3::/48No ROA covers it. Add a ROA for AS206066, maxLength 48.636 of 636
ROA: none2a0a:7540::/29No ROA covers it. Add a ROA for AS206066, maxLength 29.635 of 636

Route objects not announced

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

185.197.32.216/29RIPENo ROA
2a0a:7540:f000::/48RIPENo ROA
2a0a:7540:ffff::/48RIPENo 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.