asn.dev

Routing security

AS201118 INTELCOM

Unclassified RIPE

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

Announcements

What this network originates

3 observed

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

PrefixRPKIIRRVantage points
185.85.120.0/24RPKI validIRR53
185.85.121.0/24RPKI validIRR53
185.85.123.0/24RPKI validIRR53

RPKI · ROAs

Route origin authorisations

3 ROAs

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

PrefixMax lengthTrust anchor
185.85.120.0/24/24RIPENCC
185.85.121.0/24/24RIPENCC
185.85.123.0/24/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

3 objects · 0 not announced

Route objects naming AS201118 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
185.85.120.0/24RIPE—INTELCOM2020-12-18Announced
185.85.121.0/24RIPE—INTELCOM2017-05-15Announced
185.85.123.0/24RIPE—INTELCOM2024-04-02Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-HURRICANERADBLists AS201118 as a direct member
AS-INTELCOMGROUPRIPELists AS201118 as a direct member
AS-RETN-ACTUAL-V4RIPELists AS201118 as a direct member
AS-UGORIPELists AS201118 as a direct member

RPKI from rpki-client, validated 2026-10-12 12:10 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-12. Cross-check on bgp.he.net.