asn.dev

Routing security

AS49912 MRTV

Unclassified RIPE

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

Announcements

What this network originates

3 observed

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

PrefixRPKIIRRVantage points
84.32.80.0/23RPKI validIRR52
88.216.26.0/23RPKI validIRR52
88.216.160.0/23RPKI validIRR52

RPKI · ROAs

Route origin authorisations

4 ROAs

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

PrefixMax lengthTrust anchor
84.32.36.0/23/23RIPENCC
84.32.80.0/23/23RIPENCC
88.216.26.0/23/23RIPENCC
88.216.160.0/23/23RIPENCC

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

4 objects · 1 not announced

Route objects naming AS49912 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
84.32.36.0/24RIPE—MNT-NTT-LIR2024-11-11Not announced
84.32.80.0/23RIPE—MNT-NTT-LIR2024-11-11Announced
88.216.26.0/23RIPE—MNT-NTT-LIR2024-11-11Announced
88.216.160.0/23RIPE—MNT-NTT-LIR2024-11-11Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-NTT-LTRIPELists AS49912 as a direct member
AS-RETN-ACTUAL-V4RIPELists AS49912 as a direct member
AS-TRANSROUTE-SPECRIPELists AS49912 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.