bgpreport

Network · data from 2026-11-12

AS263767 CORPORACIÓN GALA IT

Registry name: AS263767 - CORPORACION GALA IT, C.A., VE · PeeringDB

22IPv4 routes 100.0% RPKI valid · 36.4% with a route object
6IPv6 routes 100.0% RPKI valid · 16.7% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 19 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS263767, seen from no peer

Announced routes

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

38.137.234.0/23 Valid Nonecovered by 38.137.232.0/22 673 100% 67
166.1.68.0/24 Valid Nonecovered by 166.1.68.0/23 673 100% 67
167.250.48.0/24 Valid Nonecovered by 167.250.48.0/22 670 100% 67
167.250.49.0/24 Valid Nonecovered by 167.250.48.0/22 670 100% 67
167.250.51.0/24 Valid Nonecovered by 167.250.48.0/22 670 100% 67
38.76.137.0/24 Valid Nonecovered by 38.76.136.0/22 669 99% 67
38.137.234.0/24 Valid Nonecovered by 38.137.232.0/22 669 99% 67
167.250.48.0/23 Valid Nonecovered by 167.250.48.0/22 667 99% 67
167.250.50.0/23 Valid Nonecovered by 167.250.48.0/22 667 99% 67
167.250.50.0/24 Valid Nonecovered by 167.250.48.0/22 667 99% 67
38.137.235.0/24 Valid Nonecovered by 38.137.232.0/22 666 99% 67
2803:d940:1::/48 Valid Nonecovered by 2803:d940::/32 636 100% 67
2803:d940:200::/40 Valid Nonecovered by 2803:d940::/32 636 100% 67
2803:d940::/48 Valid Nonecovered by 2803:d940::/32 631 99% 68
2803:d940:300::/40 Valid Nonecovered by 2803:d940::/32 631 99% 68
2803:d940:400::/40 Valid Nonecovered by 2803:d940::/32 629 99% 68
38.76.136.0/24 Valid Nonecovered by 38.76.136.0/22 2 0%low visibility 2
38.76.138.0/24 Valid Nonecovered by 38.76.136.0/22 2 0%low visibility 2
38.137.233.0/24 Valid Nonecovered by 38.137.232.0/22 2 0%low visibility 2
38.76.136.0/22 Valid RIR databaseARIN, RADB 673 100% 67
38.137.232.0/22 Valid RIR databaseARIN, RADB 673 100% 67
166.1.68.0/23 Valid RIR databaseARIN, RADB 673 100% 67
166.1.83.0/24 Valid RIR databaseARIN, RADB 673 100% 67
201.10.68.0/22 Valid RIR databaseRIPE 673 100% 67
38.73.226.0/24 Valid RIR databaseARIN, RADB 672 100% 67
45.38.22.0/24 Valid RIR databaseARIN, RADB 672 100% 67
167.250.48.0/22 Valid RIR databaseLACNIC, RADB 670 100% 67
2803:d940::/32 Valid RIR databaseLACNIC 636 100% 67

AS-SET

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

  • Route object: none19
ChangePrefix or setDetailFull-table peers
Route object: none38.137.234.0/23No route object for it. A route object for 38.137.232.0/22 with origin AS263767 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263767 in the RIR database for the space.673 of 673
Route object: none166.1.68.0/24No route object for it. A route object for 166.1.68.0/23 with origin AS263767 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263767 in the RIR database for the space.673 of 673
Route object: none167.250.48.0/24No route object for it. A route object for 167.250.48.0/22 with origin AS263767 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263767 in the RIR database for the space.670 of 673
Route object: none167.250.49.0/24No route object for it. A route object for 167.250.48.0/22 with origin AS263767 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263767 in the RIR database for the space.670 of 673
Route object: none167.250.51.0/24No route object for it. A route object for 167.250.48.0/22 with origin AS263767 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263767 in the RIR database for the space.670 of 673
Route object: none38.76.137.0/24No route object for it. A route object for 38.76.136.0/22 with origin AS263767 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263767 in the RIR database for the space.669 of 673
Route object: none38.137.234.0/24No route object for it. A route object for 38.137.232.0/22 with origin AS263767 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263767 in the RIR database for the space.669 of 673
Route object: none167.250.48.0/23No route object for it. A route object for 167.250.48.0/22 with origin AS263767 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263767 in the RIR database for the space.667 of 673
Route object: none167.250.50.0/23No route object for it. A route object for 167.250.48.0/22 with origin AS263767 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263767 in the RIR database for the space.667 of 673
Route object: none167.250.50.0/24No route object for it. A route object for 167.250.48.0/22 with origin AS263767 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263767 in the RIR database for the space.667 of 673
Route object: none38.137.235.0/24No route object for it. A route object for 38.137.232.0/22 with origin AS263767 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263767 in the RIR database for the space.666 of 673
Route object: none2803:d940:1::/48No route object for it. A route object for 2803:d940::/32 with origin AS263767 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263767 in the RIR database for the space.636 of 636
Route object: none2803:d940:200::/40No route object for it. A route object for 2803:d940::/32 with origin AS263767 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263767 in the RIR database for the space.636 of 636
Route object: none2803:d940::/48No route object for it. A route object for 2803:d940::/32 with origin AS263767 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263767 in the RIR database for the space.631 of 636
Route object: none2803:d940:300::/40No route object for it. A route object for 2803:d940::/32 with origin AS263767 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263767 in the RIR database for the space.631 of 636
Route object: none2803:d940:400::/40No route object for it. A route object for 2803:d940::/32 with origin AS263767 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263767 in the RIR database for the space.629 of 636
Route object: none38.76.136.0/24No route object for it. A route object for 38.76.136.0/22 with origin AS263767 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263767 in the RIR database for the space.2 of 673
Route object: none38.76.138.0/24No route object for it. A route object for 38.76.136.0/22 with origin AS263767 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263767 in the RIR database for the space.2 of 673
Route object: none38.137.233.0/24No route object for it. A route object for 38.137.232.0/22 with origin AS263767 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263767 in the RIR database for the space.2 of 673

Route objects not announced

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