Network · data from 2026-11-12

AS60916 GEYTIT

Registry name: GATEIT-AS GEYTIT OOD, BG · PeeringDB

3IPv4 routes 33.3% RPKI valid · 33.3% with a route object

0IPv6 routes

2RPKI invalid 0 origin · 2 maxLength

0No ROA 2 with no route object for this origin

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

0Route objects not announced registered with origin AS60916, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS60916, 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.


185.72.56.56/32	Invalid: maxLength	Nonecovered by 185.72.56.0/24	3 0%low visibility	6
185.72.56.74/32	Invalid: maxLength	Nonecovered by 185.72.56.0/24	3 0%low visibility	6
185.72.56.0/24	Valid	RIR databaseRIPE	673 100%	66

185.72.56.56/32

Invalid: maxLength

Nonecovered by 185.72.56.0/24

3 0%low visibility

185.72.56.74/32

Invalid: maxLength

Nonecovered by 185.72.56.0/24

3 0%low visibility

185.72.56.0/24

Valid

RIR databaseRIPE

673 100%

AS-SET

AS60916'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 4 are in fix.csv.

ROA: maxLength2
Route object: none2

Change	Prefix or set	Detail	Full-table peers
ROA: maxLength	185.72.56.56/32	ROA 185.72.56.0/24 AS60916 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 185.72.56.56/32.	3 of 673
Route object: none	185.72.56.56/32	No route object for it. A route object for 185.72.56.0/24 with origin AS60916 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS60916 in the RIR database for the space.	3 of 673
ROA: maxLength	185.72.56.74/32	ROA 185.72.56.0/24 AS60916 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 185.72.56.74/32.	3 of 673
Route object: none	185.72.56.74/32	No route object for it. A route object for 185.72.56.0/24 with origin AS60916 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS60916 in the RIR database for the space.	3 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: maxLength

185.72.56.56/32

ROA 185.72.56.0/24 AS60916 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 185.72.56.56/32.

3 of 673

Route object: none

185.72.56.56/32

No route object for it. A route object for 185.72.56.0/24 with origin AS60916 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS60916 in the RIR database for the space.

3 of 673

ROA: maxLength

185.72.56.74/32

ROA 185.72.56.0/24 AS60916 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 185.72.56.74/32.

3 of 673

Route object: none

185.72.56.74/32

3 of 673

Route objects not announced

Every route object with origin AS60916 is announced.

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.