asn.dev

Routing security

AS41911 LANET-SD

Unclassified RIPE

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

Announcements

What this network originates

13 observed

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

PrefixRPKIIRRVantage points
91.208.116.0/24No ROAIRR57
46.250.96.0/19RPKI validIRR57
91.241.120.0/21RPKI validIRR57
91.241.120.0/22RPKI validIRR57
91.241.124.0/22RPKI validIRR57
91.243.0.0/19RPKI validIRR57
91.243.0.0/20RPKI validIRR52
91.243.16.0/20RPKI validIRR52
176.39.40.0/21RPKI validIRR57
176.39.40.0/22RPKI validIRR57
176.39.44.0/22RPKI validIRR57
176.110.0.0/19RPKI validIRR57
176.110.32.0/19RPKI validIRR57

RPKI · ROAs

Route origin authorisations

6 ROAs

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

PrefixMax lengthTrust anchor
46.250.96.0/19/20RIPENCC
91.241.120.0/21/22RIPENCC
91.243.0.0/19/20RIPENCC
176.39.40.0/21/22RIPENCC
176.110.0.0/19/19RIPENCC
176.110.32.0/19/19RIPENCC

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

21 objects · 8 not announced

Route objects naming AS41911 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
46.250.96.0/20RIPELanet Network Customers More Specific RouteLANET-MNT2019-10-29Not announced
46.250.112.0/20RIPELanet Network Customers More Specific RouteLANET-MNT2019-10-29Not announced
91.241.112.0/20RIPELanet Network CustomersLANET-MNT2023-09-28Not announced
91.241.124.0/24RIPE—LANET-MNT2023-08-28Not announced
176.110.0.0/20RIPELanet Network Customers More Specific RouteLANET-MNT2019-10-30Not announced
176.110.16.0/20RIPELanet Network Customers More Specific RouteLANET-MNT2019-10-30Not announced
176.110.32.0/20RIPELanet Network Customers More Specific RouteLANET-MNT2019-10-30Not announced
176.110.48.0/20RIPELanet Network Customers More Specific RouteLANET-MNT2019-10-30Not announced
46.250.96.0/19RIPELanet Network Customers RouteLANET-MNT2019-10-29Announced
91.208.116.0/24RIPE—LANET-MNT2025-03-25Announced
91.241.120.0/21RIPELanet Network CustomersLANET-MNT2023-09-28Announced
91.241.120.0/22RIPELanet Network CustomersLANET-MNT2023-09-28Announced
91.241.124.0/22RIPELanet Network CustomersLANET-MNT2023-09-28Announced
91.243.0.0/19RIPELanet Network CustomersLANET-MNT2023-09-28Announced
91.243.0.0/20RIPELanet Network CustomersLANET-MNT2023-09-28Announced
91.243.16.0/20RIPELanet Network CustomersLANET-MNT2023-09-28Announced
176.39.40.0/21RIPE—LANET-NETOPS-MNT2025-02-22Announced
176.39.40.0/22RIPE—LANET-NETOPS-MNT2025-02-22Announced
176.39.44.0/22RIPE—LANET-NETOPS-MNT2025-02-22Announced
176.110.0.0/19RIPELanet Network RouteLANET-MNT2019-10-30Announced
176.110.32.0/19RIPELanet Network RouteLANET-MNT2019-10-30Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-HURRICANERADBLists AS41911 as a direct member
AS-LANETUARIPELists AS41911 as a direct member
AS-RETN-ACTUAL-V4RIPELists AS41911 as a direct member

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