Google LLC: PeeringDB fix list

AS15169 · peeringdb.com/net/433

PeeringDB

32 things to fix in Google LLC's PeeringDB record, from what its exchanges publish: 19 to add, 8 to correct, 5 to check. As of 2026-10-08 20:58 UTC.

Make the changes on Google LLC'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 (19)

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

  1. Poland 1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland · PeeringDB 3958From 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 AMS-IX Mumbai Mumbai, India · PeeringDB 1623From its IX-F export
    IPv4223.31.200.13
    IPv6–
    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. United States Any2Chicago Chicago, United States · PeeringDB 226From its website members list
    IPv4206.51.43.14 206.51.43.21
    IPv62001:504:13:4::14 2001:504:13:4::21
    SpeedNot published
    RS peerNot published

    The exchange lists several addresses but not which go together: add one entry for each IPv4 and IPv6 pair.

  4. Burkina Faso BFIX Ouagadougou Ouagadougou, Burkina Faso · PeeringDB 2729From 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.

  5. Cameroon CAMIX Douala Douala, Cameroon · PeeringDB 2541From 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. 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.

  7. United States CIX-ATL Atlanta, United States · PeeringDB 1668From its IX-F export and website members list

    2 connections, so 2 entries:

    IPv4206.71.12.25
    IPv62001:504:40:12::1:25
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4206.71.12.35
    IPv62001:504:40:12::1:35
    Speed100000 Mbps (100G)
    RS peerYes
  8. United States DE-CIX Dallas Dallas, United States · PeeringDB 1249From its IX-F export and website members list

    2 connections, so 2 entries:

    IPv4206.53.202.11
    IPv62001:504:61::3b41:0:1
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4206.53.202.109
    IPv62001:504:61::3b41:0:2
    Speed100000 Mbps (100G)
    RS peerYes
  9. Malaysia DE-CIX Kuala Lumpur Kuala Lumpur, Malaysia · PeeringDB 3473From its IX-F export
    IPv4103.119.234.12
    IPv62403:4ac0:1::3b41:0:1
    Speed20000 Mbps (20G)
    RS peerYes
  10. United States DE-CIX New York New York, United States · PeeringDB 804From its IX-F export and website members list

    2 connections, so 2 entries:

    IPv4206.82.104.41
    IPv62001:504:36::3b41:0:2
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4206.82.104.202
    IPv62001:504:36::3b41:0:1
    Speed100000 Mbps (100G)
    RS peerYes
  11. United States FL-IX Miami, United States · PeeringDB 954From its IX-F export and website members list

    2 connections, so 2 entries:

    IPv4206.41.108.12
    IPv62001:504:40:108::1:12
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4206.41.108.95
    IPv62001:504:40:108::1:95
    Speed100000 Mbps (100G)
    RS peerYes
  12. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export

    4 connections, so 4 entries:

    IPv4178.18.227.12
    IPv62a03:5f80:4::227:12
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4178.18.225.41
    IPv62a03:5f80:4::225:41
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4178.18.225.42
    IPv62a03:5f80:4::225:42
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4178.18.227.7
    IPv62a03:5f80:4::227:7
    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.

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

  14. United States LINX NoVA Ashburn, Reston, Manassas, United States · PeeringDB 777From its IX-F export and website members list

    2 connections, so 2 entries:

    IPv4206.55.196.65
    IPv62001:504:31::3b41:2
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4206.55.196.29
    IPv62001:504:31::3b41:1
    Speed10000 Mbps (10G)
    RS peerYes
  15. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100From its IX-F export

    2 connections, so 2 entries:

    IPv4195.208.208.232
    IPv62001:7f8:20:101::208:232
    SpeedNot published
    RS peerYes
    IPv4195.208.208.250
    IPv62001:7f8:20:101::208:250
    SpeedNot published
    RS peerYes

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

  16. Russia MSK-IX Saint-Petersburg St.Petersburg, Russia · PeeringDB 107From its IX-F export

    4 connections, so 4 entries:

    IPv4194.226.102.92
    IPv62001:7f8:20:202::102:92
    SpeedNot published
    RS peerYes
    IPv4194.226.102.138
    IPv62001:7f8:20:202::102:138
    SpeedNot published
    RS peerYes
    IPv4194.226.100.138
    IPv62001:7f8:20:201::100:138
    SpeedNot published
    RS peerYes
    IPv4194.226.100.92
    IPv62001:7f8:20:201::100:92
    SpeedNot published
    RS peerYes

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

  17. Italy Namex Rome Rome, Italy · PeeringDB 121From its IX-F export
    IPv4193.201.28.86
    IPv62001:7f8:10::1:5169
    Speed20000 Mbps (20G)
    RS peerYes

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

  18. United States NYIIX Los Angeles Los Angeles, United States · PeeringDB 23From its website members list
    IPv4149.112.104.46
    IPv62001:504:a::a501:5169:1
    SpeedNot published
    RS peerNot published
  19. Bulgaria TurkIX Sofia Sofia, Bulgaria · PeeringDB 4186From its IX-F export and website members list
    IPv4194.42.47.5
    IPv62001:7f8:161::5
    Speed200000 Mbps (200G)
    RS peerYes

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

Correct these entries (8)

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. Lithuania BALT-IX Vilnius, Lithuania · PeeringDB 2005
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G2 × 20G
    • In the entry with IPv4 77.241.206.42: set Speed to 20000 (20G) (now 100000).
    • In the entry with IPv4 77.241.206.43: set Speed to 20000 (20G) (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. Hungary BIX Budapest, Hungary · PeeringDB 55
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export193.188.137.151 193.188.137.163 193.188.137.169193.188.137.151 193.188.137.169
    IPv6 address in PeeringDB, not in the export2001:7f8:35::1:5169:1 2001:7f8:35::1:5169:2 2001:7f8:35::1:5169:32001:7f8:35::1:5169:2 2001:7f8:35::1:5169:3
    Port speed differs2 × 100G + 50G2 × 100G
    • The entry with IPv4 193.188.137.163, IPv6 2001:7f8:35::1:5169:1 isn't in the export: delete it if that connection is gone.
  3. Bulgaria BIX.BG Sofia, Bulgaria · PeeringDB 331
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export193.169.198.80 193.169.198.81 193.169.199.82 193.169.199.83193.169.198.80 193.169.198.81
    IPv6 address in PeeringDB, not in the export2001:7f8:58::3b41:0:1 2001:7f8:58::3b41:0:2 2001:7f8:58::3b41:0:3 2001:7f8:58::3b41:0:42001:7f8:58::3b41:0:1 2001:7f8:58::3b41:0:2
    • The entry with IPv4 193.169.199.82, IPv6 2001:7f8:58::3b41:0:3 isn't in the export: delete it if that connection is gone.
    • The entry with IPv4 193.169.199.83, IPv6 2001:7f8:58::3b41:0:4 isn't in the export: delete it if that connection is gone.
  4. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 300G300G + 200G
    • In the entry with IPv4 80.81.193.108: set Speed to 200000 (200G) (now 300000).
  5. India Extreme IX Delhi Delhi, India · PeeringDB 1323
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 200G + 100G3 × 200G
    • In the entry with IPv4 45.120.248.31: 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.

  6. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    Port speed differs300G + 200G2 × 300G
    • In the entry with IPv4 196.60.8.166: set Speed to 300000 (300G) (now 200000).

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

  7. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 200G50G
    • In the entry with IPv4 185.0.20.170: set Speed to 50000 (50G) (now 200000).
    • In the entry with IPv4 185.0.20.171: set Speed to 50000 (50G) (now 200000).
  8. Poland THINX Warsaw Warsaw, Poland · PeeringDB 481
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G20G
    • In the entry with IPv4 212.91.0.240: set Speed to 20000 (20G) (now 100000).
    • In the entry with IPv4 212.91.1.240: set Speed to 20000 (20G) (now 100000).
    • Add an entry: IPv4 212.91.0.240, IPv6 –, speed 20000 (20G).
    • Add an entry: IPv4 212.91.1.240, IPv6 –, speed 20000 (20G).

    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 (5)

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

  1. Netherlands Frys-IX Fryslân, Netherlands · PeeringDB 3512Not on its IX-F export
    IPv4185.1.160.180
    IPv62001:7f8:10f::3b41:180
    Speed30000 Mbps (30G)
    IPv4185.1.160.220
    IPv62001:7f8:10f::3b41:220
    Speed30000 Mbps (30G)
  2. Ghana GIXA Accra, Ghana · PeeringDB 694Not on its website members list
    IPv4196.201.2.118
    IPv6–
    Speed20000 Mbps (20G)

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

  3. Kuwait ix.kw Kuwait City, Kuwait · PeeringDB 2253Not on its IX-F export
    IPv4194.54.136.31
    IPv62a0c:c9c0::31
    Speed10000 Mbps (10G)
  4. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846Not on its IX-F export
    IPv4194.68.128.115
    IPv62001:7f8:d:fe::115
    Speed100000 Mbps (100G)
  5. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70Not on its IX-F export
    IPv4194.68.123.115
    IPv62001:7f8:d:ff::115
    Speed100000 Mbps (100G)

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