Ciudad: PeeringDB fix list

AS328722 · peeringdb.com/net/27654

2 things to fix in Ciudad's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on Ciudad's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Correct these entries (2)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

IXPN Abuja Abuja, Nigeria · PeeringDB 1870

Problem PeeringDB has The export has

IPv6 address missing from PeeringDB none 2001:43f8:bb1:150::39 2001:43f8:bb1:150::136
Port speed differs 1G 2 × 1G
- In the entry with IPv4 196.216.150.39: set IPv6 to 2001:43f8:bb1:150::39 (now empty).
- Add an entry: IPv4 –, IPv6 2001:43f8:bb1:150::136, speed 1000 (1G), RS peer yes.
IXPN Lagos Lagos, Nigeria · PeeringDB 488

Problem PeeringDB has The export has

Port speed differs 10G 3 × 10G

Problem	PeeringDB has	The export has
IPv6 address missing from PeeringDB	none	2001:43f8:bb1:150::39 2001:43f8:bb1:150::136
Port speed differs	1G	2 × 1G

Problem	PeeringDB has	The export has
Port speed differs	10G	3 × 10G

From ixreport.com/net/328722/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.