asn.dev

Routing security

AS213838 LD

Unclassified APNIC

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

Announcements

What this network originates

2 observed

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

PrefixRPKIIRRVantage points
2a14:7f40::/29RPKI validNo IRR34
91.221.41.0/24RPKI validIRR57

RPKI · ROAs

Route origin authorisations

2 ROAs

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

PrefixMax lengthTrust anchor
91.221.41.0/24/24RIPENCC
2a14:7f40::/29/29RIPENCC

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

RPKI · ASPA

Declared transit providers

1 declared

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

ASNetworkASPARouting paths
AS47794Etihad GO Company For communicationsDeclaredObserved

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

1 objects · 0 not announced

Route objects naming AS213838 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
91.221.41.0/24RIPELast Dimension IPv4 RouteLIR-SA-COMPANY-1-MNT2026-08-30Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-ATHEEB-PEERSRIPELists AS213838 as a direct member
AS-HURRICANERADBLists AS213838 as a direct member
AS-HURRICANEV6RADBLists AS213838 as a direct member

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