ixreport

RocketNet

AS327849 · directel

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

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

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

PeeringDB fix list Printable page · CSV

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

Make the changes on RocketNet'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 (2)

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 differs2 × 10G2 × 1G
    • In the entry with IPv4 196.223.23.27: set Speed to 1000 (1G) (now 10000).
    • In the entry with IPv4 196.223.23.28: 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 × 10G2 × 1G
    • In the entry with IPv4 196.60.97.27: set Speed to 1000 (1G) (now 10000).
    • In the entry with IPv4 196.60.97.28: 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.

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 RocketNet'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 80G across 4 exchanges.

South Africa CINX Cape Town, South Africa 196.223.23.27
196.223.23.28
2001:43f8:1f1::1:27
2001:43f8:1f1::1:28
2 × 10G 40 routes Both Speed differs
South Africa JINX Johannesburg, South Africa 196.60.97.27
196.60.97.28
2001:43f8:1f0::1:27
2001:43f8:1f0::1:28
2 × 10G 36 routes Both Speed differs
South Africa NAPAfrica IX Cape Town Cape Town, South Africa 196.60.70.120
196.60.71.47
2001:43f8:6d1::120
2001:43f8:6d1::71:47
2 × 10G 40 routes Both
South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa 196.60.8.102
196.60.9.102
2001:43f8:6d0::102
2001:43f8:6d0::9:102
2 × 10G 36 routes Both

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

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

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

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