ixreport

SoftLayer Technologies, Inc. (an IBM Company): PeeringDB fix list

AS36351 · peeringdb.com/net/1613

PeeringDB

8 things to fix in SoftLayer Technologies, Inc. (an IBM Company)'s PeeringDB record, from what its exchanges publish: 2 to add, 6 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on SoftLayer Technologies, Inc. (an IBM Company)'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 (2)

On the exchange's own member list, but not in SoftLayer Technologies, Inc. (an IBM Company)'s PeeringDB record. Add one entry per connection with these values.

  1. United States Any2East Washington DC, Reston, Boston, New York, Atlanta, United States · PeeringDB 204From its website members list
    IPv4206.51.40.132
    IPv62001:504:13:1::132
    SpeedNot published
    RS peerNot published
  2. Japan JPIX TOKYO Tokyo, Japan · PeeringDB 30From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

Correct these entries (6)

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. Netherlands AMS-IX Amsterdam, Netherlands · PeeringDB 26
    ProblemPeeringDB hasThe export has
    Port speed differs40G80G
    • In the entry with IPv4 80.249.210.82: set Speed to 80000 (80G) (now 40000).

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

  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs200G + 40G2 × 200G
    • In the entry with IPv4 80.81.194.167: set Speed to 200000 (200G) (now 40000).
  3. United States DE-CIX New York New York, United States · PeeringDB 804
    ProblemPeeringDB hasThe export has
    Port speed differs20G100G
    • In the entry with IPv4 206.82.104.149: set Speed to 100000 (100G) (now 20000).
  4. Australia IX Australia Melbourne (VIC-IX) Melbourne, Australia · PeeringDB 513
    ProblemPeeringDB hasThe export has
    Port speed differs10G20G
    • In the entry with IPv4 218.100.78.56: set Speed to 20000 (20G) (now 10000).

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

  5. Italy MIX-IT Milan, Italy · PeeringDB 35
    ProblemPeeringDB hasThe export has
    Port speed differs10G20G
    • In the entry with IPv4 217.29.66.47: set Speed to 20000 (20G) (now 10000).
  6. Czechia NIX.CZ Prague, Czechia · PeeringDB 71
    ProblemPeeringDB hasThe export has
    Port speed differs20G + 10G20G
    • In the entry with IPv4 91.210.16.203: set Speed to 20000 (20G) (now 10000).

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

From ixreport.com/net/36351/: 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.