ixreport

Go Communications Network

AS328051 · Go Connect

Go Communications Network (Pty) LTD

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

Tools: Where can I peer with Go Communications Network? · Where should Go Communications Network peer next? · Compare Go Communications Network 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 Go Communications Network's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on Go Communications 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.

  1. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    IPv6 address in PeeringDB, not in the export2001:43f8:6d0::180 2001:43f8:6d0::10:1922001:43f8:6d0::10:192
    • In the entry with IPv4 196.60.8.180: set IPv6 to (empty) (now 2001:43f8:6d0::180).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

Exchanges over time

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

Map

Where Go Communications Network'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 32G across 4 exchanges.

South Africa DINX Durban, South Africa 196.223.30.237 2001:43f8:1f2::237 1G 1 routes Both
South Africa NAPAfrica IX Cape Town Cape Town, South Africa 196.60.70.217 2001:43f8:6d1::217 10G Yes Both
South Africa NAPAfrica IX Durban Durban, South Africa 196.10.141.99 2001:43f8:6d2::99 1G 1 routes Both
South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa 196.60.8.180
196.60.10.192
2001:43f8:6d0::180
2001:43f8:6d0::10:192
2 × 10G 7 routes Both IPv6 not in export

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

These exchanges have a switch in a facility where Go Communications Network lists itself in PeeringDB, but don't have Go Communications Network 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 Go Communications Network lists in PeeringDB, and how many of the exchanges in each it's on.

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