Routing security

AS34775 LVNET-AS

Unclassified RIPE

RPKI valid 100% 29 of 29 announcements

RPKI invalid 0 none

No ROA 0 not covered by any ROA

IRR registered 100% 0 missing · 0 other origin

ROAs 29 authorising this AS

Announcements

What this network originates

29 observed

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

Prefix	RPKI	IRR	Vantage points
2a04:5f80::/29	RPKI valid	IRR	33
2a06:2a00::/29	RPKI valid	IRR	33
2a06:7780::/29	RPKI valid	IRR	33
2a06:ba00::/29	RPKI valid	IRR	33
2a09:4cc0::/29	RPKI valid	IRR	33
2a09:4f40::/29	RPKI valid	IRR	33
2a09:4fc0::/29	RPKI valid	IRR	33
2a09:6a80::/29	RPKI valid	IRR	33
2a09:6dc0::/29	RPKI valid	IRR	33
2a09:7a40::/29	RPKI valid	IRR	33
2a09:8a40::/29	RPKI valid	IRR	33
2a09:8a80::/29	RPKI valid	IRR	33
2a09:9ac0::/29	RPKI valid	IRR	33
2a09:9b40::/29	RPKI valid	IRR	33
2a09:12c0::/29	RPKI valid	IRR	33
2a09:13c0::/29	RPKI valid	IRR	33
2a09:41c0::/29	RPKI valid	IRR	33
2a09:50c0::/29	RPKI valid	IRR	33
2a09:73c0::/29	RPKI valid	IRR	33
2a09:95c0::/29	RPKI valid	IRR	33
2a09:97c0::/29	RPKI valid	IRR	33
2a09:940::/29	RPKI valid	IRR	33
2a09:5040::/29	RPKI valid	IRR	33
2a09:5140::/29	RPKI valid	IRR	33
2a09:5240::/29	RPKI valid	IRR	33
2a09:9840::/29	RPKI valid	IRR	33
2a09:a9c0::/29	RPKI valid	IRR	33
2a09:a400::/29	RPKI valid	IRR	33
2a09:a840::/29	RPKI valid	IRR	33

RPKI · ROAs

Route origin authorisations

29 ROAs

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

Prefix	Max length	Trust anchor
2a04:5f80::/29	/48	RIPENCC
2a06:2a00::/29	/48	RIPENCC
2a06:7780::/29	/48	RIPENCC
2a06:ba00::/29	/48	RIPENCC
2a09:940::/29	/48	RIPENCC
2a09:12c0::/29	/48	RIPENCC
2a09:13c0::/29	/48	RIPENCC
2a09:41c0::/29	/48	RIPENCC
2a09:4cc0::/29	/48	RIPENCC
2a09:4f40::/29	/48	RIPENCC
2a09:4fc0::/29	/48	RIPENCC
2a09:5040::/29	/48	RIPENCC
2a09:50c0::/29	/48	RIPENCC
2a09:5140::/29	/48	RIPENCC
2a09:5240::/29	/48	RIPENCC
2a09:6a80::/29	/48	RIPENCC
2a09:6dc0::/29	/48	RIPENCC
2a09:73c0::/29	/48	RIPENCC
2a09:7a40::/29	/48	RIPENCC
2a09:8a40::/29	/48	RIPENCC
2a09:8a80::/29	/48	RIPENCC
2a09:95c0::/29	/48	RIPENCC
2a09:97c0::/29	/48	RIPENCC
2a09:9840::/29	/48	RIPENCC
2a09:9ac0::/29	/48	RIPENCC
2a09:9b40::/29	/48	RIPENCC
2a09:a400::/29	/48	RIPENCC
2a09:a840::/29	/48	RIPENCC
2a09:a9c0::/29	/48	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

29 objects · 0 not announced

Route objects naming AS34775 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
2a04:5f80::/29	RIPE	—	`LVNET-MNT`	2026-02-24	Announced
2a06:2a00::/29	RIPE	—	`LVNET-MNT`	2026-02-24	Announced
2a06:7780::/29	RIPE	—	`LVNET-MNT`	2026-02-24	Announced
2a06:ba00::/29	RIPE	—	`LVNET-MNT`	2026-02-24	Announced
2a09:940::/29	RIPE	—	`LVNET-MNT`	2026-02-24	Announced
2a09:12c0::/29	RIPE	—	`LVNET-MNT`	2026-02-24	Announced
2a09:13c0::/29	RIPE	—	`LVNET-MNT`	2026-02-24	Announced
2a09:41c0::/29	RIPE	—	`LVNET-MNT`	2026-02-24	Announced
2a09:4cc0::/29	RIPE	—	`LVNET-MNT`	2026-02-24	Announced
2a09:4f40::/29	RIPE	—	`LVNET-MNT`	2026-02-24	Announced
2a09:4fc0::/29	RIPE	—	`LVNET-MNT`	2026-02-24	Announced
2a09:5040::/29	RIPE	—	`LVNET-MNT`	2026-02-24	Announced
2a09:50c0::/29	RIPE	—	`LVNET-MNT`	2026-02-24	Announced
2a09:5140::/29	RIPE	—	`LVNET-MNT`	2026-02-24	Announced
2a09:5240::/29	RIPE	—	`LVNET-MNT`	2026-02-24	Announced
2a09:6a80::/29	RIPE	—	`LVNET-MNT`	2026-02-24	Announced
2a09:6dc0::/29	RIPE	—	`LVNET-MNT`	2026-02-24	Announced
2a09:73c0::/29	RIPE	—	`LVNET-MNT`	2026-02-24	Announced
2a09:7a40::/29	RIPE	—	`LVNET-MNT`	2026-02-24	Announced
2a09:8a40::/29	RIPE	—	`LVNET-MNT`	2026-02-24	Announced
2a09:8a80::/29	RIPE	—	`LVNET-MNT`	2026-02-24	Announced
2a09:95c0::/29	RIPE	—	`LVNET-MNT`	2026-02-24	Announced
2a09:97c0::/29	RIPE	—	`LVNET-MNT`	2026-02-24	Announced
2a09:9840::/29	RIPE	—	`LVNET-MNT`	2026-02-24	Announced
2a09:9ac0::/29	RIPE	—	`LVNET-MNT`	2026-02-24	Announced
2a09:9b40::/29	RIPE	—	`LVNET-MNT`	2026-02-24	Announced
2a09:a400::/29	RIPE	—	`LVNET-MNT`	2026-02-24	Announced
2a09:a840::/29	RIPE	—	`LVNET-MNT`	2026-02-24	Announced
2a09:a9c0::/29	RIPE	—	`LVNET-MNT`	2026-02-24	Announced

IRR

AS-sets

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

AS-set	Where	Relationship
`AS-ANTALEX-PEERS`	RIPE	Lists AS34775 as a direct member
`AS-HURRICANEV6`	RADB	Lists AS34775 as a direct member
`AS-NSST`	RIPE	Lists AS34775 as a direct member
`AS-XCP`	RIPE	Lists AS34775 as a direct member
`AS35661:AS-FRA01DE`	RIPE	Lists AS34775 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.