Routing security

AS44364 LVNET-AS

Unclassified RIPE

RPKI valid 100% 39 of 39 announcements

RPKI invalid 0 none

No ROA 0 not covered by any ROA

IRR registered 100% 0 missing · 0 other origin

ROAs 30 authorising this AS

Announcements

What this network originates

39 observed

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

Prefix	RPKI	IRR	Vantage points
2a00:48a0::/29	RPKI valid	IRR	31
2a0a:dd80::/29	RPKI valid	IRR	31
2a0c:8140::/29	RPKI valid	IRR	31
2a0c:fa80::/29	RPKI valid	IRR	31
2a0d:5e40::/29	RPKI valid	IRR	31
2a0e:83c0::/29	RPKI valid	IRR	31
2a09:9cc0::/29	RPKI valid	IRR	31
2a09:9cc0::/48	RPKI valid	IRR	31
2a09:9d40::/29	RPKI valid	IRR	31
2a09:9d40::/48	RPKI valid	IRR	31
2a09:9dc0::/29	RPKI valid	IRR	31
2a09:9dc0::/48	RPKI valid	IRR	31
2a09:9e40::/29	RPKI valid	IRR	31
2a09:9e40::/48	RPKI valid	IRR	31
2a09:47c0::/29	RPKI valid	IRR	31
2a09:47c0::/48	RPKI valid	IRR	31
2a09:1240::/29	RPKI valid	IRR	31
2a09:1240::/48	RPKI valid	IRR	31
2a09:4740::/29	RPKI valid	IRR	31
2a09:4740::/48	RPKI valid	IRR	31
2a09:7700::/29	RPKI valid	IRR	31
2a09:a080::/29	RPKI valid	IRR	31
2a09:a080::/48	RPKI valid	IRR	31
2a09:cc0::/29	RPKI valid	IRR	31
2a09:cc0::/48	RPKI valid	IRR	31
2a10:3cc0::/29	RPKI valid	IRR	31
2a10:51c0::/29	RPKI valid	IRR	31
2a10:7880::/29	RPKI valid	IRR	31
2a11:9080::/29	RPKI valid	IRR	31
2a11:9180::/29	RPKI valid	IRR	31
2a11:9280::/29	RPKI valid	IRR	31
2a11:9680::/29	RPKI valid	IRR	31
2a11:a780::/29	RPKI valid	IRR	31
2a11:a880::/29	RPKI valid	IRR	31
2a11:a980::/29	RPKI valid	IRR	31
2a11:b280::/29	RPKI valid	IRR	31
2a11:b380::/29	RPKI valid	IRR	31
2a11:b480::/29	RPKI valid	IRR	31
2a11:d800::/29	RPKI valid	IRR	31

RPKI · ROAs

Route origin authorisations

30 ROAs

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

Prefix	Max length	Trust anchor
2a00:48a0::/29	/48	RIPENCC
2a09:cc0::/29	/48	RIPENCC
2a09:1240::/29	/48	RIPENCC
2a09:4740::/29	/48	RIPENCC
2a09:47c0::/29	/48	RIPENCC
2a09:7700::/29	/48	RIPENCC
2a09:9cc0::/29	/48	RIPENCC
2a09:9d40::/29	/48	RIPENCC
2a09:9dc0::/29	/48	RIPENCC
2a09:9e40::/29	/48	RIPENCC
2a09:a080::/29	/48	RIPENCC
2a0a:dd80::/29	/48	RIPENCC
2a0c:8140::/29	/48	RIPENCC
2a0c:fa80::/29	/48	RIPENCC
2a0d:5e40::/29	/48	RIPENCC
2a0e:83c0::/29	/48	RIPENCC
2a10:3cc0::/29	/48	RIPENCC
2a10:51c0::/29	/48	RIPENCC
2a10:7880::/29	/48	RIPENCC
2a11:9080::/29	/48	RIPENCC
2a11:9180::/29	/48	RIPENCC
2a11:9280::/29	/48	RIPENCC
2a11:9680::/29	/48	RIPENCC
2a11:a780::/29	/48	RIPENCC
2a11:a880::/29	/48	RIPENCC
2a11:a980::/29	/48	RIPENCC
2a11:b280::/29	/48	RIPENCC
2a11:b380::/29	/48	RIPENCC
2a11:b480::/29	/48	RIPENCC
2a11:d800::/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

39 objects · 0 not announced

Route objects naming AS44364 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
2a00:48a0::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced
2a09:cc0::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced
2a09:cc0::/48	RADB	Vultr Customer Route	`MAINT-AS20473`	2023-11-13	Announced
2a09:1240::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced
2a09:1240::/48	RADB	Vultr Customer Route	`MAINT-AS20473`	2023-11-13	Announced
2a09:4740::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced
2a09:4740::/48	RADB	Vultr Customer Route	`MAINT-AS20473`	2026-02-25	Announced
2a09:47c0::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced
2a09:47c0::/48	RADB	Vultr Customer Route	`MAINT-AS20473`	2026-02-25	Announced
2a09:7700::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced
2a09:9cc0::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced
2a09:9cc0::/48	RADB	Vultr Customer Route	`MAINT-AS20473`	2026-02-25	Announced
2a09:9d40::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced
2a09:9d40::/48	RADB	Vultr Customer Route	`MAINT-AS20473`	2026-02-25	Announced
2a09:9dc0::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced
2a09:9dc0::/48	RADB	Vultr Customer Route	`MAINT-AS20473`	2026-02-25	Announced
2a09:9e40::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced
2a09:9e40::/48	RADB	Vultr Customer Route	`MAINT-AS20473`	2026-02-25	Announced
2a09:a080::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced
2a09:a080::/48	RADB	Vultr Customer Route	`MAINT-AS20473`	2023-11-13	Announced
2a0a:dd80::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced
2a0c:8140::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced
2a0c:fa80::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced
2a0d:5e40::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced
2a0e:83c0::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced
2a10:3cc0::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced
2a10:51c0::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced
2a10:7880::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced
2a11:9080::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced
2a11:9180::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced
2a11:9280::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced
2a11:9680::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced
2a11:a780::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced
2a11:a880::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced
2a11:a980::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced
2a11:b280::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced
2a11:b380::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced
2a11:b480::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced
2a11:d800::/29	RIPE	—	`LVNET-MNT`	2026-02-25	Announced

IRR

AS-sets

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

AS-set	Where	Relationship
`AS-RETN-ACTUAL-V6`	RIPE	Lists AS44364 as a direct member
`AS-TREYD`	RIPE	Lists AS44364 as a direct member
`AS20473:AS-VULTR`	RADB	Lists AS44364 as a direct member
`AS205983:AS-SG`	RIPE	Lists AS44364 as a direct member

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