ixreport

Valve Corporation: PeeringDB fix list

AS32590 · peeringdb.com/net/4782

PeeringDB

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

Make the changes on Valve Corporation'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 (6)

On the exchange's own member list, but not in Valve Corporation'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. United States IX-Denver Denver, United States · PeeringDB 1207From 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.

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

  3. Sweden Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden · PeeringDB 2847From its IX-F export
    IPv4195.69.119.124
    IPv62001:7f8:d:fb::124
    SpeedNot published
    RS peerYes
  4. Sweden Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden · PeeringDB 2845From its IX-F export
    IPv4195.245.240.124
    IPv62001:7f8:d:fc::124
    SpeedNot published
    RS peerYes
  5. United States Ohio IX Columbus, United States · PeeringDB 869From 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 PIT-IX Pittsburgh, United States · PeeringDB 1999From its IX-F export and website members list

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

    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 (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. Hungary BIX Budapest, Hungary · PeeringDB 55
    ProblemPeeringDB hasThe export has
    Port speed differs40G100G
    • In the entry with IPv4 193.188.137.28: set Speed to 100000 (100G) (now 40000).
  2. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G100G
    • In the entry with IPv4 178.18.225.125: set Speed to 100000 (100G) (now 10000).
    • In the entry with IPv4 178.18.236.101: 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.

  3. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export194.68.128.124 194.68.128.224194.68.128.124
    IPv6 address in PeeringDB, not in the export2001:7f8:d:fe::124 2001:7f8:d:fe::2242001:7f8:d:fe::124
    • The entry with IPv4 194.68.128.224, IPv6 2001:7f8:d:fe::224 isn't in the export: delete it if that connection is gone.
  4. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export194.68.123.124 194.68.123.224194.68.123.124
    IPv6 address in PeeringDB, not in the export2001:7f8:d:ff::124 2001:7f8:d:ff::2242001:7f8:d:ff::124
    • The entry with IPv4 194.68.123.224, IPv6 2001:7f8:d:ff::224 isn't in the export: delete it if that connection is gone.
  5. Slovakia NIX.SK Bratislava, Slovakia · PeeringDB 299
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G800G
    • In the entry with IPv4 194.30.187.31: set Speed to 800000 (800G) (now 100000).
    • In the entry with IPv4 194.30.187.41: 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.

  6. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 400G100G
    • In the entry with IPv4 185.0.20.228: set Speed to 100000 (100G) (now 400000).
    • In the entry with IPv4 185.0.20.229: set Speed to 100000 (100G) (now 400000).

Check these entries (2)

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

  1. Germany City-IX Frankfurt Frankfurt, Germany · PeeringDB 4175Not on its IX-F export
    IPv4185.0.10.39
    IPv62001:7f8:e2::a503:2590:1
    Speed400000 Mbps (400G)
    IPv4185.0.10.68
    IPv62001:7f8:e2::a503:2590:2
    Speed400000 Mbps (400G)
  2. United Arab Emirates SH-IX Fujairah, United Arab Emirates · PeeringDB 866Not on its website members list
    IPv4185.1.15.57
    IPv62001:7f8:7a::3:2590:1
    Speed1000 Mbps (1G)
    IPv4185.1.15.67
    IPv62001:7f8:7a::3:2590:2
    Speed1000 Mbps (1G)

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

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