ixreport

WECOM

AS37731 · WECOM

Wecom Holdings (Pty) Ltd

6Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
NSPType
OpenPeering policy
6Using the route servers
1To fix in PeeringDB
13Facilities in PeeringDB

Tools: Where can I peer with WECOM? · Where should WECOM peer next? · Compare WECOM with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in WECOM's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on WECOM'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.

  1. South Africa NAPAfrica IX Cape Town Cape Town, South Africa · PeeringDB 597
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G + 10G

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

Exchanges over time

0246Oct 3, 2026Nov 19, 20266
Show as a table
DateExchanges
Nov 19, 20266
Nov 18, 20266
Nov 17, 20266
Nov 16, 20266
Nov 15, 20266
Nov 14, 20266
Nov 13, 20266
Nov 12, 20266
Nov 11, 20266
Nov 10, 20266
Nov 9, 20266
Nov 8, 20266
Nov 7, 20266
Nov 6, 20266
Nov 5, 20266
Nov 4, 20266
Nov 3, 20266
Nov 2, 20266
Nov 1, 20266
Oct 31, 20266
Oct 30, 20266
Oct 29, 20266
Oct 28, 20266
Oct 27, 20266
Oct 26, 20266
Oct 25, 20266
Oct 24, 20266
Oct 23, 20266
Oct 22, 20266
Oct 21, 20266
Oct 20, 20266
Oct 19, 20266
Oct 18, 20266
Oct 17, 20266
Oct 16, 20266
Oct 15, 20266
Oct 14, 20266
Oct 13, 20266
Oct 12, 20266
Oct 11, 20266
Oct 10, 20266
Oct 9, 20266
Oct 8, 20266
Oct 7, 20266
Oct 6, 20266
Oct 5, 20266
Oct 4, 20266
Oct 3, 20266

Map

Where WECOM's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 70G across 6 exchanges.

South Africa CINX Cape Town, South Africa 196.223.23.69 2001:43f8:1f1::1:69 10G 126 routes Both
South Africa DINX Durban, South Africa 196.223.31.69 2001:43f8:1f2::1:69 10G 159 routes Both
South Africa JINX Johannesburg, South Africa 196.60.97.48 2001:43f8:1f0::1:48 10G 159 routes Both
South Africa NAPAfrica IX Cape Town Cape Town, South Africa 196.60.71.97 2001:43f8:6d1::71:97 10G 160 routes Both Speed differs
South Africa NAPAfrica IX Durban Durban, South Africa 196.10.141.124 2001:43f8:6d2::124 10G 159 routes Both
South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa 196.60.10.176
196.60.11.67
2001:43f8:6d0::10:176
2001:43f8:6d0::11:67
2 × 10G 318 routes Both

Exchanges in its buildings that it isn't on (5)

These exchanges have a switch in a facility where WECOM lists itself in PeeringDB, but don't have WECOM as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Facilities (13)

The buildings WECOM lists in PeeringDB, and how many of the exchanges in each it's on.