bgpreport

Network · data from 2026-11-12

AS37529 Gestor de Infraestructuras de Telecomunicaciones de Guinea Ecuatorial

Registry name: Gestora de Infraestructuras de Telecomunicaciones de Guinea Ecuatorial - Gestora de Infraestructuras de Telecomunicaciones de Guinea Ecuatorial, GQ · PeeringDB

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

Announced routes

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

102.213.52.0/23 No ROA RIR databaseAFRINIC 669 99% 68
169.239.112.0/22 No ROA RIR databaseAFRINIC 669 99% 68
102.164.248.0/22 Valid Other origin only 669 99% 68
197.214.64.0/20 Valid RIR databaseAFRINIC, RIPE-NONAUTH 671 100% 68
2c0f:f8c0::/32 Valid RIR databaseAFRINIC 634 100% 68

AS-SET

PeeringDB's irr_as_set for AS37529: AS-SET-GITGE. 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 (AS37529 isn't in the set, or no route object for AS37529 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 objectsAS37529 in itNot covered
AS-SET-GITGE AFRINIC 11169 Yes 1

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

  • ROA: none2
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none102.213.52.0/23No ROA covers it. Add a ROA for AS37529, maxLength 23.669 of 673
ROA: none169.239.112.0/22No ROA covers it. Add a ROA for AS37529, maxLength 22.669 of 673
Route object: none102.164.248.0/22Route objects for it name AS328311. Add a route object with origin AS37529 in the RIR database for the space.669 of 673

Route objects not announced

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