ixreport

MSTELCOM, SARL: PeeringDB fix list

AS17400 · peeringdb.com/net/8774

PeeringDB

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

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

Add these exchanges (2)

On the exchange's own member list, but not in MSTELCOM, SARL's PeeringDB record. Add one entry per connection with these values.

  1. South Africa NAPAfrica IX Cape Town Cape Town, South Africa · PeeringDB 597From its IX-F export
    IPv4196.60.71.171
    IPv62001:43f8:6d1::71:171
    Speed10000 Mbps (10G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

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.

  1. Angola Angola IXP Luanda, Angola · PeeringDB 421
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:390::b
    Port speed differs1G10G
    • In the entry with IPv4 196.223.1.11: set IPv6 to 2001:43f8:390::b (now empty); set Speed to 10000 (10G) (now 1000).

From ixreport.com/net/17400/: 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.