bgpreport

Network · data from 2026-11-12

AS37136 Etisalat Benin

Registry name: ETISALAT BENIN - ETISALAT BENIN, BJ · PeeringDB

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

Announced routes

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

41.138.88.0/23 Valid Nonecovered by 41.138.88.0/22 673 100% 67
41.138.88.0/24 Valid Nonecovered by 41.138.88.0/22 673 100% 67
41.138.89.0/24 Valid Nonecovered by 41.138.88.0/22 673 100% 67
41.138.90.0/23 Valid Nonecovered by 41.138.88.0/22 673 100% 67
41.138.90.0/24 Valid Nonecovered by 41.138.88.0/22 673 100% 67
41.138.91.0/24 Valid Nonecovered by 41.138.88.0/22 673 100% 67
156.0.212.0/23 Valid Nonecovered by 156.0.212.0/22 673 100% 67
156.0.215.0/24 Valid Nonecovered by 156.0.212.0/22 673 100% 67
156.0.212.0/24 Valid Nonecovered by 156.0.212.0/22 671 100% 68
156.0.213.0/24 Valid Nonecovered by 156.0.212.0/22 671 100% 68
41.138.88.0/22 Valid RIR databaseAFRINIC 673 100% 67

AS-SET

PeeringDB's irr_as_set for AS37136: AS-ETISALAT. 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 (AS37136 isn't in the set, or no route object for AS37136 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 objectsAS37136 in itNot covered
AS-ETISALAT In no IRR database read today.

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

  • Route object: none10
  • AS-SET: not found1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none41.138.88.0/23No route object for it. A route object for 41.138.88.0/22 with origin AS37136 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37136 in the RIR database for the space.673 of 673
Route object: none41.138.88.0/24No route object for it. A route object for 41.138.88.0/22 with origin AS37136 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37136 in the RIR database for the space.673 of 673
Route object: none41.138.89.0/24No route object for it. A route object for 41.138.88.0/22 with origin AS37136 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37136 in the RIR database for the space.673 of 673
Route object: none41.138.90.0/23No route object for it. A route object for 41.138.88.0/22 with origin AS37136 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37136 in the RIR database for the space.673 of 673
Route object: none41.138.90.0/24No route object for it. A route object for 41.138.88.0/22 with origin AS37136 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37136 in the RIR database for the space.673 of 673
Route object: none41.138.91.0/24No route object for it. A route object for 41.138.88.0/22 with origin AS37136 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37136 in the RIR database for the space.673 of 673
Route object: none156.0.212.0/23No route object for it. A route object for 156.0.212.0/22 with origin AS37136 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37136 in the RIR database for the space.673 of 673
Route object: none156.0.215.0/24No route object for it. A route object for 156.0.212.0/22 with origin AS37136 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37136 in the RIR database for the space.673 of 673
Route object: none156.0.212.0/24No route object for it. A route object for 156.0.212.0/22 with origin AS37136 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37136 in the RIR database for the space.671 of 673
Route object: none156.0.213.0/24No route object for it. A route object for 156.0.212.0/22 with origin AS37136 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37136 in the RIR database for the space.671 of 673
AS-SET: not foundAS-ETISALATPeeringDB names AS-ETISALAT; no IRR database read has it.

Route objects not announced

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

156.0.212.0/22AFRINICValid

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.