bgpreport

Network · data from 2026-11-12

AS44234 GAYA-AS Gaya, s.r.o.

Registry name: GAYA-AS Gaya, s.r.o., SK · not in PeeringDB

7IPv4 routes 14.3% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
7No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS44234, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS44234, 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.
80.242.32.0/22 No ROA RIR databaseRIPE 671 100% 66
80.242.36.0/22 No ROA RIR databaseRIPE 671 100% 66
185.251.120.0/23 No ROA RIR databaseRIPE 671 100% 66
185.251.122.0/23 No ROA RIR databaseRIPE 671 100% 66
80.242.32.0/21 No ROA RIR databaseRIPE 669 99% 67
185.251.120.0/22 No ROA RIR databaseRIPE 667 99% 67
2a02:6722::/32 No ROA RIR databaseRIPE 634 100% 69
213.215.105.0/24 Valid RIR databaseRIPE 672 100% 66

AS-SET

AS44234 isn't in PeeringDB, where networks name their 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 7 are in fix.csv.

  • ROA: none7
ChangePrefix or setDetailFull-table peers
ROA: none80.242.32.0/22No ROA covers it. Add a ROA for AS44234, maxLength 22.671 of 673
ROA: none80.242.36.0/22No ROA covers it. Add a ROA for AS44234, maxLength 22.671 of 673
ROA: none185.251.120.0/23No ROA covers it. Add a ROA for AS44234, maxLength 23.671 of 673
ROA: none185.251.122.0/23No ROA covers it. Add a ROA for AS44234, maxLength 23.671 of 673
ROA: none80.242.32.0/21No ROA covers it. Add a ROA for AS44234, maxLength 21.669 of 673
ROA: none185.251.120.0/22No ROA covers it. Add a ROA for AS44234, maxLength 22.667 of 673
ROA: none2a02:6722::/32No ROA covers it. Add a ROA for AS44234, maxLength 32.634 of 636

Route objects not announced

Every route object with origin AS44234 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.