ixreport

Shoprite Checkers

AS328511

Shoprite Checkers (PTY) Ltd

3Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
–Type
SelectivePeering policy
3Using the route servers
3To fix in PeeringDB
0Facilities in PeeringDB

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

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

PeeringDB fix list Printable page · CSV

3 things to fix in Shoprite Checkers's PeeringDB record, from what its exchanges publish: 2 to correct, 1 at exchanges that look shut down. As of 2026-11-19 18:41 UTC.

Make the changes on Shoprite Checkers'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 NAPAfrica IX Cape Town Cape Town, South Africa · PeeringDB 597
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB196.60.71.148196.60.71.148 196.60.71.149
    IPv6 address missing from PeeringDBnone2001:43f8:6d1::71:148 2001:43f8:6d1::71:149
    Port speed differs10G2 × 10G
    • In the entry with IPv4 196.60.71.148: set IPv6 to 2001:43f8:6d1::71:148 (now empty).
    • Add an entry: IPv4 196.60.71.149, IPv6 2001:43f8:6d1::71:149, speed 10000 (10G), RS peer yes.

    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 NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:6d0::77
    • In the entry with IPv4 196.60.8.77: set IPv6 to 2001:43f8:6d0::77 (now empty).

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

Exchanges that look shut down (1)

In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.

  1. South Africa NAPAfrica MAPS Cape Townghost Cape Town, South Africa · PeeringDB 3884

    Only one outside network

    IPv4196.46.25.26
    IPv6–
    Speed1000 Mbps (1G)

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 Shoprite Checkers'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 111G across 3 exchanges.

South Africa NAPAfrica IX Cape Town Cape Town, South Africa 196.60.71.148 10G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs
South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa 196.60.8.77 100G Yes Both IPv6 not in PeeringDB
South Africa NAPAfrica MAPS Cape Townghost Cape Town, South Africa 196.46.25.26 1G Yes PeeringDB

Shoprite Checkers lists no facilities in PeeringDB.