Routing security

AS39608 LANETUA-AS

Residential RIPE

RPKI valid 100% 16 of 16 announcements

RPKI invalid 0 none

No ROA 0 not covered by any ROA

IRR registered 88% 2 missing · 0 other origin

ROAs 23 authorising this AS

Announcements

What this network originates

16 observed

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

Prefix	RPKI	IRR	Vantage points
193.93.160.0/22	RPKI valid	No IRR	6
193.107.224.0/22	RPKI valid	No IRR	6
86.111.88.0/21	RPKI valid	IRR	57
91.194.81.0/24	RPKI valid	IRR	57
91.216.165.0/24	RPKI valid	IRR	57
176.36.0.0/16	RPKI valid	IRR	57
176.37.0.0/16	RPKI valid	IRR	57
176.38.0.0/16	RPKI valid	IRR	57
176.39.34.0/23	RPKI valid	IRR	57
176.39.36.0/23	RPKI valid	IRR	57
185.53.76.0/23	RPKI valid	IRR	57
185.53.76.0/24	RPKI valid	IRR	57
185.53.78.0/24	RPKI valid	IRR	57
194.33.189.0/24	RPKI valid	IRR	57
194.50.85.0/24	RPKI valid	IRR	52
194.60.69.0/24	RPKI valid	IRR	57

RPKI · ROAs

Route origin authorisations

23 ROAs

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

Prefix	Max length	Trust anchor
86.111.64.0/19	/19	RIPENCC
86.111.88.0/21	/22	RIPENCC
91.194.81.0/24	/24	RIPENCC
91.216.165.0/24	/24	RIPENCC
176.36.0.0/14	/14	RIPENCC
176.36.0.0/16	/17	RIPENCC
176.36.160.0/24	/24	RIPENCC
176.37.0.0/16	/17	RIPENCC
176.38.0.0/16	/17	RIPENCC
176.38.244.0/23	/23	RIPENCC
176.39.0.0/16	/16	RIPENCC
176.39.34.0/23	/24	RIPENCC
176.39.36.0/23	/24	RIPENCC
185.53.76.0/23	/24	RIPENCC
185.53.76.0/24	/24	RIPENCC
185.53.78.0/24	/24	RIPENCC
193.93.160.0/22	/22	RIPENCC
193.107.224.0/22	/22	RIPENCC
194.33.189.0/24	/24	RIPENCC
194.50.85.0/24	/24	RIPENCC
194.60.69.0/24	/24	RIPENCC
2a01:5800::/32	/32	RIPENCC
2a01:bf20::/32	/32	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

36 objects · 22 not announced

Route objects naming AS39608 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
86.111.64.0/19	RIPE	Lanet Network Customers Route	`LANET-MNT`	2019-10-29	Not announced
86.111.64.0/20	RIPE	Lanet Network Customers More Specific Route	`LANET-MNT`	2019-10-29	Not announced
86.111.80.0/20	RIPE	Lanet Network Customers More Specific Route	`LANET-MNT`	2019-10-29	Not announced
86.111.88.0/22	RIPE	—	`LANET-MNT`	2022-04-27	Not announced
86.111.92.0/22	RIPE	—	`LANET-MNT`	2022-04-27	Not announced
176.36.0.0/14	RIPE	Lanet Network Route	`LANET-MNT`	2019-10-29	Not announced
176.36.0.0/17	RIPE	Lanet Network More Specific Route	`LANET-MNT`	2021-02-01	Not announced
176.36.128.0/17	RIPE	Lanet Network More Specific Route	`LANET-MNT`	2021-02-01	Not announced
176.36.160.0/23	RIPE	—	`LANET-MNT`	2024-03-06	Not announced
176.36.160.0/24	RIPE	—	`LANET-MNT`	2023-03-02	Not announced
176.37.0.0/17	RIPE	Lanet Network More Specific Route	`LANET-MNT`	2021-02-01	Not announced
176.37.128.0/17	RIPE	Lanet Network More Specific Route	`LANET-MNT`	2021-02-01	Not announced
176.37.162.0/24	RIPE	—	`LANET-MNT`	2021-05-05	Not announced
176.38.0.0/17	RIPE	Lanet Network More Specific Route	`LANET-MNT`	2021-02-01	Not announced
176.38.128.0/17	RIPE	Lanet Network More Specific Route	`LANET-MNT`	2021-02-01	Not announced
176.38.162.0/24	RIPE	—	`LANET-MNT`	2021-05-05	Not announced
176.38.244.0/23	RIPE	—	`LANET-MNT`	2026-03-05	Not announced
176.39.0.0/16	RIPE	Lanet Network More Specific Route	`LANET-MNT`	2019-10-30	Not announced
176.39.36.0/24	RIPE	—	`LANET-MNT`	2022-02-10	Not announced
176.39.37.0/24	RIPE	—	`LANET-MNT`	2022-02-10	Not announced
2a01:5800::/32	RIPE	Lanet Network Ltd	`LANET-MNT`	2019-10-29	Not announced
2a01:bf20::/32	RIPE	—	`LANET-MNT`	2019-10-29	Not announced
86.111.88.0/21	RIPE	—	`LANET-MNT`	2022-04-27	Announced
91.194.81.0/24	RIPE	—	`LANET-MNT`	2023-12-07	Announced
91.216.165.0/24	RIPE	Lanet Network Route	`LANET-MNT`	2017-07-26	Announced
176.36.0.0/16	RIPE	Lanet Network More Specific Route	`LANET-MNT`	2019-10-29	Announced
176.37.0.0/16	RIPE	Lanet Network More Specific Route	`LANET-MNT`	2019-10-29	Announced
176.38.0.0/16	RIPE	Lanet Network More Specific Route	`LANET-MNT`	2019-10-30	Announced
176.39.34.0/23	RIPE	—	`LANET-MNT`	2021-08-16	Announced
176.39.36.0/23	RIPE	—	`LANET-MNT`	2022-02-10	Announced
185.53.76.0/23	RIPE	—	`LANET-MNT`	2019-04-17	Announced
185.53.76.0/24	RIPE	—	`LANET-MNT`	2023-01-22	Announced
185.53.78.0/24	RIPE	—	`LANET-MNT`	2022-04-27	Announced
194.33.189.0/24	RIPE	Lanet Network Services Route	`LANET-MNT`	2019-10-29	Announced
194.50.85.0/24	RIPE	Lanet Network Route	`LANET-MNT`	2019-10-30	Announced
194.60.69.0/24	RIPE	Lanet Network Ltd	`LANET-MNT`	2019-10-30	Announced

IRR

AS-sets

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

AS-set	Where	Relationship
`AS-HURRICANE`	RADB	Lists AS39608 as a direct member
`AS-LANETUA`	RIPE	Lists AS39608 as a direct member
`AS-LANETUA-V6`	RIPE	Lists AS39608 as a direct member
`AS-RETN-ACTUAL-V4`	RIPE	Lists AS39608 as a direct member
`AS-TRANSROUTE-SPEC`	RIPE	Lists AS39608 as a direct member
`AS-UARNET`	RIPE	Lists AS39608 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.