ixreport

Sky-Connect Internet

AS37675 · Skywire (PTY) LTD

Sky-Connect Internet cc

3Exchanges
1On 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 Sky-Connect Internet? · Where should Sky-Connect Internet peer next? · Compare Sky-Connect Internet 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 Sky-Connect Internet's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Sky-Connect Internet'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 Sky-Connect Internet'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.70
    IPv62001:43f8:6d2::70
    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.

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
    IPv6 address in PeeringDB, not in the export2001:43f8:6d1::192none
    Port speed differs2 × 10G3 × 10G
    • In the entry with IPv4 196.60.70.192: set IPv6 to (empty) (now 2001:43f8:6d1::192).

    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 in PeeringDB, not in the export2001:43f8:6d0::192 2001:43f8:6d0::10:612001:43f8:6d0::10:61
    • In the entry with IPv4 196.60.8.192: set IPv6 to (empty) (now 2001:43f8:6d0::192).

    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 Sky-Connect Internet'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 41G across 3 exchanges.

South Africa NAPAfrica IX Cape Town Cape Town, South Africa 196.60.70.192
196.60.70.252
2001:43f8:6d1::192 2 × 10G 16 routes Both IPv6 not in exportSpeed differs
South Africa NAPAfrica IX Durban Durban, South Africa 196.10.141.70 2001:43f8:6d2::70 1G 1 routes Not in PeeringDB
South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa 196.60.8.192
196.60.10.61
2001:43f8:6d0::192
2001:43f8:6d0::10:61
2 × 10G 23 routes Both IPv6 not in export

Sky-Connect Internet lists no facilities in PeeringDB.