Solutions by STC: PeeringDB fix list
AS9155 · peeringdb.com/net/18564
3 things to fix in Solutions by STC's PeeringDB record, from what its exchanges publish: 2 to correct, 1 to check. As of 2026-10-08 18:53 UTC.
Make the changes on Solutions by STC'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.
-
Problem PeeringDB has The export has IPv4 address in PeeringDB, not in the export 194.54.136.3 194.54.136.30 194.54.136.3 IPv6 address in PeeringDB, not in the export 2a0c:c9c0::3 2a0c:c9c0::30 2a0c:c9c0::3 Port speed differs 2 × 10G 10G - The entry with IPv4 194.54.136.30, IPv6 2a0c:c9c0::30 isn't in the export: delete it if that connection is gone.
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 10G 100G - In the entry with IPv4 185.1.8.118: set Speed to 100000 (100G) (now 10000).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Solutions by STC has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 77.69.248.26 IPv6 2001:1a40:10:0:a500:91:55:1 Speed 1000 Mbps (1G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
From ixreport.com/net/9155/: 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.