Routing security
AS12722 RECONN
Hosting RIPE
RPKI valid
19%
6 of 31 announcements
RPKI invalid
1
dropped by validating networks
No ROA
24
not covered by any ROA
IRR registered
97%
1 missing · 0 other origin
ROAs
68
authorising this AS
Announcements
What this network originates
Every prefix observed with AS12722 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 212.16.80.0/24 | RPKI invalid | No IRR | 7 |
| 2a00:1f70::/32 | No ROA | IRR | 34 |
| 2a05:4800::/29 | No ROA | IRR | 34 |
| 46.22.48.0/20 | No ROA | IRR | 56 |
| 46.22.55.0/24 | No ROA | IRR covering | 5 |
| 46.22.56.0/24 | No ROA | IRR covering | 5 |
| 46.22.63.0/24 | No ROA | IRR | 56 |
| 78.142.236.0/23 | No ROA | IRR | 56 |
| 83.150.228.0/22 | No ROA | IRR | 56 |
| 84.54.16.0/22 | No ROA | IRR | 56 |
| 87.239.144.0/22 | No ROA | IRR | 56 |
| 87.239.148.0/24 | No ROA | IRR | 56 |
| 87.239.149.0/24 | No ROA | IRR | 56 |
| 87.239.150.0/24 | No ROA | IRR | 56 |
| 91.105.232.0/21 | No ROA | IRR | 56 |
| 91.224.126.0/23 | No ROA | IRR | 56 |
| 185.141.182.0/24 | No ROA | IRR | 54 |
| 185.141.183.0/24 | No ROA | IRR | 54 |
| 185.207.22.0/24 | No ROA | IRR | 54 |
| 188.64.168.0/21 | No ROA | IRR | 56 |
| 193.26.18.0/24 | No ROA | IRR | 56 |
| 195.209.32.0/19 | No ROA | IRR | 56 |
| 212.81.32.0/22 | No ROA | IRR | 56 |
| 213.166.88.0/22 | No ROA | IRR | 56 |
| 2001:67c:2824::/48 | No ROA | IRR | 34 |
| 2a02:c6c0::/32 | RPKI valid | IRR | 30 |
| 45.80.120.0/22 | RPKI valid | IRR | 56 |
| 83.171.212.0/22 | RPKI valid | IRR | 56 |
| 93.170.76.0/24 | RPKI valid | IRR | 52 |
| 95.47.161.0/24 | RPKI valid | IRR | 53 |
| 195.209.55.0/24 | RPKI valid | IRR | 52 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS12722 may originate these prefixes, up to the maximum length shown.
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 AS12722 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 |
|---|---|---|---|---|---|
| 2.59.48.0/24 | RIPE | — | IP-RIPE | 2019-06-17 | Not announced |
| 5.45.80.0/22 | RIPE | — | NETROCKS-MNT | 2026-06-15 | Not announced |
| 5.182.116.0/24 | RIPE | — | IP-RIPE | 2022-07-12 | Not announced |
| 31.222.240.0/24 | RIPE | — | IP-RIPE | 2024-01-21 | Not announced |
| 31.222.243.0/24 | RIPE | — | IP-RIPE | 2024-01-21 | Not announced |
| 37.221.80.0/24 | RIPE | — | IP-RIPE | 2019-07-22 | Not announced |
| 37.252.0.0/23 | RIPE | Netrocks LLC | netrocks.ru | RECONN-MNT | 2026-06-15 | Not announced |
| 38.180.66.0/23 | ARIN | Route Registered for Cogent Communications Customer - 3NT SOLUTIONS LLP | MNT-COGC | 2026-04-07 | Not announced |
| 38.180.66.0/23 | RADB | As an internet service provider (ISP), we offer IP transit and bandwidth services that are self-managed by our customers. As a result, we do not utilize this IP space ourselves. If you encounter any issues related to spam, fraud, phishing, DDoS, port scans, or other similar problems, please do not hesitate to reach out to us with the relevant information. Our abuse email is abuse@3nt.com | MAINT-3NT | 2026-03-24 | Not announced |
| 45.8.156.0/24 | RIPE | — | IP-RIPE | 2019-07-19 | Not announced |
| 45.10.109.0/24 | RIPE | — | IP-RIPE | 2019-11-07 | Not announced |
| 45.11.22.0/24 | RIPE | — | IP-RIPE | 2019-07-19 | Not announced |
| 45.11.212.0/24 | RIPE | — | IP-RIPE | 2022-07-12 | Not announced |
| 45.14.220.0/24 | RIPE | — | IP-RIPE | 2022-07-13 | Not announced |
| 45.14.221.0/24 | RIPE | — | IP-RIPE | 2022-07-12 | Not announced |
| 45.15.255.0/24 | RIPE | — | IP-RIPE | 2019-06-17 | Not announced |
| 45.85.64.0/24 | RIPE | — | IP-RIPE | 2019-06-24 | Not announced |
| 45.85.67.0/24 | RIPE | — | IP-RIPE | 2019-06-24 | Not announced |
| 45.86.3.0/24 | RIPE | — | IP-RIPE | 2019-07-19 | Not announced |
| 45.88.208.0/24 | RIPE | — | IP-RIPE | 2019-07-19 | Not announced |
| 45.88.211.0/24 | RIPE | — | IP-RIPE | 2019-07-19 | Not announced |
| 45.89.68.0/24 | RIPE | — | IP-RIPE | 2019-07-19 | Not announced |
| 45.89.71.0/24 | RIPE | — | IP-RIPE | 2019-07-19 | Not announced |
| 45.90.44.0/24 | RIPE | — | IP-RIPE | 2019-07-19 | Not announced |
| 45.90.47.0/24 | RIPE | — | IP-RIPE | 2019-07-19 | Not announced |
| 45.91.160.0/24 | RIPE | — | IP-RIPE | 2019-07-19 | Not announced |
| 45.128.130.0/23 | RIPE | — | IP-RIPE | 2019-07-19 | Not announced |
| 45.144.38.0/24 | RIPE | — | IP-RIPE | 2024-01-21 | Not announced |
| 45.145.3.0/24 | RIPE | — | IP-RIPE | 2019-10-24 | Not announced |
| 46.149.99.0/24 | RIPE | — | RECONN-MNT | 2020-06-10 | Not announced |
| 46.149.174.0/24 | RIPE | — | IP-RIPE | 2020-05-29 | Not announced |
| 46.150.248.0/24 | RIPE | — | IP-RIPE | 2025-11-18 | Not announced |
| 46.150.249.0/24 | RIPE | — | IP-RIPE | 2025-11-18 | Not announced |
| 85.8.187.0/24 | RIPE | — | IP-RIPE | 2019-06-25 | Not announced |
| 85.235.81.0/24 | RIPE | — | IP-RIPE | 2024-01-21 | Not announced |
| 87.239.144.0/21 | RIPE | Vincent Tech. throw RECONN | RECONN-MNT | 2015-05-12 | Not announced |
| 87.239.148.0/22 | RIPE | — | RECONN-MNT | 2020-06-10 | Not announced |
| 87.247.140.0/24 | RIPE | — | IP-RIPE | 2019-06-24 | Not announced |
| 91.193.180.0/22 | RIPE | — | NETROCKS-MNT | 2026-06-15 | Not announced |
| 91.224.126.0/24 | RIPE | — | RECONN-MNT | 2018-04-06 | Not announced |
| 94.158.188.0/24 | RIPE | — | IP-RIPE | 2019-06-17 | Not announced |
| 176.53.187.0/24 | RIPE | — | IP-RIPE | 2019-07-22 | Not announced |
| 176.56.35.0/24 | RIPE | — | IP-RIPE | 2024-01-21 | Not announced |
| 176.56.36.0/24 | RIPE | — | IP-RIPE | 2024-01-21 | Not announced |
| 176.103.82.0/24 | RIPE | — | IP-RIPE | 2025-11-18 | Not announced |
| 176.124.34.0/24 | RIPE | — | IP-RIPE | 2019-06-17 | Not announced |
| 185.4.64.0/22 | RIPE | Netrocks LLC | netrocks.ru | RECONN-MNT | 2026-06-15 | Not announced |
| 185.141.180.0/22 | RIPE | — | RECONN-MNT | 2026-03-13 | Not announced |
| 185.234.8.0/24 | RIPE | — | IP-RIPE | 2024-01-21 | Not announced |
| 188.64.140.0/24 | RIPE | — | IP-RIPE | 2024-01-21 | Not announced |
| 188.93.136.0/24 | RIPE | — | IP-RIPE | 2024-01-21 | Not announced |
| 192.109.97.0/24 | RIPE | — | IP-RIPE | 2024-01-21 | Not announced |
| 193.56.185.0/24 | RIPE | — | IP-RIPE | 2024-01-21 | Not announced |
| 193.160.211.0/24 | RIPE | — | IP-RIPE | 2024-01-21 | Not announced |
| 193.201.114.0/24 | RIPE | — | IP-RIPE | 2019-12-18 | Not announced |
| 194.32.124.0/24 | RIPE | — | IP-RIPE | 2020-05-29 | Not announced |
| 194.32.126.0/24 | RIPE | — | IP-RIPE | 2019-06-24 | Not announced |
| 194.32.240.0/24 | RIPE | — | IP-RIPE | 2019-06-24 | Not announced |
| 194.32.250.0/24 | RIPE | — | IP-RIPE | 2019-12-18 | Not announced |
| 194.34.250.0/24 | RIPE | — | IP-RIPE | 2022-07-13 | Not announced |
| 194.156.127.0/24 | RIPE | — | IP-RIPE | 2019-07-22 | Not announced |
| 195.69.148.0/24 | RIPE | — | IP-RIPE | 2024-01-21 | Not announced |
| 195.209.59.0/24 | RIPE | — | RECONN-MNT | 2024-03-04 | Not announced |
| 212.60.6.0/24 | RIPE | — | IP-RIPE | 2019-06-24 | Not announced |
| 212.107.24.0/24 | RIPE | — | IP-RIPE | 2019-06-24 | Not announced |
| 212.115.48.0/24 | RIPE | — | IP-RIPE | 2019-06-24 | Not announced |
| 212.115.50.0/24 | RIPE | — | IP-RIPE | 2019-08-06 | Not announced |
| 213.109.206.0/24 | RIPE | — | IP-RIPE | 2024-01-21 | Not announced |
| 213.139.231.0/24 | RIPE | — | IP-RIPE | 2019-07-22 | Not announced |
| 213.166.92.0/24 | RIPE | — | IP-RIPE | 2019-07-22 | Not announced |
| 213.166.95.0/24 | RIPE | — | IP-RIPE | 2019-06-24 | Not announced |
| 2a05:4800::/32 | RIPE | — | RECONN-MNT | 2026-10-01 | Not announced |
| 45.80.120.0/22 | RIPE | — | IP-RIPE | 2020-04-16 | Announced |
| 46.22.48.0/20 | RIPE | RECONN Operator Svyazi LLC | RECONN-MNT | 2015-11-09 | Announced |
| 46.22.63.0/24 | RIPE | — | RECONN-MNT | 2020-03-30 | Announced |
| 78.142.236.0/23 | RIPE | — | IP-RIPE | 2020-08-29 | Announced |
| 83.150.228.0/22 | RIPE | — | IP-RIPE | 2019-12-18 | Announced |
| 83.171.212.0/22 | RIPE | — | IP-RIPE | 2019-12-18 | Announced |
| 84.54.16.0/22 | RIPE | — | IP-RIPE | 2019-12-18 | Announced |
| 87.239.144.0/22 | RIPE | — | RECONN-MNT | 2020-06-10 | Announced |
| 87.239.148.0/24 | RIPE | — | RECONN-MNT | 2022-11-23 | Announced |
| 87.239.149.0/24 | RIPE | — | RECONN-MNT | 2022-11-23 | Announced |
| 87.239.150.0/24 | RIPE | — | RECONN-MNT | 2022-11-23 | Announced |
| 91.105.232.0/21 | RIPE | — | RECONN-MNT | 2020-09-28 | Announced |
| 91.224.126.0/23 | RIPE | reconn-global | RECONN-MNT | 2017-08-28 | Announced |
| 93.170.76.0/24 | RIPE | — | RIPE-DB-MNT | 2025-07-02 | Announced |
| 95.47.161.0/24 | RIPE | — | RIPE-DB-MNT | 2026-05-22 | Announced |
| 185.141.182.0/24 | RIPE | — | RECONN-MNT | 2026-05-27 | Announced |
| 185.141.183.0/24 | RIPE | — | RECONN-MNT | 2026-05-27 | Announced |
| 185.207.22.0/24 | RIPE | — | LIR-RU-SENTASERV-1-MNT | 2024-04-07 | Announced |
| 188.64.168.0/21 | RIPE | RECONN net 188 | RECONN-MNT | 2021-01-16 | Announced |
| 193.26.18.0/24 | RIPE | Belintermod throw RECONN | RECONN-MNT | 2021-04-15 | Announced |
| 195.209.32.0/19 | RIPE | RECONN network | RECONN-MNT | 2015-05-11 | Announced |
| 195.209.55.0/24 | RIPE | — | RECONN-MNT | 2018-02-20 | Announced |
| 212.81.32.0/22 | RIPE | — | IP-RIPE | 2020-04-16 | Announced |
| 213.166.88.0/22 | RIPE | — | IP-RIPE | 2019-12-18 | Announced |
| 2001:67c:2824::/48 | RADB | QRATOR via EMIX | MAINT-AS8966 | 2023-11-13 | Announced |
| 2001:67c:2824::/48 | RIPE | reconn-global-v6 | RECONN-MNT | 2017-08-28 | Announced |
| 2a00:1f70::/32 | RADB | QRATOR via EMIX | MAINT-AS8966 | 2023-11-13 | Announced |
| 2a00:1f70::/32 | RIPE | RECONN VSYS-1 Network | RECONN-MNT | 2021-03-29 | Announced |
| 2a02:c6c0::/32 | RADB | QRATOR via EMIX | MAINT-AS8966 | 2023-11-13 | Announced |
| 2a02:c6c0::/32 | RIPE | — | RECONN-MNT | 2018-07-30 | Announced |
| 2a05:4800::/29 | RADB | QRATOR via EMIX | MAINT-AS8966 | 2023-11-13 | Announced |
| 2a05:4800::/29 | RIPE | — | RECONN-MNT | 2017-06-19 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS12722 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-BLOCK-SET | RIPE | Lists AS12722 as a direct member |
AS-BLOCKED-RU | RIPE | Lists AS12722 as a direct member |
AS-DINET-V6 | RIPE | Lists AS12722 as a direct member |
AS-EMIX | RADB | Lists AS12722 as a direct member |
AS-HURRICANE | RADB | Lists AS12722 as a direct member |
AS-HURRICANEV6 | RADB | Lists AS12722 as a direct member |
AS-ICNET | RIPE | Lists AS12722 as a direct member |
AS-RECONN | RIPE | Lists AS12722 as a direct member |
AS-RECONN-IPV6 | RIPE | Lists AS12722 as a direct member |
AS-RECONN6 | RIPE | Lists AS12722 as a direct member |
AS-RETN-ACTUAL-V4 | RIPE | Lists AS12722 as a direct member |
AS-RUCENTER | RIPE | Lists AS12722 as a direct member |
AS209141:AS-RUCUST | RADB | Lists AS12722 as a direct member |
AS3491:AS-CUSTOMERS-EU | RADB | Lists AS12722 as a direct member |
AS41194:AS-RASCOM | RIPE | Lists AS12722 as a direct member |
RPKI from rpki-client, validated 2026-10-13 12:16 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-13. Cross-check on bgp.he.net.