Routing security
AS25549 AVANTEL-AS
Unclassified APNIC
Announcements
What this network originates
Every prefix observed with AS25549 as its origin, checked against RPKI and the IRR. Problems sort first.
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS25549 may originate these prefixes, up to the maximum length shown.
No ROA names this AS as an authorised origin.
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 AS25549 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 |
|---|---|---|---|---|---|
| 46.229.64.0/22 | RIPE | AVANTEL. Banraul metropolitan network | AVANTEL-MNT | 2012-07-19 | Not announced |
| 46.229.74.0/24 | RIPE | JSC Avantel. Tomsk network | AVANTEL-MNT | 2015-03-12 | Not announced |
| 46.229.75.0/24 | RIPE | JSC Avantel. Tomsk network | AVANTEL-MNT | 2015-03-12 | Not announced |
| 46.229.78.0/23 | RIPE | JSC Avantel. Krasnoyarsk network | AVANTEL-MNT | 2011-12-12 | Not announced |
| 46.229.78.0/24 | RIPE | Krasnoyarsk metropolitan network | AVANTEL-MNT | 2020-06-09 | Not announced |
| 80.69.176.0/24 | RIPE | RU-AVANTEL-MT-SPEC-03 | AVANTEL-MNT | 2015-06-17 | Not announced |
| 80.69.177.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Not announced |
| 80.69.178.0/24 | RIPE | RU-AVANTEL-MT-SPEC-01 | AVANTEL-MNT | 2015-06-15 | Not announced |
| 80.69.181.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Not announced |
| 80.69.182.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Not announced |
| 80.69.183.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Not announced |
| 91.201.72.0/22 | RADB | Proxy-registered route object | MAINT-AS3491 | 2025-03-28 | Not announced |
| 93.91.160.0/20 | RIPE | JSC Avantel. LIR preffix | AVANTEL-MNT | 2008-06-24 | Not announced |
| 93.91.164.0/24 | RIPE | — | AVANTEL-MNT | 2020-12-10 | Not announced |
| 93.91.170.0/24 | RIPE | — | MAGTEL-MNT | 2020-03-24 | Not announced |
| 93.91.172.0/23 | RIPE | Avantel. Barnaul metropolitan network | AVANTEL-MNT | 2014-01-22 | Not announced |
| 95.170.128.0/19 | RIPE | RU-AVANTEL-20090204 | AVANTEL-MNT | 2009-10-22 | Not announced |
| 95.170.146.0/24 | RIPE | JSC Avantel. Novosibirsk network | AVANTEL-MNT | 2009-09-17 | Not announced |
| 95.170.150.0/23 | RIPE | JSC Avantel. Novosibirsk network | MAGTEL-MNT | 2017-07-12 | Not announced |
| 95.181.128.0/22 | RIPE | Avantel. Barnaul metropolitan network | AVANTEL-MNT | 2015-06-30 | Not announced |
| 109.202.8.0/22 | RIPE | Severen-Telecom. Banraul metropolitan network | AVANTEL-MNT | 2010-06-01 | Not announced |
| 195.49.168.0/24 | RIPE | — | AVANTEL-MNT | 2019-06-06 | Not announced |
| 195.49.169.0/24 | RIPE | — | MAGTEL-MNT | 2019-06-06 | Not announced |
| 212.17.1.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Not announced |
| 212.17.2.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Not announced |
| 212.17.3.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Not announced |
| 212.17.4.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Not announced |
| 212.17.5.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Not announced |
| 212.17.6.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Not announced |
| 212.17.7.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Not announced |
| 212.17.8.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Not announced |
| 212.17.9.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Not announced |
| 212.17.10.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Not announced |
| 212.17.11.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Not announced |
| 212.17.12.0/24 | RIPE | RU-AVANTEL-MT-SPEC | AVANTEL-MNT | 2024-09-30 | Not announced |
| 212.17.13.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Not announced |
| 212.17.14.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Not announced |
| 212.17.16.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Not announced |
| 212.17.17.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Not announced |
| 212.17.18.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Not announced |
| 212.17.20.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Not announced |
| 212.17.21.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Not announced |
| 212.17.22.0/24 | RIPE | RU-AVANTEL-MT-SPEC | AVANTEL-MNT | 2024-09-30 | Not announced |
| 212.17.23.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Not announced |
| 212.17.26.0/24 | RIPE | RU-AVANTEL-MT-SPEC | AVANTEL-MNT | 2024-09-30 | Not announced |
| 212.17.27.0/24 | RIPE | RU-AVANTEL-MT-SPEC | AVANTEL-MNT | 2024-09-30 | Not announced |
| 212.17.28.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Not announced |
| 212.17.29.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Not announced |
| 212.17.30.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Not announced |
| 212.17.31.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Not announced |
| 2a00:1730:fffe::/48 | RIPE | Mirograd IPv6 | AVANTEL-MNT | 2015-02-19 | Not announced |
| 46.229.68.0/24 | RIPE | — | AVANTEL-MNT | 2024-09-13 | Announced |
| 46.229.69.0/24 | RIPE | — | AVANTEL-MNT | 2017-12-05 | Announced |
| 46.229.70.0/24 | RIPE | — | AVANTEL-MNT | 2018-01-18 | Announced |
| 46.229.71.0/24 | RIPE | — | AVANTEL-MNT | 2024-09-13 | Announced |
| 46.229.74.0/23 | RIPE | JSC Avantel. Tomsk network | AVANTEL-MNT | 2015-03-12 | Announced |
| 46.229.76.0/23 | RIPE | JSC Avantel. Tomsk network | AVANTEL-MNT | 2014-04-24 | Announced |
| 80.69.176.0/20 | RIPE | RU-AVANTEL-BLOCK-2 | AVANTEL-MNT | 2019-02-21 | Announced |
| 80.69.179.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Announced |
| 80.69.180.0/24 | RIPE | MT-AVA SPEC1 | MAGTEL-MNT | 2015-02-24 | Announced |
| 80.69.184.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Announced |
| 80.69.185.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Announced |
| 80.69.186.0/24 | RIPE | — | AVANTEL-MNT | 2026-03-11 | Announced |
| 80.69.191.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Announced |
| 82.117.64.0/21 | RIPE | — | AVANTEL-MNT | 2017-03-06 | Announced |
| 82.117.72.0/22 | RIPE | — | AVANTEL-MNT | 2018-06-22 | Announced |
| 82.117.76.0/24 | RIPE | — | AVANTEL-MNT | 2017-03-22 | Announced |
| 82.117.77.0/24 | RIPE | — | AVANTEL-MNT | 2017-03-22 | Announced |
| 84.237.65.0/24 | RIPE | — | CT-C-MNT | 2025-06-28 | Announced |
| 84.237.90.0/24 | RIPE | — | CT-C-MNT | 2025-06-28 | Announced |
| 84.237.91.0/24 | RIPE | BrSPSL thru Avantel | CT-C-MNT | 2025-06-28 | Announced |
| 91.192.172.0/22 | RADB | Proxy-registered route object | MAINT-AS3491 | 2025-03-28 | Announced |
| 91.192.172.0/22 | RIPE | CJSC Avantel | AVANTEL-MNT | 2008-11-12 | Announced |
| 91.192.172.0/24 | RIPE | — | AVANTEL-MNT | 2026-03-11 | Announced |
| 91.201.72.0/23 | RIPE | JSC Avantel | CONNECTA-MNT | 2007-12-05 | Announced |
| 91.201.74.0/24 | RIPE | JSC Avantel | CONNECTA-MNT | 2007-12-05 | Announced |
| 91.201.75.0/24 | RIPE | JSC Avantel | CONNECTA-MNT | 2007-12-05 | Announced |
| 93.91.160.0/22 | RIPE | JSC Avantel. Novosibirsk network | AVANTEL-MNT | 2008-06-24 | Announced |
| 93.91.160.0/24 | RIPE | — | AVANTEL-MNT | 2026-03-11 | Announced |
| 93.91.161.0/24 | RIPE | — | AVANTEL-MNT | 2026-03-11 | Announced |
| 93.91.165.0/24 | RIPE | ELECARD-NET | AVANTEL-MNT | 2008-11-27 | Announced |
| 93.91.166.0/24 | RIPE | Avantel. Tomsk network | AVANTEL-MNT | 2015-10-02 | Announced |
| 93.91.167.0/24 | RIPE | AVANTEL-NOVOSIBIRSK-CUSTOMERS-3 | AVANTEL-MNT | 2024-09-12 | Announced |
| 93.91.168.0/23 | RIPE | JSC Avantel. Tomsk network | AVANTEL-MNT | 2008-06-24 | Announced |
| 93.91.174.0/23 | RIPE | Avantel Kemerovo metropolitan network | AVANTEL-MNT | 2015-11-27 | Announced |
| 95.170.128.0/22 | RIPE | JSC Avantel. Novosibirsk network | AVANTEL-MNT | 2009-07-16 | Announced |
| 95.170.132.0/22 | RIPE | JSC Avantel. Novosibirsk network | AVANTEL-MNT | 2009-04-29 | Announced |
| 95.170.132.0/24 | RIPE | — | AVANTEL-MNT | 2026-03-11 | Announced |
| 95.170.136.0/23 | RIPE | — | AVANTEL-MNT | 2020-09-22 | Announced |
| 95.170.138.0/24 | RIPE | Avantel. Tomsk network | AVANTEL-MNT | 2015-12-13 | Announced |
| 95.170.140.0/23 | RIPE | JSC Avantel. Tomsk network | AVANTEL-MNT | 2014-01-23 | Announced |
| 95.170.142.0/24 | RIPE | JSC Avantel. Tomsk network | AVANTEL-MNT | 2014-01-23 | Announced |
| 95.170.144.0/23 | RIPE | JSC Avantel. Tomsk network | AVANTEL-MNT | 2009-04-06 | Announced |
| 95.170.148.0/22 | RIPE | JSC Avantel. Novosibirsk network | AVANTEL-MNT | 2009-10-22 | Announced |
| 95.170.148.0/23 | RIPE | JSC Avantel. Novosibirsk network | MAGTEL-MNT | 2017-07-12 | Announced |
| 95.170.152.0/22 | RIPE | JSC Avantel. Novosibirsk network | AVANTEL-MNT | 2009-10-22 | Announced |
| 95.170.156.0/22 | RIPE | JSC Avantel. Tomsk network | AVANTEL-MNT | 2016-05-23 | Announced |
| 109.202.0.0/21 | RIPE | JSC Avantel. Novosibirsk network | AVANTEL-MNT | 2010-03-03 | Announced |
| 109.202.12.0/22 | RIPE | JSC Avantel. Tomsk network | AVANTEL-MNT | 2010-09-28 | Announced |
| 109.202.16.0/21 | RIPE | JSC Avantel. Novosibirsk network | AVANTEL-MNT | 2010-09-29 | Announced |
| 109.202.19.0/24 | RIPE | — | AVANTEL-MNT | 2026-03-11 | Announced |
| 109.202.24.0/21 | RIPE | JSC Avantel. Novosibirsk network | AVANTEL-MNT | 2012-05-29 | Announced |
| 195.49.168.0/22 | RIPE | — | AVANTEL-MNT | 2019-06-06 | Announced |
| 195.49.171.0/24 | RIPE | — | AVANTEL-MNT | 2026-03-11 | Announced |
| 195.60.244.0/22 | RIPE | Avantel network | AVANTEL-MNT | 2024-09-12 | Announced |
| 195.60.244.0/24 | RIPE | — | AVANTEL-MNT | 2026-03-11 | Announced |
| 195.60.247.0/24 | RIPE | — | AVANTEL-MNT | 2026-03-11 | Announced |
| 212.17.0.0/19 | RIPE | — | AVANTEL-MNT | 2024-06-21 | Announced |
| 212.17.0.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Announced |
| 212.17.15.0/24 | RIPE | — | AVANTEL-MNT | 2023-01-30 | Announced |
| 212.17.19.0/24 | RIPE | RU-AVANTEL-MT-SPEC | MAGTEL-MNT | 2015-06-17 | Announced |
| 217.29.80.0/20 | RIPE | JSC Avantel. Tomsk network | AVANTEL-MNT | 2016-05-04 | Announced |
| 2a00:1730::/32 | RIPE | AVANTEL IPv6 | AVANTEL-MNT | 2014-08-18 | Announced |
| 2a00:1730:fffd::/48 | RIPE | AVANTEL-TOMSK-NETWORK-IPv6 | AVANTEL-MNT | 2015-11-18 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS25549 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-AVANTEL | RIPE | Lists AS25549 as a direct member |
AS-BAIKAL-IX-PEERS | RIPE | Lists AS25549 as a direct member |
AS-BLOCK-SET | RIPE | Lists AS25549 as a direct member |
AS-BLOCKED-RU | RIPE | Lists AS25549 as a direct member |
AS-BTN-CUSTOMERS | RADB | Lists AS25549 as a direct member |
AS-CONNECTA | RIPE | Lists AS25549 as a direct member |
AS-HURRICANE | RADB | Lists AS25549 as a direct member |
AS-HURRICANEV6 | RADB | Lists AS25549 as a direct member |
AS-MF-MGSM | RIPE | Lists AS25549 as a direct member |
AS-RASCOM-AMSIX | RIPE | Lists AS25549 as a direct member |
AS-RETN-ACTUAL-V4 | RIPE | Lists AS25549 as a direct member |
AS-RETN-ACTUAL-V6 | RIPE | Lists AS25549 as a direct member |
AS-SIBNET | RIPE | Lists AS25549 as a direct member |
AS-SOVAM-V6 | RIPE | Lists AS25549 as a direct member |
AS-TSKIX | RIPE | Lists AS25549 as a direct member |
AS-ZSTTK-SET | RIPE | Lists AS25549 as a direct member |
AS202683:AS-ONEHOP | RIPE | Lists AS25549 as a direct member |
AS209141:AS-RUCUST | RADB | Lists AS25549 as a direct member |
AS3491:AS-CUSTOMERS-EU | RADB | Lists AS25549 as a direct member |
AS41194:AS-RASCOM | RIPE | Lists AS25549 as a direct member |
RPKI from rpki-client, validated 2026-10-14 18:17 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-14. Cross-check on bgp.he.net.