asn.dev

Routing security

AS205673 UATEL

Unclassified RIPE Cable/DSL/ISP

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

Announcements

What this network originates

4 observed

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

PrefixRPKIIRRVantage points
176.39.96.0/20RPKI validIRR58
185.210.84.0/22RPKI validIRR58
185.235.132.0/22RPKI validIRR58
185.244.168.0/22RPKI validIRR58

RPKI · ROAs

Route origin authorisations

5 ROAs

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

PrefixMax lengthTrust anchor
176.39.96.0/20/21RIPENCC
176.39.96.0/22/23RIPENCC
185.210.84.0/22/23RIPENCC
185.235.132.0/22/23RIPENCC
185.244.168.0/22/23RIPENCC

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

26 objects · 22 not announced

Route objects naming AS205673 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
176.39.96.0/21RIPE—LANET-MNT2025-09-02Not announced
176.39.96.0/22RIPE—LANET-NETOPS-MNT2025-02-25Not announced
176.39.96.0/23RIPE—LANET-NETOPS-MNT2025-02-25Not announced
176.39.98.0/23RIPE—LANET-NETOPS-MNT2025-02-25Not announced
176.39.104.0/21RIPE—LANET-MNT2025-09-02Not announced
185.210.84.0/23RIPEISP UATELUA-UATEL-1-MNT2020-07-22Not announced
185.210.84.0/24RIPEISP UATELUA-UATEL-1-MNT2020-07-22Not announced
185.210.85.0/24RIPEISP UATELUA-UATEL-1-MNT2020-07-22Not announced
185.210.86.0/23RIPEISP UATELUA-UATEL-1-MNT2020-07-22Not announced
185.210.86.0/24RIPEISP UATELUA-UATEL-1-MNT2020-07-22Not announced
185.210.87.0/24RIPEISP UATELUA-UATEL-1-MNT2020-07-22Not announced
185.235.132.0/23RIPEISP UATELUA-UATEL-1-MNT2020-07-22Not announced
185.235.132.0/24RIPEISP UATELUA-UATEL-1-MNT2020-07-22Not announced
185.235.133.0/24RIPEISP UATELUA-UATEL-1-MNT2020-07-22Not announced
185.235.134.0/23RIPEISP UATELUA-UATEL-1-MNT2020-07-22Not announced
185.235.134.0/24RIPEISP UATELUA-UATEL-1-MNT2020-07-22Not announced
185.235.135.0/24RIPEF.O.C.S.UA-UATEL-1-MNT2020-10-20Not announced
185.244.168.0/23RIPE—UA-BELWEST-1-MNT2020-07-22Not announced
185.244.168.0/24RIPE—UA-BELWEST-1-MNT2020-07-22Not announced
185.244.169.0/24RIPE—UA-BELWEST-1-MNT2020-07-22Not announced
185.244.170.0/23RIPE—UA-BELWEST-1-MNT2020-07-22Not announced
185.244.171.0/24RIPE—UA-BELWEST-1-MNT2020-07-22Not announced
176.39.96.0/20RIPE—LANET-MNT2025-09-02Announced
185.210.84.0/22RIPEISP UATELUA-UATEL-1-MNT2017-06-27Announced
185.235.132.0/22RIPEISP UATELUA-UATEL-1-MNT2019-12-18Announced
185.244.168.0/22RIPE—UA-BELWEST-1-MNT2020-03-28Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-LANETUAPeeringDBDeclared by the operator as its own set
AS-HURRICANERADBLists AS205673 as a direct member
AS-RETN-ACTUAL-V4RIPELists AS205673 as a direct member
AS-TRANSROUTE-SPECRIPELists AS205673 as a direct member
AS-UATELRIPELists AS205673 as a direct member

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