Routing security
AS50326 IPTELECOM-AS
Residential RIPE Cable/DSL/ISP
Announcements
What this network originates
Every prefix observed with AS50326 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 45.158.176.0/22 | RPKI valid | IRR | 51 |
| 185.101.240.0/22 | RPKI valid | IRR | 51 |
| 185.101.243.0/24 | RPKI valid | IRR | 57 |
| 185.227.220.0/22 | RPKI valid | IRR | 51 |
| 195.191.28.0/23 | RPKI valid | IRR | 51 |
| 195.191.28.0/24 | RPKI valid | IRR | 18 |
| 195.191.29.0/24 | RPKI valid | IRR | 18 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS50326 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 45.158.176.0/22 | /24 | RIPENCC |
| 185.101.240.0/22 | /24 | RIPENCC |
| 185.227.220.0/22 | /24 | RIPENCC |
| 195.191.28.0/23 | /24 | RIPENCC |
| 2a0c:ce00::/29 | /29 | 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 AS50326 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 |
|---|---|---|---|---|---|
| 45.158.176.0/24 | RIPE | — | MNT-IPTELECOM | 2025-04-10 | Not announced |
| 45.158.177.0/24 | RIPE | — | MNT-IPTELECOM | 2025-04-10 | Not announced |
| 45.158.178.0/24 | RIPE | — | MNT-IPTELECOM | 2025-04-10 | Not announced |
| 45.158.179.0/24 | RIPE | — | MNT-IPTELECOM | 2025-04-10 | Not announced |
| 185.101.240.0/24 | RIPE | — | MNT-IPTELECOM | 2025-04-10 | Not announced |
| 185.101.241.0/24 | RIPE | — | MNT-IPTELECOM | 2025-04-10 | Not announced |
| 185.101.242.0/24 | RIPE | — | MNT-IPTELECOM | 2025-04-10 | Not announced |
| 185.227.220.0/24 | RIPE | — | MNT-IPTELECOM | 2025-04-10 | Not announced |
| 185.227.221.0/24 | RIPE | — | MNT-IPTELECOM | 2025-04-10 | Not announced |
| 185.227.222.0/24 | RIPE | — | MNT-IPTELECOM | 2025-04-10 | Not announced |
| 185.227.223.0/24 | RIPE | — | MNT-IPTELECOM | 2025-04-10 | Not announced |
| 2a0c:ce00::/29 | RIPE | — | MNT-IPTELECOM | 2017-10-25 | Not announced |
| 45.158.176.0/22 | RIPE | — | MNT-IPTELECOM | 2019-09-30 | Announced |
| 185.101.240.0/22 | RIPE | — | MNT-IPTELECOM | 2016-09-07 | Announced |
| 185.101.243.0/24 | RIPE | — | MNT-IPTELECOM | 2025-04-10 | Announced |
| 185.227.220.0/22 | RIPE | — | MNT-IPTELECOM | 2017-10-25 | Announced |
| 195.191.28.0/23 | RIPE | IPTelecom | MNT-IPTELECOM | 2016-09-12 | Announced |
| 195.191.28.0/24 | RIPE | IPTelecom | MNT-IPTELECOM | 2016-09-12 | Announced |
| 195.191.29.0/24 | RIPE | IPTelecom | MNT-IPTELECOM | 2016-09-12 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS50326 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-EUNIE | RIPE | Lists AS50326 as a direct member |
AS-GTTCUST | RIPE | Lists AS50326 as a direct member |
AS-JARMTELCO | ALTDB | Lists AS50326 as a direct member |
AS-SET-BSCCL | APNIC | Lists AS50326 as a direct member |
AS-SET-INEX-CONNECTED | RIPE | Lists AS50326 as a direct member |
AS-SET-INEX-RS | RIPE | Lists AS50326 as a direct member |
AS-TELSTRA-INTL-CUSTOMERS | RADB | Lists AS50326 as a direct member |
AS13335:AS-CUSTOMERS | ARIN | Lists AS50326 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.