asn.dev

Routing security

AS35063 TKCHOPIN-AS

Residential RIPE

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

Announcements

What this network originates

7 observed

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

PrefixRPKIIRRVantage points
2a03:9500::/32RPKI validIRR34
31.7.40.0/21RPKI validIRR51
46.29.144.0/21RPKI validIRR51
85.237.160.0/19RPKI validIRR51
185.18.140.0/22RPKI validIRR51
212.109.160.0/21RPKI validIRR51
217.171.48.0/20RPKI validIRR51

RPKI · ROAs

Route origin authorisations

7 ROAs

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

PrefixMax lengthTrust anchor
31.7.40.0/21/21RIPENCC
46.29.144.0/21/24RIPENCC
85.237.160.0/19/24RIPENCC
185.18.140.0/22/22RIPENCC
212.109.160.0/21/21RIPENCC
217.171.48.0/20/24RIPENCC
2a03:9500::/32/32RIPENCC

ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.

RPKI · ASPA

Declared transit providers

3 declared

This network has signed an ASPA record naming its transit providers. Each is compared against the upstreams observed in routing paths.

ASNetworkASPARouting paths
AS174Cogent Communications, LLCDeclaredObserved
AS6939Hurricane Electric LLCDeclaredObserved
AS12741Netia SADeclaredObserved

An observed upstream that is not declared is not necessarily a leak: our upstream inference cannot tell a transit provider from a peer seen in the same position. A declared provider that is never observed is usually a backup path.

IRR

Registered route objects

7 objects · 0 not announced

Route objects naming AS35063 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
31.7.40.0/21RIPEPL-TKCHOPINTKC-MNT2011-10-31Announced
46.29.144.0/21RIPEPL-TKCHOPINTKC-MNT2010-08-13Announced
85.237.160.0/19RIPEPL-TKCHOPINTKC-MNT2005-05-31Announced
185.18.140.0/22RIPEPL-TKCHOPINTKC-MNT2013-02-11Announced
212.109.160.0/21RIPEPL-TKCHOPINTKC-MNT2012-03-12Announced
217.171.48.0/20RIPEPL-TKCHOPINTKC-MNT2008-01-21Announced
2a03:9500::/32RIPEPL-TKCHOPINTKC-MNT2012-04-01Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-EMITEL-6RIPELists AS35063 as a direct member
AS-EXATEL-PLRIPELists AS35063 as a direct member
AS-HURRICANERADBLists AS35063 as a direct member
AS-HURRICANEV6RADBLists AS35063 as a direct member
AS-NETIARIPELists AS35063 as a direct member
AS-PLIX-CONNECTEDRIPELists AS35063 as a direct member
AS-PLIX6RIPELists AS35063 as a direct member
AS-TKCHOPINRIPELists AS35063 as a direct member
AS-VECTRARIPELists AS35063 as a direct member
AS12831:AS-TASK-COM-PCWSRIPELists AS35063 as a direct member
AS12831:AS-TASK-COM-PIONIER-TPRIPELists AS35063 as a direct member
AS29535:AS-MIX2RIPELists AS35063 as a direct member
AS5550:AS-TASKRIPELists AS35063 as a direct member
AS5550:AS-TASK-1014RIPELists AS35063 as a direct member
AS5617:AS-PLRIPELists AS35063 as a direct member

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