asn.dev

Routing security

AS42518 UNETCOM-AS

Unclassified RIPE Cable/DSL/ISP

RPKI valid 100% 12 of 12 announcements
RPKI invalid 0 none
No ROA 0 not covered by any ROA
IRR registered 100% 0 missing · 0 other origin
ROAs 8 authorising this AS

Announcements

What this network originates

12 observed

Every prefix observed with AS42518 as its origin, checked against RPKI and the IRR. Problems sort first.

PrefixRPKIIRRVantage points
91.192.188.0/22RPKI validIRR53
91.192.188.0/23RPKI validIRR10
91.192.190.0/23RPKI validIRR10
91.215.120.0/22RPKI validIRR53
91.215.120.0/23RPKI validIRR10
91.215.122.0/23RPKI validIRR10
146.120.64.0/20RPKI validIRR53
146.120.64.0/21RPKI validIRR10
146.120.72.0/21RPKI validIRR10
146.120.80.0/21RPKI validIRR53
146.120.80.0/22RPKI validIRR11
146.120.84.0/22RPKI validIRR10

RPKI · ROAs

Route origin authorisations

8 ROAs

Signed statements by address holders that AS42518 may originate these prefixes, up to the maximum length shown.

PrefixMax lengthTrust anchor
91.192.188.0/22/22RIPENCC
91.192.188.0/23/23RIPENCC
91.192.190.0/23/23RIPENCC
91.215.120.0/22/22RIPENCC
91.215.120.0/23/23RIPENCC
91.215.122.0/23/23RIPENCC
146.120.64.0/20/24RIPENCC
146.120.80.0/21/24RIPENCC

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

17 objects · 5 not announced

Route objects naming AS42518 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.

PrefixSourceDescriptionMaintainerChangedRouting
91.192.188.0/24RIPEUnet CommunicationMNT-UNETKOM2008-03-24Not announced
91.192.189.0/24RIPEUnet CommunicationMNT-UNETKOM2008-06-24Not announced
91.192.190.0/24RIPEUnet CommunicationMNT-UNETKOM2008-06-24Not announced
91.192.191.0/24RIPEUnet CommunicationMNT-UNETKOM2008-06-24Not announced
2001:67c:19f0::/48RIPE—RIPE-DB-MNT2025-09-03Not announced
91.192.188.0/22RIPEUnet CommunicationMNT-UNETKOM2007-05-25Announced
91.192.188.0/23RIPEUnet CommunicationMNT-UNETKOM2007-08-15Announced
91.192.190.0/23RIPEUnet CommunicationMNT-UNETKOM2007-08-15Announced
91.215.120.0/22RIPEUnet CommunicationMNT-UNETKOM2009-08-13Announced
91.215.120.0/23RIPEUnet CommunicationMNT-UNETKOM2009-08-13Announced
91.215.122.0/23RIPEUnet CommunicationMNT-UNETKOM2009-08-13Announced
146.120.64.0/20RIPE—RIPE-DB-MNT2026-05-22Announced
146.120.64.0/21RIPE—RIPE-DB-MNT2026-05-22Announced
146.120.72.0/21RIPE—RIPE-DB-MNT2026-05-22Announced
146.120.80.0/21RIPE—RIPE-DB-MNT2026-05-22Announced
146.120.80.0/22RIPE—RIPE-DB-MNT2026-05-22Announced
146.120.84.0/22RIPE—RIPE-DB-MNT2026-05-22Announced

IRR

AS-sets

The as-set is what upstreams expand to build this network's customer filter. Sets that list AS42518 directly show who expects to carry it.

AS-setWhereRelationship
AS-UNETCOMRUPeeringDBDeclared by the operator as its own set
AS-LUXTELECOMRIPELists AS42518 as a direct member
AS-PETERSTAR-NWRIPELists AS42518 as a direct member
AS-PPEERRIPELists AS42518 as a direct member
AS-RETN-ACTUAL-V4RIPELists AS42518 as a direct member
AS-ROSTELECOMRIPELists AS42518 as a direct member
AS-SILVERNETRIPELists AS42518 as a direct member
AS-TRANSROUTE-SPECRIPELists AS42518 as a direct member
AS-UNETCOMRURIPELists AS42518 as a direct member
AS41194:AS-RASCOMRIPELists AS42518 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.