ixreport

Salesforce.com: PeeringDB fix list

AS14340 · peeringdb.com/net/1100

PeeringDB

14 things to fix in Salesforce.com's PeeringDB record, from what its exchanges publish: 3 to add, 9 to correct, 2 to check. As of 2026-10-08 22:13 UTC.

Make the changes on Salesforce.com'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 (3)

On the exchange's own member list, but not in Salesforce.com's PeeringDB record. Add one entry per connection with these values.

  1. United States ChIX Chicago, United States · PeeringDB 239From 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.

  2. India DE-CIX Mumbai Mumbai, India · PeeringDB 832From 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.

  3. United States DE-CIX Phoenix Phoenix, United States · PeeringDB 3775From its IX-F export and website members list
    IPv4149.112.27.10
    IPv62001:504:116::3804:0:1
    Speed10000 Mbps (10G)
    RS peerYes

Correct these entries (9)

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. Germany DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 185.1.170.32: set Speed to 100000 (100G) (now 10000).
  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs20G100G
    • In the entry with IPv4 80.81.195.43: set Speed to 100000 (100G) (now 20000).
  3. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 185.1.210.51: set Speed to 100000 (100G) (now 10000).
  4. France DE-CIX Marseille Marseille, France · PeeringDB 1149
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 185.1.47.71: set Speed to 100000 (100G) (now 10000).
  5. Germany DE-CIX Munich Munich, Germany · PeeringDB 248
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 185.1.208.40: set Speed to 100000 (100G) (now 10000).
  6. United States DE-CIX New York New York, United States · PeeringDB 804
    ProblemPeeringDB hasThe export has
    Port speed differs10G200G
    • In the entry with IPv4 206.82.104.188: set Speed to 200000 (200G) (now 10000).
  7. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs10G20G
    • In the entry with IPv4 195.66.227.50: set Speed to 20000 (20G) (now 10000).
  8. United States LINX NoVA Ashburn, Reston, Manassas, United States · PeeringDB 777
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 206.55.196.53: set Speed to 100000 (100G) (now 10000).
  9. United States MASS-IX Boston, United States · PeeringDB 1086
    ProblemPeeringDB hasThe export has
    Port speed differs400M1G
    • In the entry with IPv4 206.53.143.28: set Speed to 1000 (1G) (now 400).

Check these entries (2)

In PeeringDB, but on none of the exchange's own lists. If Salesforce.com has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Japan BBIX Tokyo Tokyo, Japan · PeeringDB 126Not on its website members list
    IPv4101.203.89.72
    IPv62001:de8:c::1:4340:1
    Speed10000 Mbps (10G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

  2. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70Not on its IX-F export
    IPv4194.68.123.150
    IPv62001:7f8:d:ff::150
    Speed10000 Mbps (10G)

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