ixreport

Amobia Communications

AS37266 · Amobia

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
3To fix in PeeringDB
3Facilities in PeeringDB

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

3 things to fix in Amobia Communications's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on Amobia Communications'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 NAPAfrica IX Cape Town Cape Town, South Africa · PeeringDB 597
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:6d1::34
    • In the entry with IPv4 196.60.70.34: set IPv6 to 2001:43f8:6d1::34 (now empty).

    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.

  2. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:6d0::66 2001:43f8:6d0::227
    • In the entry with IPv4 196.60.8.227: set IPv6 to 2001:43f8:6d0::227 (now empty).
    • In the entry with IPv4 196.60.8.66: set IPv6 to 2001:43f8:6d0::66 (now empty).

    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.

  3. South Africa NMBINX Gqeberha, South Africa · PeeringDB 4148
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:690::24
    • In the entry with IPv4 196.60.120.24: set IPv6 to 2001:43f8:690::24 (now empty).

    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 Amobia Communications'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 50G across 4 exchanges.

South Africa CINX Cape Town, South Africa 196.223.22.24 2001:43f8:1f1::24 10G 19 routes Both
South Africa NAPAfrica IX Cape Town Cape Town, South Africa 196.60.70.34 10G 17 routes Both IPv6 not in PeeringDB
South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa 196.60.8.66
196.60.8.227
2 × 10G 23 routes Both IPv6 not in PeeringDB
South Africa NMBINX Gqeberha, South Africa 196.60.120.24 10G 5 routes Both IPv6 not in PeeringDB

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

These exchanges have a switch in a facility where Amobia Communications lists itself in PeeringDB, but don't have Amobia Communications 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 Amobia Communications 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
South Africa OADC, Port ElizabethGqeberha 1 of 1