bgpreport

Network · data from 2026-11-12

AS47747 TeleTower

Registry name: TMK-NET-AS Limited Liability Company "TeleTower", RU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS47747, 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.
31.3.21.0/24 No ROA Nonecovered by 31.3.16.0/21 671 100% 66
31.3.23.120/32 No ROA Nonecovered by 31.3.16.0/21 1 0%low visibility 1
31.3.16.0/21 No ROA RIR databaseRIPE 673 100% 66
31.3.18.0/24 No ROA RIR databaseRIPE 673 100% 66
185.109.160.0/24 No ROA RIR databaseRIPE 673 100% 66
185.117.244.0/22 No ROA RIR databaseRIPE 673 100% 66
185.117.246.0/23 No ROA RIR databaseRIPE 673 100% 66
2a03:fec0::/32 No ROA RIR databaseRIPE 635 100% 67
2a10:540::/29 No ROA RIR databaseRIPE 632 99% 67

AS-SET

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

  • ROA: none9
  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none31.3.21.0/24No ROA covers it. Add a ROA for AS47747, maxLength 24.671 of 673
Route object: none31.3.21.0/24No route object for it. A route object for 31.3.16.0/21 with origin AS47747 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47747 in the RIR database for the space.671 of 673
ROA: none31.3.23.120/32No ROA covers it. Add a ROA for AS47747, maxLength 32.1 of 673
Route object: none31.3.23.120/32No route object for it. A route object for 31.3.16.0/21 with origin AS47747 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS47747 in the RIR database for the space.1 of 673
ROA: none31.3.16.0/21No ROA covers it. Add a ROA for AS47747, maxLength 21.673 of 673
ROA: none31.3.18.0/24No ROA covers it. Add a ROA for AS47747, maxLength 24.673 of 673
ROA: none185.109.160.0/24No ROA covers it. Add a ROA for AS47747, maxLength 24.673 of 673
ROA: none185.117.244.0/22No ROA covers it. Add a ROA for AS47747, maxLength 22.673 of 673
ROA: none185.117.246.0/23No ROA covers it. Add a ROA for AS47747, maxLength 23.673 of 673
ROA: none2a03:fec0::/32No ROA covers it. Add a ROA for AS47747, maxLength 32.635 of 636
ROA: none2a10:540::/29No ROA covers it. Add a ROA for AS47747, maxLength 29.632 of 636

Route objects not announced

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

31.3.19.0/24RIPENo ROA
2a03:79a0::/32RIPENo 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.