asn.dev

Routing security

AS35493 BELNET

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 AS35493 as its origin, checked against RPKI and the IRR. Problems sort first.

PrefixRPKIIRRVantage points
91.237.168.0/23RPKI validIRR52
91.237.170.0/24RPKI validIRR52
185.90.164.0/22RPKI validIRR52

RPKI · ROAs

Route origin authorisations

4 ROAs

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

PrefixMax lengthTrust anchor
91.237.168.0/23/23RIPENCC
91.237.170.0/24/24RIPENCC
185.90.164.0/22/22RIPENCC
2a05:e300::/29/29RIPENCC

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

Route objects naming AS35493 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.237.168.0/23RIPEBelnet Snina, s.r.o.MNT-BELNET2015-03-26Announced
91.237.170.0/24RIPEBelnet Snina, s.r.o.MNT-BELNET2015-03-26Announced
185.90.164.0/22RIPEBelnet Snina, s.r.o.MNT-BELNET2015-03-26Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-EMAXRIPELists AS35493 as a direct member
AS-RETN-ACTUAL-V4RIPELists AS35493 as a direct member
AS-SLOVAKRIPELists AS35493 as a direct member

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