ixreport

Linux Tech

AS328423 · DcData

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

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

Make the changes on Linux Tech'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 DINX Durban, South Africa · PeeringDB 610
    ProblemPeeringDB hasThe export has
    Port speed differs1.024G10G
    • In the entry with IPv4 196.223.30.213: set Speed to 10000 (10G) (now 1024).

    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 Durban Durban, South Africa · PeeringDB 969
    ProblemPeeringDB hasThe export has
    Port speed differs1.024G10G
    • In the entry with IPv4 196.10.141.54: set Speed to 10000 (10G) (now 1024).

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

  3. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    Port speed differs1.024G1G
    • In the entry with IPv4 196.60.9.212: set Speed to 1000 (1G) (now 1024).

    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 Linux Tech'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 3.072G across 3 exchanges.

South Africa DINX Durban, South Africa 196.223.30.213 2001:43f8:1f2::213 1.024G 5 routes Both Speed differs
South Africa NAPAfrica IX Durban Durban, South Africa 196.10.141.54 2001:43f8:6d2::54 1.024G 5 routes Both Speed differs
South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa 196.60.9.212 2001:43f8:6d0::9:212 1.024G 5 routes Both Speed differs

Linux Tech lists no facilities in PeeringDB.