ixreport

BitCo

AS37358 · BitCo

7Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
7Using the route servers
3To fix in PeeringDB
3Facilities in PeeringDB

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

3 things to fix in BitCo's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on BitCo'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 (3)

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 CINX Cape Town, South Africa · PeeringDB 344
    ProblemPeeringDB hasThe export has
    Port speed differs10G1G
    • In the entry with IPv4 196.223.22.79: set Speed to 1000 (1G) (now 10000).

    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 JINX Johannesburg, South Africa · PeeringDB 129
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G3 × 1G
    • In the entry with IPv4 196.60.96.128: set Speed to 1000 (1G) (now 10000).
    • In the entry with IPv4 196.60.96.79: set Speed to 1000 (1G) (now 10000).

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

  3. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    Port speed differs40G + 20G100G + 40G
    • In the entry with IPv4 196.60.11.61: set Speed to 100000 (100G) (now 20000).

    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

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

Map

Where BitCo'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 121G across 7 exchanges.

South Africa CINX Cape Town, South Africa 196.223.22.79 2001:43f8:1f1::79 10G 11 routes Both Speed differs
South Africa DINX Durban, South Africa 196.223.30.79 2001:43f8:1f2::79 10G 8 routes Both
South Africa JINX Johannesburg, South Africa 196.60.96.79
196.60.96.128
2001:43f8:1f0::79
2001:43f8:1f0::128
2 × 10G 77 routes Both Speed differs
South Africa JINX Voice Johannesburg, South Africa 196.223.15.28 1G Yes PeeringDB
South Africa NAPAfrica IX Cape Town Cape Town, South Africa 196.60.70.38 2001:43f8:6d1::38 10G 11 routes Both
South Africa NAPAfrica IX Durban Durban, South Africa 196.10.141.74 2001:43f8:6d2::74 10G 8 routes Both
South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa 196.60.8.160
196.60.11.61
2001:43f8:6d0::160
2001:43f8:6d0::11:61
40G + 20G 135 routes Both Speed differs

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

These exchanges have a switch in a facility where BitCo lists itself in PeeringDB, but don't have BitCo 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 (3)

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

South Africa Teraco Johannesburg Campus, South AfricaJohannesburg 3 of 6
South Africa Teraco CT1 Cape Town, South AfricaCape Town 2 of 3
South Africa Teraco DB1 Durban, South AfricaDurban 2 of 2