Go Communications Network
AS328051 · Go Connect
Go Communications Network (Pty) LTD
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.
-
Problem PeeringDB has The export has IPv6 address in PeeringDB, not in the export 2001:43f8:6d0::180 2001:43f8:6d0::10:192 2001: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
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 4 |
| Nov 18, 2026 | 4 |
| Nov 17, 2026 | 4 |
| Nov 16, 2026 | 4 |
| Nov 15, 2026 | 4 |
| Nov 14, 2026 | 4 |
| Nov 13, 2026 | 4 |
| Nov 12, 2026 | 4 |
| Nov 11, 2026 | 4 |
| Nov 10, 2026 | 4 |
| Nov 9, 2026 | 4 |
| Nov 8, 2026 | 4 |
| Nov 7, 2026 | 4 |
| Nov 6, 2026 | 4 |
| Nov 5, 2026 | 4 |
| Nov 4, 2026 | 4 |
| Nov 3, 2026 | 4 |
| Nov 2, 2026 | 4 |
| Nov 1, 2026 | 4 |
| Oct 31, 2026 | 4 |
| Oct 30, 2026 | 4 |
| Oct 29, 2026 | 4 |
| Oct 28, 2026 | 4 |
| Oct 27, 2026 | 4 |
| Oct 26, 2026 | 4 |
| Oct 25, 2026 | 4 |
| Oct 24, 2026 | 4 |
| Oct 23, 2026 | 4 |
| Oct 22, 2026 | 4 |
| Oct 21, 2026 | 4 |
| Oct 20, 2026 | 4 |
| Oct 19, 2026 | 4 |
| Oct 18, 2026 | 4 |
| Oct 17, 2026 | 4 |
| Oct 16, 2026 | 4 |
| Oct 15, 2026 | 4 |
| Oct 14, 2026 | 4 |
| Oct 13, 2026 | 4 |
| Oct 12, 2026 | 4 |
| Oct 11, 2026 | 4 |
| Oct 10, 2026 | 4 |
| Oct 9, 2026 | 4 |
| Oct 8, 2026 | 4 |
| Oct 7, 2026 | 4 |
| Oct 6, 2026 | 4 |
| Oct 5, 2026 | 4 |
| Oct 4, 2026 | 4 |
| Oct 3, 2026 | 4 |
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.
| DINX Durban, South Africa | 1G | Both | |
| NAPAfrica IX Cape Town Cape Town, South Africa | 10G | Both | |
| NAPAfrica IX Durban Durban, South Africa | 1G | Both | |
| NAPAfrica IX Johannesburg Johannesburg, South Africa | 2 × 10G | Both IPv6 not in export |
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.
| JINXJohannesburg, South Africa | 215 | |
| NetIXSofia, Bulgaria | 204 | |
| CINXCape Town, South Africa | 128 | |
| NAPAfrica MAPS JohannesburgJohannesburg, South Africa | 31 | |
| Global Peer ExchangeWashington, United States | 6 | |
| JINX VoiceJohannesburg, South Africa | 4 |
Facilities (3)
The buildings Go Communications Network lists in PeeringDB, and how many of the exchanges in each it's on.
| Teraco Johannesburg Campus, South AfricaJohannesburg | 1 of 6 | |
| Teraco CT1 Cape Town, South AfricaCape Town | 1 of 3 | |
| Teraco DB1 Durban, South AfricaDurban | 2 of 2 |