asn.dev

Routing security

AS202798 EITAA-MESSENGER

Unclassified RIPE

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

Announcements

What this network originates

3 observed

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

PrefixRPKIIRRVantage points
2.189.56.0/24RPKI validIRR other origin53
2.189.58.0/24RPKI validIRR53
91.102.126.0/24RPKI validIRR53

RPKI · ROAs

Route origin authorisations

4 ROAs

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

PrefixMax lengthTrust anchor
2.189.56.0/24/24RIPENCC
2.189.58.0/24/24RIPENCC
91.102.126.0/24/24RIPENCC
2001:67c:db8::/48/48RIPENCC

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

3 objects · 1 not announced

Route objects naming AS202798 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
2001:67c:db8::/48RIPE—EITAA-MNT2024-01-31Not announced
2.189.58.0/24RIPE—AS12880-MNT2023-05-01Announced
91.102.126.0/24RIPE—EITAA-MNT2026-04-14Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-TICGWRIPELists AS202798 as a direct member
AS202798:AS-EITAARIPELists AS202798 as a direct member
AS41194:AS-RASCOMRIPELists AS202798 as a direct member

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