Routing security

AS43037 SEZNAM-

Hosting RIPE

RPKI valid 100% 12 of 12 announcements

RPKI invalid 0 none

No ROA 0 not covered by any ROA

IRR registered 100% 0 missing · 0 other origin

ROAs 13 authorising this AS

Announcements

What this network originates

12 observed

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

Prefix	RPKI	IRR	Vantage points
2a02:598::/32	RPKI valid	IRR	30
2a02:598:2::/48	RPKI valid	IRR	30
2a02:598:3333::/48	RPKI valid	IRR	30
2a02:598:4444::/48	RPKI valid	IRR	30
2a02:598:a::/48	RPKI valid	IRR	30
2a02:598:b::/48	RPKI valid	IRR	30
77.75.72.0/23	RPKI valid	IRR	54
77.75.74.0/24	RPKI valid	IRR	54
77.75.75.0/24	RPKI valid	IRR	54
77.75.76.0/23	RPKI valid	IRR	54
77.75.78.0/23	RPKI valid	IRR	54
185.66.188.0/22	RPKI valid	IRR	54

RPKI · ROAs

Route origin authorisations

13 ROAs

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

Prefix	Max length	Trust anchor
77.75.72.0/21	/21	RIPENCC
77.75.72.0/23	/23	RIPENCC
77.75.74.0/24	/24	RIPENCC
77.75.75.0/24	/24	RIPENCC
77.75.76.0/23	/23	RIPENCC
77.75.78.0/23	/23	RIPENCC
185.66.188.0/22	/22	RIPENCC
2a02:598::/32	/32	RIPENCC
2a02:598:2::/48	/48	RIPENCC
2a02:598:a::/48	/48	RIPENCC
2a02:598:b::/48	/48	RIPENCC
2a02:598:3333::/48	/48	RIPENCC
2a02:598:4444::/48	/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

13 objects · 1 not announced

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

Prefix	Source	Description	Maintainer	Changed	Routing
77.75.72.0/21	RIPE	—	`SEZNAM-MNT`	2022-11-15	Not announced
77.75.72.0/23	RIPE	SEZNAM - I	`SEZNAM-MNT`	2007-09-20	Announced
77.75.74.0/24	RIPE	SEZNAM - II	`SEZNAM-MNT`	2007-10-04	Announced
77.75.75.0/24	RIPE	SEZNAM - II	`SEZNAM-MNT`	2014-04-29	Announced
77.75.76.0/23	RIPE	SEZNAM - III	`SEZNAM-MNT`	2007-10-04	Announced
77.75.78.0/23	RIPE	SEZNAM - II	`SEZNAM-MNT`	2014-10-16	Announced
185.66.188.0/22	RIPE	SEZNAM - III	`SEZNAM-MNT`	2015-11-02	Announced
2a02:598::/32	RIPE	Seznam.cz IPv6 route	`SEZNAM-MNT`	2010-06-22	Announced
2a02:598:2::/48	RIPE	—	`SEZNAM-MNT`	2016-08-16	Announced
2a02:598:a::/48	RIPE	—	`SEZNAM-MNT`	2016-08-16	Announced
2a02:598:b::/48	RIPE	—	`SEZNAM-MNT`	2016-08-16	Announced
2a02:598:3333::/48	RIPE	SEZNAM - II	`SEZNAM-MNT`	2014-04-29	Announced
2a02:598:4444::/48	RIPE	SEZNAM - II	`SEZNAM-MNT`	2014-04-29	Announced

IRR

AS-sets

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

AS-set	Where	Relationship
`AS-43413_NT-NIX`	RIPE	Lists AS43037 as a direct member
`AS-CTIOL`	RIPE	Lists AS43037 as a direct member
`AS-DIALTELECOM`	RIPE	Lists AS43037 as a direct member
`AS-MANDA-DECIX-PEERS-V4`	RIPE	Lists AS43037 as a direct member
`AS-MANDA-DECIX-PEERS-V6`	RIPE	Lists AS43037 as a direct member
`AS-SEZNAM-CZ`	RIPE	Lists AS43037 as a direct member
`AS-TO2-NIX-PEER`	RIPE	Lists AS43037 as a direct member
`AS24971:AS-MAI-NIX-PEER`	RIPE	Lists AS43037 as a direct member
`AS42000:AS-NIXCZ-PEERINGS`	RIPE	Lists AS43037 as a direct member
`AS6695:AS-DECIX-FRA-CONNECTED`	RIPE	Lists AS43037 as a direct member
`AS6695:AS-DECIX-FRA-RS`	RIPE	Lists AS43037 as a direct member
`AS6695:AS-DECIX-FRA-RS-V6`	RIPE	Lists AS43037 as a direct member
`AS8251:AS-NIX-PEERINGS`	RIPE	Lists AS43037 as a direct member

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