ixreport

Amazon.com: PeeringDB fix list

AS16509 · peeringdb.com/net/1418

PeeringDB

34 things to fix in Amazon.com's PeeringDB record, from what its exchanges publish: 11 to add, 22 to correct, 1 to check. As of 2026-10-08 22:13 UTC.

Make the changes on Amazon.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 (11)

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

  1. Ukraine 1-IX UA Kyiv, Ukraine · PeeringDB 3562From 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. Hong Kong AMS-IX Hong Kong Hong Kong, Hong Kong · PeeringDB 577From its IX-F export

    2 connections, so 2 entries:

    IPv4103.247.139.10
    IPv62001:df0:296::a501:6509:1
    Speed10000 Mbps (10G)
    RS peerNo
    IPv4103.247.139.74
    IPv62001:df0:296::a501:6509:2
    Speed10000 Mbps (10G)
    RS peerNo

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

  3. India AMS-IX Mumbai Mumbai, India · PeeringDB 1623From its IX-F export

    2 connections, so 2 entries:

    IPv4223.31.200.29
    IPv62001:e48:44:100b:0:a501:6509:2
    Speed10000 Mbps (10G)
    RS peerNo
    IPv4223.31.200.30
    IPv62001:e48:44:100b:0:a501:6509:1
    Speed10000 Mbps (10G)
    RS peerNo

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

  4. Singapore AMS-IX Singapore Singapore, Singapore · PeeringDB 3800From its IX-F export

    2 connections, so 2 entries:

    IPv4112.137.24.160
    IPv62a00:8422:ae5::a501:6509:2
    Speed10000 Mbps (10G)
    RS peerNo
    IPv4112.137.24.238
    IPv62a00:8422:ae5::a501:6509:1
    Speed10000 Mbps (10G)
    RS peerNo

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

  5. United States DE-CIX Houston Houston, United States · PeeringDB 4599From its IX-F export and website members list

    2 connections, so 2 entries:

    IPv4149.112.113.3
    IPv62001:504:13f::407d:0:1
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4149.112.113.4
    IPv62001:504:13f::407d:0:2
    Speed100000 Mbps (100G)
    RS peerYes
  6. Portugal DE-CIX Lisbon Lisbon, Portugal · PeeringDB 2531From its IX-F export and website members list
    IPv4185.1.131.34
    IPv62001:7f8:d5::407d:0:1
    Speed20000 Mbps (20G)
    RS peerYes
  7. Italy DE-CIX Palermo Palermo, Italy · PeeringDB 1131From its IX-F export and website members list
    IPv4185.1.46.9
    IPv62001:7f8:32::407d:0:1
    Speed40000 Mbps (40G)
    RS peerYes
  8. Australia IX Australia Canberra (ACT-IX) Canberra, Australia · PeeringDB 976From its IX-F export

    2 connections, so 2 entries:

    IPv4218.100.54.134
    IPv62001:7fa:11:5:0:407d:0:1
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4218.100.54.135
    IPv62001:7fa:11:5:0:407d:0:2
    Speed10000 Mbps (10G)
    RS peerYes

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

  9. Sweden Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden · PeeringDB 2847From its IX-F export
    IPv4195.69.119.47
    IPv62001:7f8:d:fb::47
    SpeedNot published
    RS peerNo
  10. Sweden Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden · PeeringDB 2845From its IX-F export
    IPv4195.245.240.47
    IPv62001:7f8:d:fc::47
    SpeedNot published
    RS peerNo
  11. Greece SEECIX Athens, Greece · PeeringDB 3184From its IX-F export and website members list
    IPv4185.1.172.3
    IPv62001:7f8:f5::407d:0:1
    Speed20000 Mbps (20G)
    RS peerYes

Correct these entries (22)

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 differs2 × 600G600G + 2 × 400G
    • In the entry with IPv4 80.249.210.100: set Speed to 400000 (400G) (now 600000).
    • In the entry with IPv4 80.249.210.217: set Speed to 400000 (400G) (now 600000).

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

  2. Germany BCIX Berlin, Germany · PeeringDB 87
    ProblemPeeringDB hasThe export has
    Port speed differs200G + 100G2 × 400G
    • In the entry with IPv4 193.178.185.195: set Speed to 400000 (400G) (now 100000).
    • In the entry with IPv4 193.178.185.95: set Speed to 400000 (400G) (now 200000).

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

  3. Canada CANIX Montreal Montreal, Canada · PeeringDB 355
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 40G2 × 200G
    • In the entry with IPv4 198.179.18.60: set Speed to 200000 (200G) (now 40000).
    • In the entry with IPv4 198.179.18.74: set Speed to 200000 (200G) (now 40000).

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

  4. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 800G2 × 1.2T
    • In the entry with IPv4 80.81.194.152: set Speed to 1200000 (1.2T) (now 800000).
    • In the entry with IPv4 80.81.195.152: set Speed to 1200000 (1.2T) (now 800000).
  5. Spain DE-CIX Madrid Madrid, Spain · PeeringDB 1277
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G2 × 400G
    • In the entry with IPv4 185.1.192.214: set Speed to 400000 (400G) (now 100000).
    • In the entry with IPv4 185.1.192.95: set Speed to 400000 (400G) (now 100000).
  6. France DE-CIX Marseille Marseille, France · PeeringDB 1149
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G2 × 400G
    • In the entry with IPv4 185.1.47.115: set Speed to 400000 (400G) (now 100000).
    • In the entry with IPv4 185.1.47.48: set Speed to 400000 (400G) (now 100000).
  7. India Extreme IX Pune Pune, India · PeeringDB 4805
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G4 × 100G
  8. Indonesia IIX-Jakarta Jakarta, Indonesia · PeeringDB 210
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G10G
    • In the entry with IPv4 123.108.9.180: set Speed to 10000 (10G) (now 100000).
    • In the entry with IPv4 123.108.9.182: set Speed to 10000 (10G) (now 100000).

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

  9. United States KCIX Kansas City, United States · PeeringDB 249
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G2 × 400G
    • In the entry with IPv4 206.51.7.131: set Speed to 400000 (400G) (now 100000).
    • In the entry with IPv4 206.51.7.194: set Speed to 400000 (400G) (now 100000).
  10. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321
    ProblemPeeringDB hasThe export has
    Port speed differs400G500G
    • In the entry with IPv4 195.66.237.175: set Speed to 500000 (500G) (now 400000).
  11. Philippines Maharlika IX Manila, Philippines · PeeringDB 4167
    ProblemPeeringDB hasThe export has
    IPv4 address differs103.121.64.36 103.121.64.37163.223.201.36 163.223.201.37
    IPv6 address differs2400:efa0::1:6509:1 2400:efa0::1:6509:22001:df0:a940::1:6509:1 2001:df0:a940::1:6509:2
    • The entry with IPv4 103.121.64.36, IPv6 2400:efa0::1:6509:1 isn't in the export: delete it if that connection is gone.
    • The entry with IPv4 103.121.64.37, IPv6 2400:efa0::1:6509:2 isn't in the export: delete it if that connection is gone.
    • Add an entry: IPv4 163.223.201.37, IPv6 2001:df0:a940::1:6509:2, speed 100000 (100G), RS peer yes.
    • Add an entry: IPv4 163.223.201.36, IPv6 2001:df0:a940::1:6509:1, speed 100000 (100G), RS peer yes.
  12. United States MASS-IX Boston, United States · PeeringDB 1086
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G2 × 100G
    • In the entry with IPv4 206.53.143.52: set Speed to 100000 (100G) (now 10000).
    • In the entry with IPv4 206.53.143.53: set Speed to 100000 (100G) (now 10000).
  13. United States MICE Minneapolis, MN, United States · PeeringDB 446
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G2 × 800G
    • In the entry with IPv4 206.108.255.111: set Speed to 800000 (800G) (now 100000).
    • In the entry with IPv4 206.108.255.112: set Speed to 800000 (800G) (now 100000).

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

  14. Italy MIX-IT Milan, Italy · PeeringDB 35
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G400G + 100G
    • In the entry with IPv4 217.29.67.16: set Speed to 400000 (400G) (now 100000).
  15. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB195.208.208.225 195.208.209.119195.208.208.225 195.208.209.119 195.208.210.93
    IPv6 address missing from PeeringDB2001:7f8:20:101::208:225 2001:7f8:20:101::209:1192001:7f8:20:101::208:225 2001:7f8:20:101::209:119 2001:7f8:20:101::210:93
    • Add an entry: IPv4 195.208.210.93, IPv6 2001:7f8:20:101::210:93, RS peer no.

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

  16. South Africa NAPAfrica IX Cape Town Cape Town, South Africa · PeeringDB 597
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G2 × 200G
    • In the entry with IPv4 196.60.70.105: set Speed to 200000 (200G) (now 100000).
    • In the entry with IPv4 196.60.70.110: set Speed to 200000 (200G) (now 100000).

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

  17. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 400G2 × 300G
    • In the entry with IPv4 196.60.9.105: set Speed to 300000 (300G) (now 400000).
    • In the entry with IPv4 196.60.9.110: set Speed to 300000 (300G) (now 400000).

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

  18. Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64
    ProblemPeeringDB hasThe export has
    IPv6 address differs2001:7f8:13::a501:6509:1 2001:7f8:13::a501:6509:22001:7f8:13::a501:6509:5 2001:7f8:13::a501:6509:6
    • In the entry with IPv4 193.239.119.131: set IPv6 to 2001:7f8:13::a501:6509:5 (now 2001:7f8:13::a501:6509:1).
    • In the entry with IPv4 193.239.119.132: set IPv6 to 2001:7f8:13::a501:6509:6 (now 2001:7f8:13::a501:6509:2).

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

  19. United States PhillyIX Philadelphia, United States · PeeringDB 2088
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 20G2 × 100G
    • In the entry with IPv4 206.80.234.7: set Speed to 100000 (100G) (now 20000).
    • In the entry with IPv4 206.80.234.8: set Speed to 100000 (100G) (now 20000).
  20. United States SIX Seattle Seattle, United States · PeeringDB 13
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 400G + 2 × 300G2 × 300G

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

  21. Taiwan STUIX Taipei City, Taiwan · PeeringDB 3352
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G2 × 100G
    • In the entry with IPv4 103.158.187.36: set Speed to 100000 (100G) (now 10000).
    • In the entry with IPv4 103.158.187.45: set Speed to 100000 (100G) (now 10000).

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

  22. Switzerland SwissIX Zurich, Switzerland · PeeringDB 60
    ProblemPeeringDB hasThe export has
    Port speed differs100G + 40G2 × 100G
    • In the entry with IPv4 91.206.52.107: set Speed to 100000 (100G) (now 40000).

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

Check these entries (1)

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

  1. Denmark Netnod Copenhagen BLUE -- MTU9K Malmo / Copenhagen, Denmark · PeeringDB 2868Not on its IX-F export
    IPv4212.237.192.47
    IPv62001:7f8:d:202::47
    Speed100000 Mbps (100G)

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