bgpreport

Network · data from 2026-11-12

AS37140 PPL NET GHANA

Registry name: Airtel Ghana Limited - Airtel Ghana Limited, GH · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS37140, 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.215.162.0/24 Invalid: origin Other origin only 1 0%low visibility 3
196.175.0.0/20 No ROA Other origin onlycovered by 196.175.0.0/18 669 99% 68
196.175.248.0/22 No ROA Other origin only 651 97% 67
41.215.160.0/21 No ROA Other origin only 650 97% 67
196.175.224.0/24 No ROA RIR databaseAFRINIC 669 99% 68
196.175.240.0/22 No ROA RIR databaseAFRINIC 669 99% 68
196.175.248.0/23 No ROA RIR databaseAFRINIC 669 99% 68
196.175.250.0/23 No ROA RIR databaseAFRINIC 669 99% 68
196.175.2.0/24 Valid RIR databaseAFRINIC 669 99% 68
196.175.3.0/24 Valid RIR databaseAFRINIC 669 99% 68
196.175.1.0/24 Valid RIR databaseAFRINIC 668 99% 67

AS-SET

AS37140'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 35 are in fix.csv.

  • ROA: origin1
  • ROA: none7
  • Route object: none4
  • Route object: not announced23
ChangePrefix or setDetailFull-table peers
ROA: origin41.215.162.0/24ROAs covering it name AS37030, not AS37140. If AS37140 should announce it, add a ROA for AS37140.1 of 673
Route object: none41.215.162.0/24Route objects for it name AS37030. Add a route object with origin AS37140 in the RIR database for the space.1 of 673
ROA: none196.175.0.0/20No ROA covers it. Add a ROA for AS37140, maxLength 20.669 of 673
Route object: none196.175.0.0/20Route objects for it name AS37030. A route object for 196.175.0.0/18 with origin AS37140 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37140 in the RIR database for the space.669 of 673
ROA: none196.175.248.0/22No ROA covers it. Add a ROA for AS37140, maxLength 22.651 of 673
Route object: none196.175.248.0/22Route objects for it name AS37030. Add a route object with origin AS37140 in the RIR database for the space.651 of 673
ROA: none41.215.160.0/21No ROA covers it. Add a ROA for AS37140, maxLength 21.650 of 673
Route object: none41.215.160.0/21Route objects for it name AS37030. Add a route object with origin AS37140 in the RIR database for the space.650 of 673
ROA: none196.175.224.0/24No ROA covers it. Add a ROA for AS37140, maxLength 24.669 of 673
ROA: none196.175.240.0/22No ROA covers it. Add a ROA for AS37140, maxLength 22.669 of 673
ROA: none196.175.248.0/23No ROA covers it. Add a ROA for AS37140, maxLength 23.669 of 673
ROA: none196.175.250.0/23No ROA covers it. Add a ROA for AS37140, maxLength 23.669 of 673

Route objects not announced

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

41.190.88.0/22RIPE-NONAUTHNo ROA
45.208.0.0/16AFRINICNo ROA
45.209.0.0/16AFRINICNo ROA
45.210.0.0/15AFRINICNo ROA
45.210.0.0/16AFRINICNo ROA
196.172.0.0/15AFRINICNo ROA
196.174.0.0/17AFRINICNo ROA
196.174.128.0/17AFRINICNo ROA
196.175.0.0/18AFRINICNo ROA
196.175.0.0/24AFRINICValid
196.175.64.0/18AFRINICNo ROA
196.175.128.0/19AFRINICNo ROA
196.175.224.0/23AFRINICNo ROA
196.175.224.0/26AFRINICNo ROA
196.175.224.32/27AFRINICNo ROA
196.175.224.64/26AFRINICNo ROA
196.175.224.96/29AFRINICNo ROA
196.175.224.128/26AFRINICNo ROA
196.175.225.0/24AFRINICNo ROA
196.175.226.0/23AFRINICNo ROA
196.175.252.0/24AFRINICNo ROA
197.190.0.0/16AFRINICNo ROA
197.191.0.0/16AFRINICNo 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.