Harare IX: operator report
Harare, Zimbabwe · PeeringDB 2617 · ixreport.com/ix/2617/report/
Members of Harare IX that PeeringDB has wrong, from its IX-F export (13 networks, read 2026-10-08 18:46 UTC), against PeeringDB as of 2026-10-08 18:53 UTC. 13 networks to follow up; 3 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.
On your lists, missing from PeeringDB (11)
These networks could add Harare IX to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
| Network | On your | Addresses | Contact |
|---|---|---|---|
| AS42 PCH AS42 | IX-F | 196.60.44.17 2001:43f8:310::17 1G |
No public contact |
| AS112 DNS-OARC-112 | IX-F | 196.60.44.4 2001:43f8:310::4 1G |
Technical: email address (needs JavaScript) |
| AS3856 PCH AS3856 | IX-F | 196.60.44.18 2001:43f8:310::18 1G |
No public contact |
| AS30844 Liquid Intelligent Technologies | IX-F | 196.60.44.13 2001:43f8:310::13 1G |
No public contact |
| AS36986 Africom | IX-F | 196.60.44.15 2001:43f8:310::15 1G |
Technical: email address (needs JavaScript) 2638644004078 |
| AS37123 Telecontract Pvt Ltd | IX-F | 196.60.44.16 2001:43f8:310::16 1G |
No public contact |
| AS37183 Utande Internet Services | IX-F | 196.60.44.12 2001:43f8:310::12 1G |
No public contact |
| AS37184 Powertel Communications | IX-F | 196.60.44.14 2001:43f8:310::14 1G |
No public contact |
| AS37204 Telone Zimbabwe | IX-F | 196.60.44.11 2001:43f8:310::11 1G |
Technical: email address (needs JavaScript) +263242799801 |
| AS37355 Harare IX Route Servers | IX-F | 196.60.44.1 196.60.44.2 2001:43f8:310::1 2001:43f8:310::2 2 × 1G |
No PeeringDB record |
| AS328235 ZINX | IX-F | 196.60.44.3 2001:43f8:310::3 1G |
No public contact |
Addresses or port speeds that differ (2)
PeeringDB against your IX-F export, for the 2 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.