bgpreport

Network · data from 2026-11-12

AS9110 AGTelecom-AS "AMT GROUP TELECOM" Limited Liability Company

Registry name: AGTelecom-AS "AMT GROUP TELECOM" Limited Liability Company, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9110, 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.
185.75.250.0/24 No ROA RIR databaseRIPE 673 100% 67
194.246.80.0/24 No ROA RIR databaseRIPE 672 100% 67
212.111.64.0/21 No ROA RIR databaseRIPE 672 100% 67
212.111.72.0/22 No ROA RIR databaseRIPE 672 100% 67
212.111.76.0/24 No ROA RIR databaseRIPE 672 100% 67
212.111.79.0/24 No ROA RIR databaseRIPE 672 100% 67
212.111.90.0/24 No ROA RIR databaseRIPE 672 100% 67
212.111.92.0/22 No ROA RIR databaseRIPE 672 100% 67
212.233.64.0/22 No ROA RIR databaseRIPE 672 100% 67
212.233.100.0/22 No ROA RIR databaseRIPE 672 100% 67
212.233.104.0/21 No ROA RIR databaseRIPE 672 100% 67
212.233.111.0/24 No ROA RIR databaseRIPE 672 100% 67
212.233.112.0/21 No ROA RIR databaseRIPE 672 100% 67
212.233.124.0/22 No ROA RIR databaseRIPE 672 100% 67
2a05:6d80::/29 No ROA RIR databaseRIPE 633 100% 67
212.233.104.0/24 No ROA RIR databaseRIPE 3 0%low visibility 2
212.233.105.0/24 No ROA RIR databaseRIPE 3 0%low visibility 2
212.233.109.0/24 No ROA RIR databaseRIPE 3 0%low visibility 2

AS-SET

AS9110 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 25 are in fix.csv.

  • ROA: none18
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none185.75.250.0/24No ROA covers it. Add a ROA for AS9110, maxLength 24.673 of 673
ROA: none194.246.80.0/24No ROA covers it. Add a ROA for AS9110, maxLength 24.672 of 673
ROA: none212.111.64.0/21No ROA covers it. Add a ROA for AS9110, maxLength 21.672 of 673
ROA: none212.111.72.0/22No ROA covers it. Add a ROA for AS9110, maxLength 22.672 of 673
ROA: none212.111.76.0/24No ROA covers it. Add a ROA for AS9110, maxLength 24.672 of 673
ROA: none212.111.79.0/24No ROA covers it. Add a ROA for AS9110, maxLength 24.672 of 673
ROA: none212.111.90.0/24No ROA covers it. Add a ROA for AS9110, maxLength 24.672 of 673
ROA: none212.111.92.0/22No ROA covers it. Add a ROA for AS9110, maxLength 22.672 of 673
ROA: none212.233.64.0/22No ROA covers it. Add a ROA for AS9110, maxLength 22.672 of 673
ROA: none212.233.100.0/22No ROA covers it. Add a ROA for AS9110, maxLength 22.672 of 673
ROA: none212.233.104.0/21No ROA covers it. Add a ROA for AS9110, maxLength 21.672 of 673
ROA: none212.233.111.0/24No ROA covers it. Add a ROA for AS9110, maxLength 24.672 of 673
ROA: none212.233.112.0/21No ROA covers it. Add a ROA for AS9110, maxLength 21.672 of 673
ROA: none212.233.124.0/22No ROA covers it. Add a ROA for AS9110, maxLength 22.672 of 673
ROA: none2a05:6d80::/29No ROA covers it. Add a ROA for AS9110, maxLength 29.633 of 636
ROA: none212.233.104.0/24No ROA covers it. Add a ROA for AS9110, maxLength 24.3 of 673
ROA: none212.233.105.0/24No ROA covers it. Add a ROA for AS9110, maxLength 24.3 of 673
ROA: none212.233.109.0/24No ROA covers it. Add a ROA for AS9110, maxLength 24.3 of 673

Route objects not announced

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

212.111.64.0/24RIPENo ROA
212.233.101.66/32RIPENo ROA
212.233.106.0/24RIPENo ROA
212.233.107.0/24RIPENo ROA
212.233.108.0/24RIPENo ROA
212.233.110.0/24RIPENo ROA
212.233.126.0/24RIPENo 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.