Routing security
AS42065 ETELECOM-AS
Unclassified RIPE
RPKI valid
100%
33 of 33 announcements
RPKI invalid
0
none
No ROA
0
not covered by any ROA
IRR registered
100%
0 missing · 0 other origin
ROAs
36
authorising this AS
Announcements
What this network originates
Every prefix observed with AS42065 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 2a02:1e1::/32 | RPKI valid | IRR | 31 |
| 46.19.184.0/21 | RPKI valid | IRR | 53 |
| 77.239.224.0/19 | RPKI valid | IRR | 53 |
| 83.243.64.0/22 | RPKI valid | IRR | 53 |
| 83.243.68.0/24 | RPKI valid | IRR | 53 |
| 83.243.70.0/23 | RPKI valid | IRR | 53 |
| 91.108.0.0/22 | RPKI valid | IRR | 53 |
| 91.108.24.0/21 | RPKI valid | IRR | 53 |
| 91.108.32.0/23 | RPKI valid | IRR | 53 |
| 91.108.52.0/24 | RPKI valid | IRR | 53 |
| 92.62.48.0/20 | RPKI valid | IRR | 53 |
| 94.124.176.0/22 | RPKI valid | IRR | 53 |
| 94.229.96.0/20 | RPKI valid | IRR | 53 |
| 95.140.92.0/24 | RPKI valid | IRR | 53 |
| 95.140.94.0/24 | RPKI valid | IRR | 53 |
| 95.161.0.0/18 | RPKI valid | IRR | 53 |
| 95.161.88.0/22 | RPKI valid | IRR | 53 |
| 95.161.95.0/24 | RPKI valid | IRR | 53 |
| 95.161.96.0/23 | RPKI valid | IRR | 53 |
| 95.161.100.0/23 | RPKI valid | IRR | 53 |
| 95.161.102.0/23 | RPKI valid | IRR | 53 |
| 95.161.104.0/23 | RPKI valid | IRR | 53 |
| 95.161.125.0/24 | RPKI valid | IRR | 53 |
| 95.161.127.0/24 | RPKI valid | IRR | 53 |
| 185.26.72.0/24 | RPKI valid | IRR | 1 |
| 185.26.74.0/24 | RPKI valid | IRR | 53 |
| 185.51.60.0/22 | RPKI valid | IRR | 53 |
| 188.65.64.0/21 | RPKI valid | IRR | 53 |
| 193.218.140.0/22 | RPKI valid | IRR | 53 |
| 194.110.66.0/24 | RPKI valid | IRR | 53 |
| 212.232.64.0/20 | RPKI valid | IRR | 53 |
| 213.21.0.0/19 | RPKI valid | IRR | 53 |
| 213.21.48.0/20 | RPKI valid | IRR | 53 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS42065 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 46.19.184.0/21 | /21 | RIPENCC |
| 77.239.224.0/19 | /19 | RIPENCC |
| 83.243.64.0/22 | /22 | RIPENCC |
| 83.243.68.0/24 | /24 | RIPENCC |
| 83.243.70.0/23 | /23 | RIPENCC |
| 91.108.0.0/22 | /24 | RIPENCC |
| 91.108.24.0/21 | /24 | RIPENCC |
| 91.108.32.0/23 | /24 | RIPENCC |
| 91.108.52.0/24 | /24 | RIPENCC |
| 92.62.48.0/20 | /22 | RIPENCC |
| 94.124.176.0/22 | /23 | RIPENCC |
| 94.124.178.0/23 | /24 | RIPENCC |
| 94.229.96.0/20 | /20 | RIPENCC |
| 95.140.92.0/24 | /24 | RIPENCC |
| 95.140.94.0/24 | /24 | RIPENCC |
| 95.161.0.0/18 | /24 | RIPENCC |
| 95.161.88.0/22 | /24 | RIPENCC |
| 95.161.95.0/24 | /24 | RIPENCC |
| 95.161.96.0/23 | /24 | RIPENCC |
| 95.161.100.0/23 | /23 | RIPENCC |
| 95.161.102.0/23 | /24 | RIPENCC |
| 95.161.104.0/23 | /24 | RIPENCC |
| 95.161.124.0/24 | /24 | RIPENCC |
| 95.161.125.0/24 | /24 | RIPENCC |
| 95.161.127.0/24 | /24 | RIPENCC |
| 185.26.72.0/24 | /24 | RIPENCC |
| 185.26.74.0/24 | /24 | RIPENCC |
| 185.51.60.0/22 | /24 | RIPENCC |
| 188.65.64.0/21 | /21 | RIPENCC |
| 193.218.140.0/22 | /22 | RIPENCC |
| 194.110.66.0/24 | /24 | RIPENCC |
| 212.232.64.0/20 | /20 | RIPENCC |
| 213.21.0.0/19 | /19 | RIPENCC |
| 213.21.48.0/20 | /20 | RIPENCC |
| 2a00:11d8::/32 | /48 | RIPENCC |
| 2a02:1e1::/32 | /32 | RIPENCC |
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 AS42065 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 |
|---|---|---|---|---|---|
| 83.243.64.0/21 | RIPE | eTelecom Network | MNT-GLOBAL-NET | 2021-02-09 | Not announced |
| 83.243.64.0/24 | RIPE | Etelecom INfrastructure | ETELECOM-MNT | 2021-02-09 | Not announced |
| 83.243.65.0/24 | RIPE | Home Users Network 1 | ETELECOM-MNT | 2021-02-09 | Not announced |
| 83.243.66.0/24 | RIPE | SPB Primorskiy region customer | ETELECOM-MNT | 2021-02-09 | Not announced |
| 83.243.67.0/24 | RIPE | Home Users Network 2 | ETELECOM-MNT | 2021-02-09 | Not announced |
| 83.243.70.0/24 | RIPE | P2P St.Petersburg Network | ETELECOM-MNT | 2021-02-09 | Not announced |
| 83.243.71.0/24 | RIPE | eTelecom Management Network | ETELECOM-MNT | 2021-02-09 | Not announced |
| 91.108.0.0/24 | RIPE | — | MNT-AG-GLOBALNET-1 | 2022-11-01 | Not announced |
| 91.108.1.0/24 | RIPE | — | MNT-AG-GLOBALNET-1 | 2022-11-01 | Not announced |
| 91.108.2.0/24 | RIPE | Electronstroy | MNT-AG-GLOBALNET-1 | 2022-11-01 | Not announced |
| 91.108.3.0/24 | RIPE | — | MNT-AG-GLOBALNET-1 | 2022-11-01 | Not announced |
| 91.108.24.0/23 | RIPE | — | ETELECOM-MNT | 2021-02-09 | Not announced |
| 91.108.24.0/24 | RIPE | — | MNT-AG-GLOBALNET-1 | 2022-11-01 | Not announced |
| 91.108.25.0/24 | RIPE | — | MNT-AG-GLOBALNET-1 | 2022-11-01 | Not announced |
| 91.108.26.0/23 | RIPE | ETelecom_Customers | MNT-GLOBAL-NET | 2022-11-01 | Not announced |
| 91.108.26.0/24 | RIPE | — | MNT-GLOBAL-NET | 2022-11-01 | Not announced |
| 91.108.27.0/24 | RIPE | — | MNT-GLOBAL-NET | 2022-11-01 | Not announced |
| 91.108.28.0/22 | RIPE | — | MNT-GLOBAL-NET | 2016-12-16 | Not announced |
| 91.108.28.0/24 | RIPE | — | MNT-GLOBAL-NET | 2022-11-01 | Not announced |
| 91.108.29.0/24 | RIPE | — | MNT-GLOBAL-NET | 2022-11-01 | Not announced |
| 91.108.30.0/24 | RIPE | — | MNT-GLOBAL-NET | 2022-11-01 | Not announced |
| 91.108.31.0/24 | RIPE | — | MNT-GLOBAL-NET | 2022-11-01 | Not announced |
| 91.108.32.0/24 | RIPE | — | MNT-GLOBAL-NET | 2020-03-31 | Not announced |
| 91.108.33.0/24 | RIPE | — | MNT-GLOBAL-NET | 2018-07-10 | Not announced |
| 92.62.60.0/22 | RIPE | — | MNT-AG-GLOBALNET-1 | 2026-02-17 | Not announced |
| 94.124.176.0/23 | RIPE | ETelecom_Customers | MNT-AG-GLOBALNET-1 | 2023-06-30 | Not announced |
| 94.124.178.0/23 | RIPE | ETelecom_Customers | MNT-GLOBAL-NET | 2018-10-23 | Not announced |
| 94.124.178.0/24 | RIPE | — | MNT-GLOBAL-NET | 2022-11-01 | Not announced |
| 94.124.179.0/24 | RIPE | — | MNT-GLOBAL-NET | 2022-11-01 | Not announced |
| 95.161.88.0/24 | RIPE | — | MNT-AG-GLOBALNET-1 | 2022-11-01 | Not announced |
| 95.161.89.0/24 | RIPE | — | MNT-AG-GLOBALNET-1 | 2022-11-01 | Not announced |
| 95.161.90.0/24 | RIPE | — | MNT-AG-GLOBALNET-1 | 2022-11-01 | Not announced |
| 95.161.91.0/24 | RIPE | — | MNT-AG-GLOBALNET-1 | 2022-11-01 | Not announced |
| 95.161.96.0/24 | RIPE | — | MNT-GLOBAL-NET | 2019-12-10 | Not announced |
| 95.161.97.0/24 | RIPE | — | TIERA-MNT | 2020-04-15 | Not announced |
| 95.161.124.0/24 | RIPE | — | MNT-AG-GLOBALNET-1 | 2024-12-03 | Not announced |
| 109.239.140.0/24 | RIPE | Telegram Messenger LLP | MNT-TELEGRAM | 2018-04-16 | Not announced |
| 185.51.60.0/24 | RIPE | — | MNT-GLOBAL-NET | 2022-11-01 | Not announced |
| 185.51.61.0/24 | RIPE | — | MNT-GLOBAL-NET | 2022-11-01 | Not announced |
| 185.51.62.0/24 | RIPE | — | MNT-GLOBAL-NET | 2026-10-05 | Not announced |
| 185.51.63.0/24 | RIPE | — | MNT-GLOBAL-NET | 2026-10-05 | Not announced |
| 193.218.140.0/24 | RIPE | — | MNT-AG-GLOBALNET-1 | 2022-11-01 | Not announced |
| 193.218.141.0/24 | RIPE | — | MNT-AG-GLOBALNET-1 | 2022-11-01 | Not announced |
| 193.218.142.0/24 | RIPE | — | MNT-AG-GLOBALNET-1 | 2022-11-01 | Not announced |
| 193.218.143.0/24 | RIPE | — | MNT-AG-GLOBALNET-1 | 2022-11-01 | Not announced |
| 2a00:11d8::/32 | RIPE | — | MNT-AG-GLOBALNET-1 | 2024-12-03 | Not announced |
| 46.19.184.0/21 | RIPE | brand eTelecom | MNT-AG-GLOBALNET-1 | 2026-02-17 | Announced |
| 77.239.224.0/19 | RIPE | eTelecom | MNT-AG-GLOBALNET-1 | 2026-02-17 | Announced |
| 83.243.64.0/22 | RIPE | — | MNT-GLOBAL-NET | 2022-11-01 | Announced |
| 83.243.68.0/24 | RIPE | eTelecom Collocation Network | ETELECOM-MNT | 2021-02-09 | Announced |
| 83.243.70.0/23 | RIPE | — | MNT-AG-GLOBALNET-1 | 2022-11-03 | Announced |
| 91.108.0.0/22 | RIPE | eTelecom_NAT_NETWORK | MNT-GLOBAL-NET | 2021-02-09 | Announced |
| 91.108.24.0/21 | RIPE | — | MNT-AG-GLOBALNET-1 | 2022-11-01 | Announced |
| 91.108.32.0/23 | RIPE | — | MNT-AG-GLOBALNET-1 | 2022-11-07 | Announced |
| 91.108.52.0/24 | RIPE | — | MNT-GLOBAL-NET | 2022-01-24 | Announced |
| 92.62.48.0/20 | RIPE | — | MNT-AG-GLOBALNET-1 | 2026-02-17 | Announced |
| 94.124.176.0/22 | RIPE | ETelecom_Customers | MNT-AG-GLOBALNET-1 | 2024-12-17 | Announced |
| 94.229.96.0/20 | RIPE | — | MNT-AG-GLOBALNET-1 | 2026-02-17 | Announced |
| 95.140.92.0/24 | RIPE | — | MNT-GLOBAL-NET | 2022-08-19 | Announced |
| 95.140.94.0/24 | RIPE | Leti Campus Network | MNT-GLOBAL-NET | 2015-05-29 | Announced |
| 95.161.0.0/18 | RIPE | — | MNT-AG-GLOBALNET-1 | 2024-12-03 | Announced |
| 95.161.88.0/22 | RIPE | ETelecom Customers | MNT-AG-GLOBALNET-1 | 2021-01-21 | Announced |
| 95.161.95.0/24 | RIPE | — | MNT-AG-GLOBALNET-1 | 2024-12-16 | Announced |
| 95.161.96.0/23 | RIPE | — | MNT-AG-GLOBALNET-1 | 2022-11-07 | Announced |
| 95.161.100.0/23 | RIPE | — | MNT-AG-GLOBALNET-1 | 2026-02-17 | Announced |
| 95.161.102.0/23 | RIPE | Services | MNT-AG-GLOBALNET-1 | 2021-08-19 | Announced |
| 95.161.104.0/23 | RIPE | Office subnet | MNT-AG-GLOBALNET-1 | 2021-07-28 | Announced |
| 95.161.125.0/24 | RIPE | — | MNT-AG-GLOBALNET-1 | 2024-12-03 | Announced |
| 95.161.127.0/24 | RIPE | — | MNT-AG-GLOBALNET-1 | 2024-12-03 | Announced |
| 185.26.72.0/24 | RIPE | — | PEERING-MNT | 2022-06-29 | Announced |
| 185.26.74.0/24 | RIPE | — | MNT-AG-GLOBALNET-1 | 2022-07-15 | Announced |
| 185.51.60.0/22 | RIPE | GlobalNet Temporaly Network | MNT-GLOBAL-NET | 2026-10-05 | Announced |
| 188.65.64.0/21 | RIPE | — | MNT-AG-GLOBALNET-1 | 2026-02-17 | Announced |
| 193.218.140.0/22 | RIPE | Etelecom route object | ETELECOM-MNT | 2021-02-09 | Announced |
| 194.110.66.0/24 | RIPE | RU-SPB-YG | GUGL-MNT | 2023-06-23 | Announced |
| 212.232.64.0/20 | RIPE | — | MNT-AG-GLOBALNET-1 | 2026-02-17 | Announced |
| 213.21.0.0/19 | RIPE | — | MNT-AG-GLOBALNET-1 | 2026-02-17 | Announced |
| 213.21.48.0/20 | RIPE | — | MNT-AG-GLOBALNET-1 | 2026-02-17 | Announced |
| 2a02:1e1::/32 | RIPE | — | MNT-AG-GLOBALNET-1 | 2023-04-21 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS42065 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-BLOCK-SET | RIPE | Lists AS42065 as a direct member |
AS-BLOCKED-RU | RIPE | Lists AS42065 as a direct member |
AS-ETELECOM-2 | RIPE | Lists AS42065 as a direct member |
AS-EUT | RIPE | Lists AS42065 as a direct member |
AS-GLOBAL-IX | RIPE | Lists AS42065 as a direct member |
AS-GLOBAL-NET | RIPE | Lists AS42065 as a direct member |
AS34251:AS-RUFILE | RIPE | Lists AS42065 as a direct member |
RPKI from rpki-client, validated 2026-10-17 12:17 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, collected 2026-10-17. Cross-check on bgp.he.net.