Network · data from 2026-11-12

AS60592 Gransy s.r.o. - anycastdns.cz

Registry name: GRANSY Gransy s.r.o., CZ · PeeringDB

18IPv4 routes 88.9% RPKI valid · 94.4% with a route object

3IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

2No ROA 1 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

5Route objects not announced registered with origin AS60592, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS60592, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.


91.207.188.0/23	No ROA	Other origin only	673 100%	67
46.175.135.0/24	No ROA	RIR databaseRIPE	672 100%	67
91.207.188.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
91.207.189.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
185.28.192.0/24	Valid	RIR databaseRIPE	673 100%	67
185.28.193.0/24	Valid	RIR databaseRIPE	673 100%	67
185.38.109.0/24	Valid	RIR databaseRIPE	673 100%	67
185.82.212.0/24	Valid	RIR databaseRIPE	673 100%	67
185.82.213.0/24	Valid	RIR databaseRIPE	673 100%	67
185.82.214.0/24	Valid	RIR databaseRIPE	673 100%	67
23.26.24.0/21	Valid	RIR databaseARIN	672 100%	67
185.38.110.0/24	Valid	RIR databaseRIPE	672 100%	67
185.38.111.0/24	Valid	RIR databaseRIPE	672 100%	67
46.8.8.0/24	Valid	RIR databaseRIPE	671 100%	66
91.224.58.0/24	Valid	RIR databaseRIPE	670 100%	68
185.38.108.0/24	Valid	RIR databaseRIPE	670 100%	67
46.8.9.0/24	Valid	RIR databaseRIPE	669 99%	66
185.28.194.0/24	Valid	RIR databaseRIPE	669 99%	67
2a00:a160::/32	Valid	RIR databaseRIPE	635 100%	69
2a03:6920::/32	Valid	RIR databaseRADB, RIPE	635 100%	67
2a00:fea0::/32	Valid	RIR databaseRADB, RIPE	634 100%	70

AS-SET

AS60592's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 8 are in fix.csv.

ROA: none2
Route object: none1
Route object: not announced5

Change	Prefix or set	Detail	Full-table peers
ROA: none	91.207.188.0/23	No ROA covers it. Add a ROA for AS60592, maxLength 23.	673 of 673
Route object: none	91.207.188.0/23	Route objects for it name AS15685. Add a route object with origin AS60592 in the RIR database for the space.	673 of 673
ROA: none	46.175.135.0/24	No ROA covers it. Add a ROA for AS60592, maxLength 24.	672 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

91.207.188.0/23

No ROA covers it. Add a ROA for AS60592, maxLength 23.

673 of 673

Route object: none

91.207.188.0/23

Route objects for it name AS15685. Add a route object with origin AS60592 in the RIR database for the space.

673 of 673

ROA: none

46.175.135.0/24

No ROA covers it. Add a ROA for AS60592, maxLength 24.

672 of 673

Route objects not announced

Route objects with origin AS60592 whose prefix no peer sees AS60592 announce. Many are kept on purpose (backup routes, space announced only in some places).


46.8.8.0/23	RADB	Valid
185.28.192.0/22	RIPE	No ROA
185.28.195.0/24	RIPE	No ROA
2a00:a160::/48	RIPE	Invalid: maxLength
2a03:6920::/48	RIPE	Invalid: maxLength

46.8.8.0/23

RADB

Valid

185.28.192.0/22

RIPE

No ROA

185.28.195.0/24

RIPE

No ROA

2a00:a160::/48

RIPE

Invalid: maxLength

2a03:6920::/48

RIPE

Invalid: maxLength

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.