bgpreport

Network · data from 2026-11-12

AS202682 Geetoo

Registry name: geetoo-cz Geetoo Technology s.r.o., CZ · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS202682, 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.
92.119.64.0/24 Valid Nonecovered by 92.119.64.0/22 672 100% 67
92.119.65.0/24 Valid Nonecovered by 92.119.64.0/22 672 100% 67
92.119.66.0/24 Valid Nonecovered by 92.119.64.0/22 672 100% 67
92.119.67.0/24 Valid Nonecovered by 92.119.64.0/22 672 100% 67
185.155.129.0/24 Valid Nonecovered by 185.155.128.0/22 672 100% 67
185.155.130.0/24 Valid Nonecovered by 185.155.128.0/22 672 100% 67
185.155.131.0/24 Valid Nonecovered by 185.155.128.0/22 672 100% 67
92.119.64.0/22 Valid RIR databaseRIPE 673 100% 66
185.155.128.0/22 Valid RIR databaseRIPE 673 100% 66
2a07:9444::/32 Valid RIR databaseRIPE 634 100% 67
2a07:9440::/29 Valid RIR databaseRIPE 633 100% 67

AS-SET

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

  • Route object: none7
ChangePrefix or setDetailFull-table peers
Route object: none92.119.64.0/24No route object for it. A route object for 92.119.64.0/22 with origin AS202682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202682 in the RIR database for the space.672 of 673
Route object: none92.119.65.0/24No route object for it. A route object for 92.119.64.0/22 with origin AS202682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202682 in the RIR database for the space.672 of 673
Route object: none92.119.66.0/24No route object for it. A route object for 92.119.64.0/22 with origin AS202682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202682 in the RIR database for the space.672 of 673
Route object: none92.119.67.0/24No route object for it. A route object for 92.119.64.0/22 with origin AS202682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202682 in the RIR database for the space.672 of 673
Route object: none185.155.129.0/24No route object for it. A route object for 185.155.128.0/22 with origin AS202682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202682 in the RIR database for the space.672 of 673
Route object: none185.155.130.0/24No route object for it. A route object for 185.155.128.0/22 with origin AS202682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202682 in the RIR database for the space.672 of 673
Route object: none185.155.131.0/24No route object for it. A route object for 185.155.128.0/22 with origin AS202682 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202682 in the RIR database for the space.672 of 673

Route objects not announced

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