asn.dev

Routing security

AS214830 ZEBRA-TELECOM-AS

Unclassified RIPE

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

Announcements

What this network originates

4 observed

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

PrefixRPKIIRRVantage points
91.210.172.0/24No ROAIRR55
91.210.173.0/24No ROAIRR55
91.210.174.0/24No ROAIRR53
91.210.175.0/24No ROAIRR52

RPKI · ROAs

Route origin authorisations

0 ROAs

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

No ROA names this AS as an authorised origin.

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 · 0 not announced

Route objects naming AS214830 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.210.172.0/24RIPE—ALKZ-MNT2024-05-24Announced
91.210.173.0/24RIPE—ALKZ-MNT2024-05-24Announced
91.210.174.0/24RIPE—ALKZ-MNT2024-05-24Announced
91.210.175.0/24RIPE—ALKZ-MNT2024-05-24Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-HURRICANERADBLists AS214830 as a direct member
AS-RETN-ACTUAL-V4RIPELists AS214830 as a direct member
AS-SET_TNSPLUSRIPELists AS214830 as a direct member
AS-TRANSKZRIPELists AS214830 as a direct member

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