bgpreport

Network · data from 2026-11-12

AS64131 GLOBALCONNECT

Registry name: AS64131 - GLOBALCONNECT SPA, CL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS64131, 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.
200.24.124.0/24 Valid Nonecovered by 200.24.124.0/22 12 2%low visibility 8
200.24.126.0/24 Valid Nonecovered by 200.24.124.0/22 12 2%low visibility 8
200.24.127.0/24 Valid Nonecovered by 200.24.124.0/22 12 2%low visibility 8
167.249.30.0/24 Valid Other IRR onlyRADB 109 16% 41
167.249.31.0/24 Valid Other IRR onlyRADB 109 16% 41
167.249.30.0/23 Valid RIR databaseLACNIC, RADB 672 100% 66
200.24.124.0/22 Valid RIR databaseLACNIC 672 100% 66
2803:6a10::/32 Valid RIR databaseLACNIC 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS64131: AS64131:AS-ALL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS64131 isn't in the set, or no route object for AS64131 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS64131 in itNot covered
AS64131:AS-ALL LACNIC 61059 Yes 0

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

  • Route object: none3
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
Route object: none200.24.124.0/24No route object for it. A route object for 200.24.124.0/22 with origin AS64131 covers it (filters allowing more-specifics accept it). Add a route object with origin AS64131 in the RIR database for the space.12 of 673
Route object: none200.24.126.0/24No route object for it. A route object for 200.24.124.0/22 with origin AS64131 covers it (filters allowing more-specifics accept it). Add a route object with origin AS64131 in the RIR database for the space.12 of 673
Route object: none200.24.127.0/24No route object for it. A route object for 200.24.124.0/22 with origin AS64131 covers it (filters allowing more-specifics accept it). Add a route object with origin AS64131 in the RIR database for the space.12 of 673
Route object: RIR167.249.30.0/24Route object only in RADB. Add it in the RIR database for the space.109 of 673
Route object: RIR167.249.31.0/24Route object only in RADB. Add it in the RIR database for the space.109 of 673

Route objects not announced

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