LIONEX1: operator report
Lilongwe, Malawi · PeeringDB 4446 · ixreport.com/ix/4446/report/
Members of LIONEX1 that PeeringDB has wrong, from its IX-F export (5 networks, read 2026-10-08 22:05 UTC), against PeeringDB as of 2026-10-08 22:13 UTC. 4 networks to follow up; 1 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 (2)
These networks could add LIONEX1 to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
Addresses or port speeds that differ (1)
PeeringDB against your IX-F export, for the 3 networks in both. Either the network's PeeringDB record or the export is out of date.
| Network | Problem | PeeringDB has | Your export has | Contact |
|---|---|---|---|---|
| AS37187 Skyband | IPv6 address in PeeringDB, not in the export | 2001:43f8:1720::33 | none | No public contact |
In PeeringDB, not on your lists (1)
Either your lists are missing these networks, or they've left and their PeeringDB record is out of date.
| Network | In PeeringDB | Contact |
|---|---|---|
| AS13335 Cloudflare | 196.60.122.40 2001:43f8:1720::40 20G |
Policy: email address (needs JavaScript) +16503198930email address (needs JavaScript) |