CAMIX Yaounde: operator report
Yaoundé, Cameroon · PeeringDB 2554 · ixreport.com/ix/2554/report/
Members of CAMIX Yaounde that PeeringDB has wrong, from its IX-F export (10 networks, read 2026-11-19 12:22 UTC) and its website members list (13 networks, read 2026-11-19 12:22 UTC), against PeeringDB as of 2026-11-19 12:40 UTC. 14 networks to follow up; 4 with a public PeeringDB contact.
Contacts are the networks' public PeeringDB contacts: the peering (policy) contact where there is one, else technical, then NOC. Networks keep these themselves on PeeringDB.
Data: PeeringDB (peeringdb.com), and CAMIX Yaounde's own member lists. Report by IX Report (ixreport.com).
On your lists, missing from PeeringDB (12)
These networks could add CAMIX Yaounde to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
| Network | On your | Addresses | Contact |
|---|---|---|---|
| AS3856 PCH AS3856 | website | – | No public contact |
| AS15169 Google LLC | website | – | No public contact |
| AS20940 Akamai Technologies | website | – | No public contact |
| AS36905 Creolink Communications | IX-F and website | 196.60.6.12 | No public contact |
| AS36912 Orange Cameroun | IX-F and website | 196.60.6.15 | Policy: email address (needs JavaScript) +237699949688 |
| AS37620 AS37620 | website | – | No PeeringDB record |
| AS37718 CAMIX NAP - Serveur de route | IX-F | 196.60.6.1 | Policy: email address (needs JavaScript) +237693600248 |
| AS327741 Infogenie | IX-F | 196.60.6.13 | No PeeringDB record |
| AS327820 SWECOM | website | – | No public contact |
| AS328091 CAMIX Services | IX-F | 196.60.6.2 | Technical: email address (needs JavaScript) +237655008667 |
| AS328123 CAMPOST | IX-F and website | 196.60.6.10 | No PeeringDB record |
| AS328840 ST Digital | website | – | Technical: email address (needs JavaScript) +237242232007email address (needs JavaScript)email address (needs JavaScript) |
Addresses or port speeds that differ (2)
PeeringDB against your IX-F export, for the 4 networks in both. Either the network's PeeringDB record or the export is out of date.
In PeeringDB, not on your lists (0)
Either your lists are missing these networks, or they've left and their PeeringDB record is out of date.
None.