bgpreport

Network · data from 2026-11-12

AS37288 West and Central African Research Network

Registry name: West and Central African Research Network - West and Central African Research Network, SN · PeeringDB

1IPv4 routes 0.0% 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
2No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
11Route objects not announced registered with origin AS37288, seen from no peer

Announced routes

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

196.216.188.0/22 No ROA RIR databaseAFRINIC, RADB 673 100% 68
2001:43f8:1d0::/48 No ROA RIR databaseAFRINIC 606 95% 68

AS-SET

PeeringDB's irr_as_set for AS37288: AS-SET-WACREN. 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 (AS37288 isn't in the set, or no route object for AS37288 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 objectsAS37288 in itNot covered
AS-SET-WACREN AFRINIC 415144 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 13 are in fix.csv.

  • ROA: none2
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: none196.216.188.0/22No ROA covers it. Add a ROA for AS37288, maxLength 22.673 of 673
ROA: none2001:43f8:1d0::/48No ROA covers it. Add a ROA for AS37288, maxLength 48.606 of 636

Route objects not announced

Route objects with origin AS37288 whose prefix no peer sees AS37288 announce. Many are kept on purpose (backup routes, space announced only in some places).

102.130.0.0/21RADBNo ROA
102.208.188.0/23RADBNo ROA
102.219.81.0/24RADBNo ROA
154.68.192.0/18RADBNo ROA
164.160.192.0/21RADBNo ROA
196.27.128.0/17RADBNo ROA
196.27.136.0/24RADBNo ROA
196.216.188.0/24RADBNo ROA
196.216.189.0/24RADBNo ROA
196.216.190.0/24RADBNo ROA
196.216.191.0/24RADBNo ROA

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.