Routing security

AS401856 METAMERG-NET - Metamerg Network LLC

Unclassified ARIN

RPKI valid 100% 6 of 6 announcements

RPKI invalid 0 none

No ROA 0 not covered by any ROA

IRR registered 0% 6 missing · 0 other origin

ROAs 6 authorising this AS

Announcements

What this network originates

6 observed

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

Prefix	RPKI	IRR	Vantage points
2a01:6640::/29	RPKI valid	No IRR	30
2a11:b980::/29	RPKI valid	No IRR	30
2a11:c480::/29	RPKI valid	No IRR	30
2a11:ce80::/29	RPKI valid	No IRR	30
2a11:dd80::/29	RPKI valid	No IRR	30
2a11:ef80::/29	RPKI valid	No IRR	30

RPKI · ROAs

Route origin authorisations

6 ROAs

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

Prefix	Max length	Trust anchor
2a01:6640::/29	/48	RIPENCC
2a11:b980::/29	/48	RIPENCC
2a11:c480::/29	/48	RIPENCC
2a11:ce80::/29	/48	RIPENCC
2a11:dd80::/29	/48	RIPENCC
2a11:ef80::/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

0 objects · 0 not announced

Route objects naming AS401856 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.

No route objects name this AS as origin.

IRR

AS-sets

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

AS-set	Where	Relationship
`AS-ZENLAYER`	RADB	Lists AS401856 as a direct member
`AS62610:AS-ZEC-CUSTOMER`	RADB	Lists AS401856 as a direct member

RPKI from rpki-client, validated 2026-11-07 13:08 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-11-07. Cross-check on bgp.he.net.