ixreport

MUBVUMELA

AS328916 · MBVIT

MUBVUMELA CORPORATION 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
2To fix in PeeringDB
2Facilities in PeeringDB

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

Make the changes on MUBVUMELA'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 MUBVUMELA's PeeringDB record. Add one entry per connection with these values.

  1. South Africa NAPAfrica IX Durban Durban, South Africa · PeeringDB 969From its IX-F export
    IPv4196.10.141.100
    IPv62001:43f8:6d2::100
    Speed10000 Mbps (10G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

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
    Port speed differs10G30G
    • In the entry with IPv4 196.60.10.226: set Speed to 30000 (30G) (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

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 MUBVUMELA'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 30G across 3 exchanges.

South Africa NAPAfrica IX Cape Town Cape Town, South Africa 196.60.70.184 2001:43f8:6d1::184 10G Yes Both
South Africa NAPAfrica IX Durban Durban, South Africa 196.10.141.100 2001:43f8:6d2::100 10G Yes Not in PeeringDB
South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa 196.60.10.226 2001:43f8:6d0::10:226 10G 4 routes Both Speed differs

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

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