ixreport

Ax-net

AS328361 · Ax-net

Amax Electronics Pty Ltd

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

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

Make the changes on Ax-net's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (1)

On the exchange's own member list, but not in Ax-net's PeeringDB record. Add one entry per connection with these values.

  1. South Africa CINX Cape Town, South Africa · PeeringDB 344From its IX-F export
    IPv4196.223.23.170
    IPv62001:43f8:1f1::1:170
    Speed1000 Mbps (1G)
    RS peerYes

    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

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

Map

Where Ax-net'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 21G across 3 exchanges.

South Africa CINX Cape Town, South Africa 196.223.23.170 2001:43f8:1f1::1:170 1G 4 routes Not in PeeringDB
South Africa NAPAfrica IX Cape Town Cape Town, South Africa 196.60.71.167 2001:43f8:6d1::71:167 10G 4 routes Both
South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa 196.60.9.156 2001:43f8:6d0::9:156 10G 4 routes Both

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

These exchanges have a switch in a facility where Ax-net lists itself in PeeringDB, but don't have Ax-net 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 Ax-net 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 2 of 3