KT RWANDA NETWORK: PeeringDB fix list
AS37228 · peeringdb.com/net/29101
One thing to fix in KT RWANDA NETWORK's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on KT RWANDA NETWORK'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 (1)
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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 196.223.12.132 196.223.12.132 196.223.12.153 IPv6 address missing from PeeringDB none 2001:43f8:150::132 2001:43f8:150::153 Port speed differs 10G 2 × 10G - In the entry with IPv4 196.223.12.132: set IPv6 to 2001:43f8:150::132 (now empty).
- Add an entry: IPv4 196.223.12.153, IPv6 2001:43f8:150::153, speed 10000 (10G), RS peer no.
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
From ixreport.com/net/37228/: 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.