Routing security
AS41798 TTC-AS JSC Transtelecom
Unclassified RIPE NSP
RPKI valid
99%
204 of 207 announcements
RPKI invalid
0
none
No ROA
3
not covered by any ROA
IRR registered
100%
0 missing · 0 other origin
ROAs
207
authorising this AS
Announcements
What this network originates
Every prefix observed with AS41798 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 194.135.25.0/24 | No ROA | IRR | 54 |
| 195.12.124.0/24 | No ROA | IRR | 54 |
| 195.58.52.0/24 | No ROA | IRR | 54 |
| 2.57.96.0/24 | RPKI valid | IRR | 54 |
| 2.57.97.0/24 | RPKI valid | IRR | 54 |
| 2.57.98.0/24 | RPKI valid | IRR | 54 |
| 2.57.99.0/24 | RPKI valid | IRR | 54 |
| 2a00:ab40::/32 | RPKI valid | IRR | 34 |
| 2a00:ab40:100::/48 | RPKI valid | IRR covering | 34 |
| 2a00:ab40:101::/48 | RPKI valid | IRR covering | 34 |
| 2a00:ab40:102::/48 | RPKI valid | IRR covering | 34 |
| 2a00:ab40:103::/48 | RPKI valid | IRR covering | 34 |
| 2a00:ab40:200::/48 | RPKI valid | IRR covering | 34 |
| 2a00:ab40:201::/48 | RPKI valid | IRR covering | 34 |
| 2a00:ab40:300::/48 | RPKI valid | IRR covering | 34 |
| 2a00:ab40:301::/48 | RPKI valid | IRR covering | 34 |
| 2a00:ab40:3000::/48 | RPKI valid | IRR | 34 |
| 2a00:ab40:4000::/48 | RPKI valid | IRR | 34 |
| 2a00:ab40:5000::/48 | RPKI valid | IRR | 32 |
| 2a00:ab40:7200::/48 | RPKI valid | IRR covering | 34 |
| 2a00:ab40:7201::/48 | RPKI valid | IRR covering | 34 |
| 2a00:ab40:7300::/48 | RPKI valid | IRR covering | 34 |
| 2a00:ab40:7301::/48 | RPKI valid | IRR covering | 34 |
| 2a00:ab40:7400::/48 | RPKI valid | IRR covering | 34 |
| 2a00:ab40:7401::/48 | RPKI valid | IRR covering | 34 |
| 37.17.176.0/21 | RPKI valid | IRR | 54 |
| 37.17.176.0/24 | RPKI valid | IRR | 54 |
| 37.17.177.0/24 | RPKI valid | IRR | 54 |
| 37.17.178.0/24 | RPKI valid | IRR | 54 |
| 37.17.180.0/24 | RPKI valid | IRR | 54 |
| 37.17.182.0/24 | RPKI valid | IRR | 54 |
| 37.17.183.0/24 | RPKI valid | IRR | 54 |
| 37.208.40.0/21 | RPKI valid | IRR | 54 |
| 37.208.40.0/24 | RPKI valid | IRR | 54 |
| 37.208.41.0/24 | RPKI valid | IRR | 54 |
| 37.208.42.0/24 | RPKI valid | IRR | 54 |
| 37.208.43.0/24 | RPKI valid | IRR | 54 |
| 37.208.44.0/24 | RPKI valid | IRR | 54 |
| 37.208.45.0/24 | RPKI valid | IRR | 54 |
| 37.208.46.0/24 | RPKI valid | IRR | 54 |
| 37.208.47.0/24 | RPKI valid | IRR | 54 |
| 45.88.90.0/24 | RPKI valid | IRR | 54 |
| 45.140.24.0/23 | RPKI valid | IRR | 54 |
| 45.140.24.0/24 | RPKI valid | IRR | 54 |
| 45.140.25.0/24 | RPKI valid | IRR | 54 |
| 45.144.175.0/24 | RPKI valid | IRR | 54 |
| 80.71.150.0/24 | RPKI valid | IRR | 55 |
| 82.115.44.0/22 | RPKI valid | IRR | 54 |
| 82.115.45.0/24 | RPKI valid | IRR | 54 |
| 82.115.46.0/24 | RPKI valid | IRR | 54 |
| 82.115.47.0/24 | RPKI valid | IRR | 54 |
| 87.255.202.0/23 | RPKI valid | IRR | 54 |
| 87.255.202.0/24 | RPKI valid | IRR | 54 |
| 87.255.203.0/24 | RPKI valid | IRR | 54 |
| 87.255.204.0/22 | RPKI valid | IRR | 54 |
| 87.255.204.0/24 | RPKI valid | IRR | 54 |
| 87.255.205.0/24 | RPKI valid | IRR | 54 |
| 87.255.206.0/24 | RPKI valid | IRR | 54 |
| 87.255.207.0/24 | RPKI valid | IRR | 54 |
| 87.255.208.0/20 | RPKI valid | IRR | 54 |
| 87.255.208.0/24 | RPKI valid | IRR | 54 |
| 87.255.209.0/24 | RPKI valid | IRR | 54 |
| 87.255.211.0/24 | RPKI valid | IRR | 54 |
| 87.255.212.0/24 | RPKI valid | IRR | 54 |
| 87.255.214.0/24 | RPKI valid | IRR | 54 |
| 87.255.215.0/24 | RPKI valid | IRR | 54 |
| 87.255.216.0/24 | RPKI valid | IRR | 54 |
| 87.255.217.0/24 | RPKI valid | IRR | 54 |
| 87.255.218.0/24 | RPKI valid | IRR | 54 |
| 87.255.219.0/24 | RPKI valid | IRR | 54 |
| 87.255.220.0/24 | RPKI valid | IRR | 54 |
| 87.255.221.0/24 | RPKI valid | IRR | 54 |
| 87.255.222.0/24 | RPKI valid | IRR | 54 |
| 87.255.223.0/24 | RPKI valid | IRR | 54 |
| 91.185.0.0/19 | RPKI valid | IRR | 54 |
| 91.185.1.0/24 | RPKI valid | IRR | 54 |
| 91.185.2.0/24 | RPKI valid | IRR | 54 |
| 91.185.3.0/24 | RPKI valid | IRR | 54 |
| 91.185.4.0/24 | RPKI valid | IRR | 54 |
| 91.185.5.0/24 | RPKI valid | IRR | 54 |
| 91.185.6.0/24 | RPKI valid | IRR | 54 |
| 91.185.7.0/24 | RPKI valid | IRR | 54 |
| 91.185.8.0/24 | RPKI valid | IRR | 54 |
| 91.185.9.0/24 | RPKI valid | IRR | 54 |
| 91.185.10.0/24 | RPKI valid | IRR | 54 |
| 91.185.12.0/24 | RPKI valid | IRR | 54 |
| 91.185.13.0/24 | RPKI valid | IRR | 54 |
| 91.185.14.0/24 | RPKI valid | IRR | 54 |
| 91.185.15.0/24 | RPKI valid | IRR | 54 |
| 91.185.16.0/24 | RPKI valid | IRR | 54 |
| 91.185.17.0/24 | RPKI valid | IRR | 54 |
| 91.185.18.0/24 | RPKI valid | IRR | 54 |
| 91.185.19.0/24 | RPKI valid | IRR | 54 |
| 91.185.20.0/24 | RPKI valid | IRR | 54 |
| 91.185.21.0/24 | RPKI valid | IRR covering | 55 |
| 91.185.22.0/24 | RPKI valid | IRR | 54 |
| 91.185.23.0/24 | RPKI valid | IRR | 54 |
| 91.185.24.0/24 | RPKI valid | IRR | 54 |
| 91.185.25.0/24 | RPKI valid | IRR | 54 |
| 91.185.26.0/24 | RPKI valid | IRR | 54 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS41798 may originate these prefixes, up to the maximum length shown.
Showing 200 of 207.
ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.
RPKI · ASPA
Declared transit providers
No ASPA record This network has not published an ASPA object. ASPA lets a network sign the list of its transit providers, so routers can reject paths that route through anyone else (route leaks). Only a few thousand networks publish one so far, so its absence is normal.
IRR
Registered route objects
Route objects naming AS41798 as origin, across RADb, the RIR registries, ALTDB and NTTCOM. Objects that are registered but not announced come first: a stale object lets anyone who can spoof this origin through an IRR-built filter.
| Prefix | Source | Description | Maintainer | Changed | Routing |
|---|---|---|---|---|---|
| 37.17.179.0/24 | RIPE | Transtelecom Kazakhstan Network | MNT-TTCP | 2011-12-20 | Not announced |
| 37.17.181.0/24 | RIPE | Transtelecom Kazakhstan Network | MNT-TTCP | 2011-12-20 | Not announced |
| 82.115.44.0/24 | RIPE | TTC network | KPV28-RIPE | 2024-12-30 | Not announced |
| 87.255.210.0/24 | RIPE | JSC Transtelecom | KPV28-RIPE | 2019-01-16 | Not announced |
| 87.255.213.0/24 | RIPE | JSC Transtelecom | KPV28-RIPE | 2019-01-16 | Not announced |
| 91.185.0.0/22 | RIPE | TTC | MNT-TTCP | 2015-03-31 | Not announced |
| 91.185.0.0/24 | RIPE | JSC Transtelecom | KPV28-RIPE | 2019-01-16 | Not announced |
| 91.185.4.0/22 | RIPE | AlmatyTranstelNet | MNT-TTCP | 2006-11-22 | Not announced |
| 91.185.8.144/28 | RIPE | Transtelecom Kazakhstan | MNT-TTCP | 2007-02-13 | Not announced |
| 91.185.8.192/26 | RIPE | TTC Kazakhstan kizilorda network | MNT-TTCP | 2007-03-05 | Not announced |
| 91.185.11.0/24 | RADB | Proxy-registered route object | MAINT-AS3491 | 2025-03-28 | Not announced |
| 91.185.11.0/24 | RIPE | Transtelecom Kazakhstan | MNT-TTCP | 2011-07-13 | Not announced |
| 91.185.11.128/25 | RIPE | Transtelecom Kazakhstan | MNT-TTCP | 2007-03-21 | Not announced |
| 91.185.14.128/25 | RIPE | KazTTC Kokshetau DSL Network | MNT-TTCP | 2007-07-13 | Not announced |
| 91.185.20.0/23 | RIPE | Transtelecom Kazakhstan | MNT-TTCP | 2008-01-25 | Not announced |
| 176.98.237.0/24 | RIPE | — | KPV28-RIPE | 2022-01-26 | Not announced |
| 2.57.96.0/24 | RIPE | — | TTC_INET | 2019-04-02 | Announced |
| 2.57.97.0/24 | RIPE | NAT_Almaty | TTC_INET | 2019-04-02 | Announced |
| 2.57.98.0/24 | RIPE | NAT_Aktobe | TTC_INET | 2019-04-02 | Announced |
| 2.57.99.0/24 | RIPE | PPPoE_Aktobe | TTC_INET | 2019-04-02 | Announced |
| 37.17.176.0/21 | RIPE | Transtelecom Kazakhstan Network | MNT-TTCP | 2018-07-31 | Announced |
| 37.17.176.0/24 | RIPE | Transtelecom Kazakhstan Network | MNT-TTCP | 2011-12-20 | Announced |
| 37.17.177.0/24 | RIPE | Transtelecom Kazakhstan Network | MNT-TTCP | 2011-12-20 | Announced |
| 37.17.178.0/24 | RIPE | Transtelecom Kazakhstan Network | MNT-TTCP | 2011-12-20 | Announced |
| 37.17.180.0/24 | RIPE | Transtelecom Kazakhstan Network | MNT-TTCP | 2011-12-20 | Announced |
| 37.17.182.0/24 | RIPE | Transtelecom Kazakhstan Network | MNT-TTCP | 2011-12-20 | Announced |
| 37.17.183.0/24 | RIPE | Transtelecom Kazakhstan Network | MNT-TTCP | 2011-12-20 | Announced |
| 37.208.40.0/21 | RIPE | Transtelecom Kazakhstan Network | MNT-TTCP | 2012-04-02 | Announced |
| 37.208.40.0/24 | RIPE | Transtelecom Kazakhstan Network | MNT-TTCP | 2015-01-26 | Announced |
| 37.208.41.0/24 | RIPE | Transtelecom Kazakhstan Network | MNT-TTCP | 2015-06-03 | Announced |
| 37.208.42.0/24 | RIPE | Transtelecom Kazakhstan Network | MNT-TTCP | 2015-06-03 | Announced |
| 37.208.43.0/24 | RIPE | Transtelecom Kazakhstan Network | MNT-TTCP | 2015-06-03 | Announced |
| 37.208.44.0/24 | RIPE | Transtelecom Kazakhstan Network | MNT-TTCP | 2015-06-03 | Announced |
| 37.208.45.0/24 | RIPE | Transtelecom Kazakhstan Network | MNT-TTCP | 2015-06-03 | Announced |
| 37.208.46.0/24 | RIPE | Transtelecom Kazakhstan Network | MNT-TTCP | 2015-06-03 | Announced |
| 37.208.47.0/24 | RIPE | Transtelecom Kazakhstan Network | MNT-TTCP | 2015-06-03 | Announced |
| 45.88.90.0/24 | RIPE | — | INTERLIR-MNT | 2024-09-17 | Announced |
| 45.140.24.0/23 | RIPE | TTC network | KPV28-RIPE | 2024-06-13 | Announced |
| 45.140.24.0/24 | RIPE | TTC network | KPV28-RIPE | 2024-06-13 | Announced |
| 45.140.25.0/24 | RIPE | TTC network | KPV28-RIPE | 2024-06-13 | Announced |
| 45.144.175.0/24 | RIPE | — | MTF-MNT | 2024-10-04 | Announced |
| 80.71.150.0/24 | RIPE | — | IP-RIPE | 2026-03-26 | Announced |
| 82.115.44.0/22 | RIPE | TTC network | KPV28-RIPE | 2024-12-30 | Announced |
| 82.115.45.0/24 | RIPE | TTC network | KPV28-RIPE | 2024-12-30 | Announced |
| 82.115.46.0/24 | RIPE | TTC network | KPV28-RIPE | 2024-12-30 | Announced |
| 82.115.47.0/24 | RIPE | TTC network | KPV28-RIPE | 2024-12-30 | Announced |
| 87.255.202.0/23 | RIPE | — | BAKHYTZHAN_USEN | 2023-02-21 | Announced |
| 87.255.202.0/24 | RIPE | JSC Transtelecom | KPV28-RIPE | 2019-01-16 | Announced |
| 87.255.203.0/24 | RIPE | JSC Transtelecom | KPV28-RIPE | 2019-01-16 | Announced |
| 87.255.204.0/22 | RIPE | — | BAKHYTZHAN_USEN | 2023-02-21 | Announced |
| 87.255.204.0/24 | RIPE | JSC Transtelecom | KPV28-RIPE | 2019-01-16 | Announced |
| 87.255.205.0/24 | RIPE | JSC Transtelecom | KPV28-RIPE | 2019-01-16 | Announced |
| 87.255.206.0/24 | RIPE | JSC Transtelecom | KPV28-RIPE | 2019-01-16 | Announced |
| 87.255.207.0/24 | RIPE | JSC Transtelecom | KPV28-RIPE | 2019-01-16 | Announced |
| 87.255.208.0/20 | RIPE | — | BAKHYTZHAN_USEN | 2023-02-21 | Announced |
| 87.255.208.0/24 | RIPE | JSC Transtelecom | KPV28-RIPE | 2019-01-16 | Announced |
| 87.255.209.0/24 | RIPE | JSC Transtelecom | KPV28-RIPE | 2019-01-16 | Announced |
| 87.255.211.0/24 | RIPE | JSC Transtelecom | KPV28-RIPE | 2019-01-16 | Announced |
| 87.255.212.0/24 | RIPE | JSC Transtelecom | KPV28-RIPE | 2019-01-16 | Announced |
| 87.255.214.0/24 | RIPE | JSC Transtelecom | KPV28-RIPE | 2019-01-16 | Announced |
| 87.255.215.0/24 | RIPE | JSC Transtelecom | KPV28-RIPE | 2019-01-16 | Announced |
| 87.255.216.0/24 | RIPE | JSC Transtelecom | KPV28-RIPE | 2019-01-16 | Announced |
| 87.255.217.0/24 | RIPE | JSC Transtelecom | KPV28-RIPE | 2019-01-16 | Announced |
| 87.255.218.0/24 | RIPE | JSC Transtelecom | KPV28-RIPE | 2019-01-16 | Announced |
| 87.255.219.0/24 | RIPE | JSC Transtelecom | KPV28-RIPE | 2019-01-16 | Announced |
| 87.255.220.0/24 | RIPE | TTC_Astana | TTC_INET | 2019-03-20 | Announced |
| 87.255.221.0/24 | RIPE | — | TTC_INET | 2019-03-20 | Announced |
| 87.255.222.0/24 | RIPE | — | TTC_INET | 2019-03-20 | Announced |
| 87.255.223.0/24 | RIPE | — | TTC_INET | 2019-03-20 | Announced |
| 91.185.0.0/19 | RIPE | Transtelecom Kazakhstan Network | MNT-TTCP | 2012-01-26 | Announced |
| 91.185.1.0/24 | RIPE | TTC | MNT-TTCP | 2015-06-03 | Announced |
| 91.185.2.0/24 | RIPE | TTC | MNT-TTCP | 2015-06-03 | Announced |
| 91.185.3.0/24 | RIPE | TTC | MNT-TTCP | 2015-06-03 | Announced |
| 91.185.4.0/24 | RIPE | TTC | MNT-TTCP | 2015-06-03 | Announced |
| 91.185.5.0/24 | RIPE | TTC | MNT-TTCP | 2015-06-03 | Announced |
| 91.185.6.0/24 | RIPE | TTC | MNT-TTCP | 2015-06-03 | Announced |
| 91.185.7.0/24 | RIPE | TTC | MNT-TTCP | 2015-06-03 | Announced |
| 91.185.8.0/24 | RADB | Proxy-registered route object | MAINT-AS3491 | 2025-03-28 | Announced |
| 91.185.8.0/24 | RIPE | Kazakhstan Transtelecom network | MNT-TTCP | 2011-07-12 | Announced |
| 91.185.9.0/24 | RADB | Proxy-registered route object | MAINT-AS3491 | 2025-03-28 | Announced |
| 91.185.9.0/24 | RIPE | Transtelecom Kazakhstan Network | MNT-TTCP | 2007-01-16 | Announced |
| 91.185.10.0/24 | RADB | Proxy-registered route object | MAINT-AS3491 | 2025-03-28 | Announced |
| 91.185.10.0/24 | RIPE | Kazakhstan Transtelecom network | MNT-TTCP | 2011-07-14 | Announced |
| 91.185.12.0/24 | RADB | Proxy-registered route object | MAINT-AS3491 | 2025-03-28 | Announced |
| 91.185.12.0/24 | RIPE | Kazakhstan Transtelecom network | MNT-TTCP | 2011-07-12 | Announced |
| 91.185.13.0/24 | RADB | Proxy-registered route object | MAINT-AS3491 | 2025-03-28 | Announced |
| 91.185.13.0/24 | RIPE | Kazakhstan Transtelecom network | MNT-TTCP | 2011-07-14 | Announced |
| 91.185.14.0/24 | RADB | Proxy-registered route object | MAINT-AS3491 | 2025-03-28 | Announced |
| 91.185.14.0/24 | RIPE | Kazakhstan Transtelecom network | MNT-TTCP | 2011-07-14 | Announced |
| 91.185.15.0/24 | RIPE | KaTTC Astana Network | MNT-TTCP | 2007-07-26 | Announced |
| 91.185.16.0/24 | RADB | Proxy-registered route object | MAINT-AS3491 | 2025-03-28 | Announced |
| 91.185.16.0/24 | RIPE | Kazakhstan Transtelecom network | MNT-TTCP | 2011-07-12 | Announced |
| 91.185.17.0/24 | RIPE | ShonBi LLP Network | MNT-TTCP | 2007-11-27 | Announced |
| 91.185.18.0/24 | RIPE | KazTeleCom | MNT-TTCP | 2007-12-12 | Announced |
| 91.185.19.0/24 | RIPE | Transtelecom Kazakhstan | MNT-TTCP | 2007-12-13 | Announced |
| 91.185.20.0/24 | RIPE | TTC Network | MNT-TTCP | 2014-03-12 | Announced |
| 91.185.22.0/24 | RIPE | Transtelecom Kazakhstan | MNT-TTCP | 2008-01-25 | Announced |
| 91.185.23.0/24 | RIPE | Transtelecom Kazakhstan | MNT-TTCP | 2008-01-31 | Announced |
| 91.185.24.0/24 | RIPE | Transtelecom Kazakhstan | MNT-TTCP | 2008-02-19 | Announced |
| 91.185.25.0/24 | RIPE | for Netring Company | MNT-TTCP | 2008-03-31 | Announced |
| 91.185.26.0/24 | RIPE | Uralsk DSL Network | MNT-TTCP | 2008-03-31 | Announced |
| 91.185.27.0/24 | RIPE | Kazakhstan Transtelecom Astana DSL Pool | MNT-TTCP | 2008-04-14 | Announced |
| 91.185.28.0/24 | RIPE | for Instaphone Company | MNT-TTCP | 2008-04-22 | Announced |
| 91.185.29.0/24 | RIPE | JSC Transtelecom | MNT-TTCP | 2017-09-27 | Announced |
| 91.185.30.0/24 | RIPE | Domovoi Ltd | MNT-TTCP | 2008-06-25 | Announced |
| 91.185.31.0/24 | RIPE | TTC_IP | MNT-TTCP | 2022-02-17 | Announced |
| 91.212.166.0/24 | RIPE | — | IP-RIPE | 2026-03-18 | Announced |
| 91.246.80.0/20 | RIPE | — | BAKHYTZHAN_USEN | 2023-02-21 | Announced |
| 91.246.80.0/24 | RIPE | — | KPV28-RIPE | 2021-01-18 | Announced |
| 91.246.81.0/24 | RIPE | — | KPV28-RIPE | 2021-01-18 | Announced |
| 91.246.82.0/24 | RIPE | — | KPV28-RIPE | 2021-02-15 | Announced |
| 91.246.83.0/24 | RIPE | TTC_pool_for_Corp_customers | KPV28-RIPE | 2021-02-24 | Announced |
| 91.246.84.0/24 | RIPE | TTC_pool_for_Corp_customers | KPV28-RIPE | 2021-02-25 | Announced |
| 91.246.85.0/24 | RIPE | — | KPV28-RIPE | 2021-03-25 | Announced |
| 91.246.86.0/24 | RIPE | — | KPV28-RIPE | 2021-04-16 | Announced |
| 91.246.87.0/24 | RIPE | — | KPV28-RIPE | 2021-04-28 | Announced |
| 91.246.88.0/24 | RIPE | — | KPV28-RIPE | 2021-04-28 | Announced |
| 91.246.89.0/24 | RIPE | — | KPV28-RIPE | 2021-05-08 | Announced |
| 91.246.90.0/24 | RIPE | — | KPV28-RIPE | 2021-05-25 | Announced |
| 91.246.91.0/24 | RIPE | — | KPV28-RIPE | 2021-06-09 | Announced |
| 91.246.92.0/24 | RIPE | — | KPV28-RIPE | 2021-06-15 | Announced |
| 91.246.93.0/24 | RIPE | — | KPV28-RIPE | 2021-06-18 | Announced |
| 91.246.94.0/24 | RIPE | — | KPV28-RIPE | 2021-08-31 | Announced |
| 91.246.95.0/24 | RIPE | — | BAKHYTZHAN_USEN | 2022-03-03 | Announced |
| 91.246.96.0/21 | RIPE | — | BAKHYTZHAN_USEN | 2023-02-21 | Announced |
| 91.246.96.0/24 | RIPE | — | MNT-TTCP | 2020-06-29 | Announced |
| 91.246.97.0/24 | RIPE | — | MNT-TTCP | 2020-07-01 | Announced |
| 91.246.98.0/24 | RIPE | — | MNT-TTCP | 2020-07-03 | Announced |
| 91.246.99.0/24 | RIPE | — | KPV28-RIPE | 2020-07-03 | Announced |
| 91.246.100.0/24 | RIPE | — | KPV28-RIPE | 2024-04-03 | Announced |
| 91.246.101.0/24 | RIPE | — | KPV28-RIPE | 2024-04-03 | Announced |
| 91.246.102.0/24 | RIPE | Nur-Sultan prefix for Customers | KPV28-RIPE | 2020-10-30 | Announced |
| 91.246.103.0/24 | RIPE | Almaty Customers Network | KPV28-RIPE | 2020-12-02 | Announced |
| 94.141.224.0/20 | RIPE | — | BAKHYTZHAN_USEN | 2023-02-21 | Announced |
| 94.141.224.0/24 | RIPE | — | MNT-TTCP | 2020-01-06 | Announced |
| 94.141.225.0/24 | RIPE | — | MNT-TTCP | 2020-01-06 | Announced |
| 94.141.226.0/24 | RIPE | — | MNT-TTCP | 2020-01-06 | Announced |
| 94.141.227.0/24 | RIPE | — | MNT-TTCP | 2020-01-06 | Announced |
| 94.141.228.0/24 | RIPE | — | MNT-TTCP | 2020-01-06 | Announced |
| 94.141.229.0/24 | RIPE | — | MNT-TTCP | 2020-01-06 | Announced |
| 94.141.230.0/24 | RIPE | — | MNT-TTCP | 2020-01-06 | Announced |
| 94.141.231.0/24 | RIPE | — | MNT-TTCP | 2020-01-06 | Announced |
| 94.141.232.0/24 | RIPE | — | MNT-TTCP | 2020-01-06 | Announced |
| 94.141.233.0/24 | RIPE | — | MNT-TTCP | 2020-01-06 | Announced |
| 94.141.234.0/24 | RIPE | — | MNT-TTCP | 2020-01-06 | Announced |
| 94.141.235.0/24 | RIPE | — | MNT-TTCP | 2020-01-06 | Announced |
| 94.141.236.0/24 | RIPE | — | MNT-TTCP | 2020-01-06 | Announced |
| 94.141.237.0/24 | RIPE | — | MNT-TTCP | 2020-01-06 | Announced |
| 94.141.238.0/24 | RIPE | — | MNT-TTCP | 2020-01-06 | Announced |
| 94.141.239.0/24 | RIPE | — | MNT-TTCP | 2020-01-06 | Announced |
| 94.141.240.0/22 | RIPE | — | BAKHYTZHAN_USEN | 2023-02-21 | Announced |
| 94.141.240.0/24 | RIPE | TTC_SNP | TTC_INET | 2019-08-13 | Announced |
| 94.141.241.0/24 | RIPE | TTC_SNP | TTC_INET | 2019-08-13 | Announced |
| 94.141.242.0/24 | RIPE | TTC_SNP | TTC_INET | 2019-08-13 | Announced |
| 94.141.243.0/24 | RIPE | TTC_SNP | TTC_INET | 2019-08-13 | Announced |
| 94.141.248.0/22 | RIPE | — | BAKHYTZHAN_USEN | 2023-02-21 | Announced |
| 94.141.248.0/24 | RIPE | TTC customers | MNT-TTCP | 2020-03-20 | Announced |
| 94.141.249.0/24 | RIPE | — | MNT-TTCP | 2020-01-06 | Announced |
| 94.141.250.0/24 | RIPE | — | MNT-TTCP | 2020-01-06 | Announced |
| 94.141.251.0/24 | RIPE | — | MNT-TTCP | 2020-01-06 | Announced |
| 146.19.255.0/24 | RIPE | TTC network | KPV28-RIPE | 2024-06-13 | Announced |
| 170.168.33.0/24 | RIPE | — | IP-RIPE | 2025-08-12 | Announced |
| 170.168.34.0/24 | RIPE | — | IP-RIPE | 2025-08-13 | Announced |
| 170.168.100.0/24 | RIPE | — | IP-RIPE | 2025-09-24 | Announced |
| 170.168.101.0/24 | RIPE | — | IP-RIPE | 2025-09-24 | Announced |
| 170.168.192.0/24 | RIPE | — | IP-RIPE | 2026-09-28 | Announced |
| 176.98.224.0/20 | RIPE | — | BAKHYTZHAN_USEN | 2023-02-21 | Announced |
| 176.98.224.0/24 | RIPE | — | MNT-TTCP | 2020-01-08 | Announced |
| 176.98.225.0/24 | RIPE | — | MNT-TTCP | 2020-01-08 | Announced |
| 176.98.226.0/24 | RIPE | — | MNT-TTCP | 2020-01-08 | Announced |
| 176.98.227.0/24 | RIPE | — | KPV28-RIPE | 2021-09-08 | Announced |
| 176.98.228.0/24 | RIPE | — | BAKHYTZHAN_USEN | 2021-09-13 | Announced |
| 176.98.229.0/24 | RIPE | — | KPV28-RIPE | 2021-09-29 | Announced |
| 176.98.230.0/24 | RIPE | — | BAKHYTZHAN_USEN | 2021-10-25 | Announced |
| 176.98.231.0/24 | RIPE | — | BAKHYTZHAN_USEN | 2021-10-25 | Announced |
| 176.98.232.0/24 | RIPE | — | KPV28-RIPE | 2024-04-03 | Announced |
| 176.98.233.0/24 | RIPE | — | KPV28-RIPE | 2024-04-03 | Announced |
| 176.98.234.0/24 | RIPE | — | BAKHYTZHAN_USEN | 2022-01-11 | Announced |
| 176.98.235.0/24 | RIPE | — | KPV28-RIPE | 2022-01-26 | Announced |
| 176.98.236.0/24 | RIPE | — | BAKHYTZHAN_USEN | 2022-01-25 | Announced |
| 176.98.238.0/24 | RIPE | — | KPV28-RIPE | 2022-01-26 | Announced |
| 176.98.239.0/24 | RIPE | — | KPV28-RIPE | 2022-01-26 | Announced |
| 176.98.240.0/22 | RIPE | TTC ip | KPV28-RIPE | 2019-01-16 | Announced |
| 176.98.240.0/24 | RIPE | — | MNT-TTCP | 2020-04-16 | Announced |
| 176.100.42.0/24 | RIPE | — | IP-RIPE | 2026-03-18 | Announced |
| 178.22.168.0/21 | RADB | Proxy-registered route object | MAINT-AS3491 | 2025-03-28 | Announced |
| 178.22.168.0/21 | RIPE | Transtelecom Kazakhstan Network | MNT-TTCP | 2011-05-19 | Announced |
| 178.22.168.0/24 | RIPE | Transtelecom Astana Network | MNT-TTCP | 2011-05-19 | Announced |
| 178.22.169.0/24 | RIPE | Transtelecom Astana Network | MNT-TTCP | 2011-05-19 | Announced |
| 178.22.170.0/24 | RIPE | Transtelecom Astana DSL Network | MNT-TTCP | 2011-05-19 | Announced |
| 178.22.171.0/24 | RIPE | Transtelecom Astana DSL Network | MNT-TTCP | 2011-09-22 | Announced |
| 178.22.172.0/24 | RIPE | Transtelecom Astana DSL Network | MNT-TTCP | 2011-05-19 | Announced |
| 178.22.173.0/24 | RIPE | Transtelecom Uralsk Network | MNT-TTCP | 2011-05-19 | Announced |
| 178.22.174.0/24 | RIPE | Transtelecom Almaty DSL Network | MNT-TTCP | 2011-05-19 | Announced |
| 178.22.175.0/24 | RIPE | Transtelecom Karaganda DSL Network | MNT-TTCP | 2011-05-19 | Announced |
| 185.187.17.0/24 | RIPE | TTC network | KPV28-RIPE | 2024-06-13 | Announced |
| 193.104.253.0/24 | RIPE | TTC network | KPV28-RIPE | 2019-01-16 | Announced |
| 193.111.175.0/24 | RIPE | TTC network | KPV28-RIPE | 2024-06-13 | Announced |
| 193.124.93.0/24 | RIPE | — | INTERLIR-MNT | 2026-04-09 | Announced |
| 193.124.204.0/24 | RIPE | — | MTF-MNT | 2025-01-27 | Announced |
Showing 200 of 213.
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS41798 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-TRANSKZ | PeeringDB | Declared by the operator as its own set |
AS-10099 | RADB | Lists AS41798 as a direct member |
AS-BTN-CUSTOMERS | RADB | Lists AS41798 as a direct member |
AS-CIBERTELPEER | RIPE | Lists AS41798 as a direct member |
AS-CN | RADB | Lists AS41798 as a direct member |
AS-CN2 | APNIC | Lists AS41798 as a direct member |
AS-CN2 | RADB | Lists AS41798 as a direct member |
AS-DALANET-PEERS | RIPE | Lists AS41798 as a direct member |
AS-EMIX | RADB | Lists AS41798 as a direct member |
AS-HURRICANE | RADB | Lists AS41798 as a direct member |
AS-HURRICANEV6 | RADB | Lists AS41798 as a direct member |
AS-INDRIK | RIPE | Lists AS41798 as a direct member |
AS-KAZEXCHANGE | RIPE | Lists AS41798 as a direct member |
AS-KAZGOV-IX-RS | RIPE | Lists AS41798 as a direct member |
AS-KAZNIX-PEER | RIPE | Lists AS41798 as a direct member |
AS-KDP-RUSSIA | RIPE | Lists AS41798 as a direct member |
AS-KTCPEERS | RIPE | Lists AS41798 as a direct member |
AS-MTU | RIPE | Lists AS41798 as a direct member |
AS-MTU2 | RIPE | Lists AS41798 as a direct member |
AS-PS-PEERING | RIPE | Lists AS41798 as a direct member |
AS-RETN-ACTUAL-V4 | RIPE | Lists AS41798 as a direct member |
AS-RETN-ACTUAL-V6 | RIPE | Lists AS41798 as a direct member |
AS-SAIMANETPEERS-1 | RIPE | Lists AS41798 as a direct member |
AS-SET_TNSPLUS | RIPE | Lists AS41798 as a direct member |
AS-TRANSKZ | RIPE | Lists AS41798 as a direct member |
AS-TRANSKZ-IPV6 | RIPE | Lists AS41798 as a direct member |
AS-UL-COM-MEDIA | RIPE | Lists AS41798 as a direct member |
AS3491:AS-CUSTOMERS-EU | RADB | Lists AS41798 as a direct member |
AS41194:AS-RASCOM | RIPE | Lists AS41798 as a direct member |
AS58453:AS-ASIAASCUST | APNIC | Lists AS41798 as a direct member |
AS58453:AS-ASIAASCUST | RADB | Lists AS41798 as a direct member |
AS58453:AS-ASIATEST | APNIC | Lists AS41798 as a direct member |
AS58453:AS-ASIATEST2 | APNIC | Lists AS41798 as a direct member |
AS63529:AS-63529-AS-IMPORT-AS23764 | APNIC | Lists AS41798 as a direct member |
RPKI from rpki-client, validated 2026-10-12 12:10 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-12. Cross-check on bgp.he.net.