bgpreport

Network · data from 2026-11-12

AS37526 TELECEL FASO

Registry name: TELECEL FASO - TELECEL FASO, BF · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS37526, 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.
2c0f:f8b0::/32 No ROA Other IRR onlyRADB 635 100% 70
105.235.178.0/24 No ROA RIR databaseAFRINIC 673 100% 67
105.235.188.0/24 No ROA RIR databaseAFRINIC 673 100% 67
105.235.191.0/24 No ROA RIR databaseAFRINIC 673 100% 67
105.235.176.0/20 No ROA RIR databaseAFRINIC, RADB 671 100% 68
105.235.176.0/24 No ROA RIR databaseAFRINIC 671 100% 68
105.235.177.0/24 No ROA RIR databaseAFRINIC 671 100% 68
105.235.183.0/24 No ROA RIR databaseAFRINIC 671 100% 68
105.235.185.0/24 No ROA RIR databaseAFRINIC 671 100% 68
105.235.187.0/24 No ROA RIR databaseAFRINIC 671 100% 68
105.235.189.0/24 No ROA RIR databaseAFRINIC 671 100% 68
105.235.190.0/24 No ROA RIR databaseAFRINIC 671 100% 68

AS-SET

AS37526'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 20 are in fix.csv.

  • ROA: none12
  • Route object: RIR1
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none2c0f:f8b0::/32No ROA covers it. Add a ROA for AS37526, maxLength 32.635 of 636
Route object: RIR2c0f:f8b0::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none105.235.178.0/24No ROA covers it. Add a ROA for AS37526, maxLength 24.673 of 673
ROA: none105.235.188.0/24No ROA covers it. Add a ROA for AS37526, maxLength 24.673 of 673
ROA: none105.235.191.0/24No ROA covers it. Add a ROA for AS37526, maxLength 24.673 of 673
ROA: none105.235.176.0/20No ROA covers it. Add a ROA for AS37526, maxLength 20.671 of 673
ROA: none105.235.176.0/24No ROA covers it. Add a ROA for AS37526, maxLength 24.671 of 673
ROA: none105.235.177.0/24No ROA covers it. Add a ROA for AS37526, maxLength 24.671 of 673
ROA: none105.235.183.0/24No ROA covers it. Add a ROA for AS37526, maxLength 24.671 of 673
ROA: none105.235.185.0/24No ROA covers it. Add a ROA for AS37526, maxLength 24.671 of 673
ROA: none105.235.187.0/24No ROA covers it. Add a ROA for AS37526, maxLength 24.671 of 673
ROA: none105.235.189.0/24No ROA covers it. Add a ROA for AS37526, maxLength 24.671 of 673
ROA: none105.235.190.0/24No ROA covers it. Add a ROA for AS37526, maxLength 24.671 of 673

Route objects not announced

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

105.235.176.0/32AFRINICNo ROA
105.235.179.0/24AFRINICNo ROA
105.235.180.0/24AFRINICNo ROA
105.235.181.0/24AFRINICNo ROA
105.235.182.0/24AFRINICNo ROA
105.235.184.0/24AFRINICNo ROA
105.235.186.0/24AFRINICNo 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.