asn.dev

Routing security

AS57801 SK-NIC-AS SK-NIC, a.s.

Unclassified APNIC

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

Announcements

What this network originates

7 observed

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

PrefixRPKIIRRVantage points
2a02:6300:30::/48No ROAIRR30
109.71.66.0/24No ROAIRR54
185.16.187.0/24No ROAIRR52
2a04:2b00:100::/48RPKI validIRR29
84.245.96.0/24RPKI validIRR1
194.0.45.0/24RPKI validIRR1
195.12.159.0/24RPKI validIRR1

RPKI · ROAs

Route origin authorisations

9 ROAs

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

PrefixMax lengthTrust anchor
84.245.96.0/24/24RIPENCC
91.212.112.0/24/24RIPENCC
194.0.45.0/24/24RIPENCC
195.12.159.0/24/24RIPENCC
2001:678:70::/48/48RIPENCC
2001:678:90::/48/48RIPENCC
2001:678:9c::/48/48RIPENCC
2001:67c:26d4::/48/48RIPENCC
2a04:2b00:100::/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

12 objects · 5 not announced

Route objects naming AS57801 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.212.112.0/24RIPESK-NIC, a.s. PI networkSKNIC-MNT2012-02-14Not announced
2001:678:70::/48RIPESK-NIC, a.s.SKNIC-MNT2021-05-19Not announced
2001:678:90::/48RIPESK-NIC, a.s.SKNIC-MNT2021-05-19Not announced
2001:678:9c::/48RIPESK-NIC, a.s.SKNIC-MNT2021-05-19Not announced
2001:67c:26d4::/48RIPESK-NIC, a.s. PI networkSKNIC-MNT2012-02-14Not announced
84.245.96.0/24RIPESK-NIC, a.s.SKNIC-MNT2021-05-19Announced
109.71.66.0/24RIPE—SKNIC-MNT2017-09-18Announced
185.16.187.0/24RIPE—CENTRALNIC-MNT2024-08-06Announced
194.0.45.0/24RIPESK-NIC, a.s.SKNIC-MNT2021-05-19Announced
195.12.159.0/24RIPESK-NIC, a.s.SKNIC-MNT2021-05-19Announced
2a02:6300:30::/48RIPE—SKNIC-MNT2017-09-18Announced
2a04:2b00:100::/48RIPE—CENTRALNIC-MNT2024-08-06Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-BENESTRARIPELists AS57801 as a direct member
AS-CNICRIPELists AS57801 as a direct member
AS-LIGHTSTORMRIPELists AS57801 as a direct member
AS-NWN-TRANSITRADBLists AS57801 as a direct member
AS-SWANRIPELists AS57801 as a direct member
AS13335:AS-CUSTOMERSARINLists AS57801 as a direct member
AS50128:AS-CUSTOMERSRIPELists AS57801 as a direct member
AS57801:AS-TRANZITRIPELists AS57801 as a direct member

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