S3 Company: PeeringDB fix list
AS4849 · peeringdb.com/net/42701
5 things to fix in S3 Company's PeeringDB record, from what its exchanges publish: 4 to correct, 1 to check. As of 2026-10-08 18:53 UTC.
Make the changes on S3 Company'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 (4)
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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 193.169.198.191 193.169.198.191 193.169.199.101 IPv6 address missing from PeeringDB 2001:7f8:58::12f1:0:2 2001:7f8:58::12f1:0:1 2001:7f8:58::12f1:0:2 - In the entry with IPv4 193.169.198.191: set IPv6 to 2001:7f8:58::12f1:0:1 (now 2001:7f8:58::12f1:0:2).
- Add an entry: IPv4 193.169.199.101, IPv6 2001:7f8:58::12f1:0:2.
-
Problem PeeringDB has The export has Port speed differs 3 × 100G + 2 × 10G 3 × 100G + 10G 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.
-
Problem PeeringDB has The export has Port speed differs 100G 10G - In the entry with IPv4 195.66.228.119: set Speed to 10000 (10G) (now 100000).
-
Problem PeeringDB has The export has Port speed differs 100G 10G - In the entry with IPv4 185.1.32.117: set Speed to 10000 (10G) (now 100000).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If S3 Company has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 193.188.137.109 IPv6 – Speed 10000 Mbps (10G)
From ixreport.com/net/4849/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.