ixreport

Akamai Technologies: PeeringDB fix list

AS20940 · peeringdb.com/net/2

PeeringDB

31 things to fix in Akamai Technologies's PeeringDB record, from what its exchanges publish: 11 to add, 13 to correct, 7 to check. As of 2026-10-08 22:13 UTC.

Make the changes on Akamai Technologies'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 Akamai Technologies's PeeringDB record. Add one entry per connection with these values.

  1. Curaçao AMS-IX Caribbean Curacao, Curaçao · PeeringDB 366From its IX-F export
    IPv4200.0.20.25
    IPv62001:13c7:6004::a502:940: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.

  2. United States Any2East Washington DC, Reston, Boston, New York, Atlanta, United States · PeeringDB 204From its website members list
    IPv4206.51.40.68
    IPv62001:504:13:1::68
    SpeedNot published
    RS peerNot published
  3. Netherlands Asteroid Amsterdam Amsterdam, Netherlands · PeeringDB 1812From its IX-F export
    IPv4185.1.94.11
    IPv62001:7f8:b6::51cc:1
    Speed100000 Mbps (100G)
    RS peerYes
  4. United States Chicago Open Pipes Chicago, United States · PeeringDB 4960From its IX-F export
    IPv4149.112.192.15
    IPv62001:505:149::15
    Speed100000 Mbps (100G)
    RS peerYes

    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 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.

  6. India Extreme IX Pune Pune, India · PeeringDB 4805From its IX-F export

    The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

  7. United States HOUIX Houston, United States · PeeringDB 2835From its IX-F export and website members list
    IPv4206.83.136.88
    IPv62001:504:9e::88
    Speed100000 Mbps (100G)
    RS peerNot published
  8. Kenya KIXP - Nairobi Nairobi, Kenya · PeeringDB 236From 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.

  9. Norway Netnod Oslo BLUE -- MTU9K Oslo, Norway · PeeringDB 4855From its IX-F export
    IPv4194.153.157.8
    IPv62001:7f8:d:500::8
    SpeedNot published
    RS peerYes
  10. Norway Netnod Oslo GREEN -- MTU9K Oslo, Norway · PeeringDB 4856From its IX-F export
    IPv4194.153.157.72
    IPv62001:7f8:d:501::72
    SpeedNot published
    RS peerYes
  11. Rwanda RINEX Kigali, Rwanda · PeeringDB 1032From 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 (13)

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. Spain CATNIX Barcelona, Spain · PeeringDB 62
    ProblemPeeringDB hasThe export has
    Port speed differs100G50G
    • In the entry with IPv4 193.242.98.157: set Speed to 50000 (50G) (now 100000).

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

  2. United States CIX-NoVA Ashburn, Reston, Washington DC, United States · PeeringDB 4796
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB149.112.69.19149.112.69.17 149.112.69.19
    IPv6 address missing from PeeringDB2001:504:40:69::1:192001:504:40:69::1:17 2001:504:40:69::1:19
    Port speed differs100G2 × 100G
    • Add an entry: IPv4 149.112.69.17, IPv6 2001:504:40:69::1:17, speed 100000 (100G), RS peer yes.
  3. United States DE-CIX Chicago Chicago, United States · PeeringDB 3378
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB149.112.11.33149.112.11.33 149.112.11.92
    IPv6 address missing from PeeringDB2001:504:102::51cc:0:12001:504:102::51cc:0:1 2001:504:102::51cc:0:2
    Port speed differs100G400G + 100G
    • Add an entry: IPv4 149.112.11.92, IPv6 2001:504:102::51cc:0:2, speed 400000 (400G), RS peer yes.
  4. United States DE-CIX Dallas Dallas, United States · PeeringDB 1249
    ProblemPeeringDB hasThe export has
    Port speed differs3 × 200G400G + 2 × 200G
    • In the entry with IPv4 206.53.202.125: set Speed to 400000 (400G) (now 200000).
  5. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 800G + 400G + 100G3 × 800G + 400G
    • In the entry with IPv4 80.81.192.168: set Speed to 800000 (800G) (now 100000).
  6. India DE-CIX Mumbai Mumbai, India · PeeringDB 832
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB103.27.170.100 103.27.170.154 103.27.171.120103.27.170.67 103.27.170.100 103.27.170.154 103.27.171.120
    IPv6 address missing from PeeringDB2401:7500:fff6::100 2401:7500:fff6::121 2401:7500:fff6::1542401:7500:fff6::c7 2401:7500:fff6::100 2401:7500:fff6::121 2401:7500:fff6::154
    Port speed differs2 × 200G + 100G2 × 200G + 2 × 100G
    • Add an entry: IPv4 103.27.170.67, IPv6 2401:7500:fff6::c7, speed 100000 (100G), RS peer yes.
  7. United States DE-CIX New York New York, United States · PeeringDB 804
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G400G + 100G
    • In the entry with IPv4 206.82.104.62: set Speed to 400000 (400G) (now 100000).
  8. Poland EPIX.Katowice Katowice/Silesia, Poland · PeeringDB 491
    ProblemPeeringDB hasThe export has
    Port speed differs400G200G
    • In the entry with IPv4 178.216.40.224: set Speed to 200000 (200G) (now 400000).

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

  9. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs4 × 100G2 × 100G

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

  10. Indonesia IIX-Jakarta Jakarta, Indonesia · PeeringDB 210
    ProblemPeeringDB hasThe export has
    Port speed differs300G + 200G + 100G200G + 2 × 100G
    • In the entry with IPv4 123.108.9.37: set Speed to 100000 (100G) (now 300000).

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

  11. Indonesia JKT-IX Jakarta, Indonesia · PeeringDB 2476
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 400G + 300G3 × 400G + 100G
    • In the entry with IPv4 119.11.186.142: set Speed to 400000 (400G) (now 300000).
  12. United States MICE Minneapolis, MN, United States · PeeringDB 446
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB206.108.255.84 206.108.255.85206.108.255.43 206.108.255.44 206.108.255.84 206.108.255.85
    IPv6 address missing from PeeringDB2001:504:27::51cc:0:1 2001:504:27::51cc:0:22001:504:27::51cc:0:1 2001:504:27::51cc:0:2 2001:504:27::51cc:0:3 2001:504:27::51cc:0:4
    Port speed differs500G + 400G500G + 3 × 400G
    • Add an entry: IPv4 206.108.255.43, IPv6 2001:504:27::51cc:0:3, speed 400000 (400G), RS peer yes.
    • Add an entry: IPv4 206.108.255.44, IPv6 2001:504:27::51cc:0:4, speed 400000 (400G), RS peer yes.

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

  13. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    IPv6 address in PeeringDB, not in the export2001:7f8:7f::45 2001:7f8:7f::1212001:7f8:7f::121
    Port speed differs300G + 200G62.5G
    • In the entry with IPv4 185.0.20.121: set Speed to 62500 (62.5G) (now 300000).
    • In the entry with IPv4 185.0.20.45: set IPv6 to (empty) (now 2001:7f8:7f::45); set Speed to 62500 (62.5G) (now 200000).

Check these entries (7)

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

  1. Armenia ArmIX Yerevan, Armenia · PeeringDB 851Not on its website members list
    IPv491.218.7.11
    IPv62001:7f8:94::aa
    Speed20000 Mbps (20G)

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

  2. Ghana GIXA Accra, Ghana · PeeringDB 694Not on its website members list
    IPv4196.201.2.160
    IPv6–
    Speed10000 Mbps (10G)

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

  3. Germany MegaIX Berlin Berlin, Germany · PeeringDB 209Not on its IX-F export
    IPv4194.9.117.19
    IPv62001:7f8:8:5:0:51cc:0:1
    Speed100000 Mbps (100G)
  4. Denmark Netnod Copenhagen BLUE -- MTU9K Malmo / Copenhagen, Denmark · PeeringDB 2868Not on its IX-F export
    IPv4212.237.192.170
    IPv62001:7f8:d:202::170
    Speed200000 Mbps (200G)
  5. Denmark Netnod Copenhagen GREEN -- MTU9K Malmo / Copenhagen, Denmark · PeeringDB 193Not on its IX-F export
    IPv4212.237.193.170
    IPv62001:7f8:d:203::170
    Speed200000 Mbps (200G)
  6. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846Not on its IX-F export
    IPv4194.68.128.170
    IPv62001:7f8:d:fe::170
    Speed300000 Mbps (300G)
  7. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70Not on its IX-F export
    IPv4194.68.123.170
    IPv62001:7f8:d:ff::170
    Speed300000 Mbps (300G)

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