ROBLOX: PeeringDB fix list

AS22697 · peeringdb.com/net/14578

PeeringDB

7 things to fix in ROBLOX's PeeringDB record, from what its exchanges publish: 1 to add, 5 to correct, 1 to check. As of 2026-10-08 20:58 UTC.

Make the changes on ROBLOX'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 (1)

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

  1. United States Any2Chicago Chicago, United States · PeeringDB 226From its website members list
    IPv4206.51.43.34
    IPv62001:504:13:4::34
    SpeedNot published
    RS peerNot published

Correct these entries (5)

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. United States DE-CIX Dallas Dallas, United States · PeeringDB 1249
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G2 × 200G
    • In the entry with IPv4 206.53.202.208: set Speed to 200000 (200G) (now 100000).
    • In the entry with IPv4 206.53.202.209: set Speed to 200000 (200G) (now 100000).
  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 400G + 2 × 200G4 × 500G
    • In the entry with IPv4 80.81.195.233: set Speed to 500000 (500G) (now 400000).
    • In the entry with IPv4 80.81.195.234: set Speed to 500000 (500G) (now 400000).
    • In the entry with IPv4 80.81.196.115: set Speed to 500000 (500G) (now 200000).
    • In the entry with IPv4 80.81.196.138: set Speed to 500000 (500G) (now 200000).
  3. United States DE-CIX New York New York, United States · PeeringDB 804
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB206.82.104.74 206.82.104.89 206.82.104.223206.82.104.74 206.82.104.89 206.82.104.207 206.82.104.223
    IPv6 address missing from PeeringDB2001:504:36::58a9:0:1 2001:504:36::58a9:0:2 2001:504:36::58a9:0:62001:504:36::58a9:0:1 2001:504:36::58a9:0:2 2001:504:36::58a9:0:4 2001:504:36::58a9:0:6
    Port speed differs3 × 100G2 × 200G + 2 × 100G
    • In the entry with IPv4 206.82.104.223: set Speed to 200000 (200G) (now 100000).
    • Add an entry: IPv4 206.82.104.207, IPv6 2001:504:36::58a9:0:4, speed 200000 (200G), RS peer yes.
  4. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 200G + 4 × 100G4 × 100G
    • In the entry with IPv4 178.18.236.105: set Speed to 100000 (100G) (now 200000).
    • In the entry with IPv4 178.18.236.106: set Speed to 100000 (100G) (now 200000).

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

  5. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 200G2 × 400G
    • In the entry with IPv4 195.66.227.159: set Speed to 400000 (400G) (now 200000).
    • In the entry with IPv4 195.66.227.161: set Speed to 400000 (400G) (now 200000).

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If ROBLOX 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.90.161
    IPv62001:de8:c::2:2697:1
    Speed100000 Mbps (100G)
    IPv4101.203.90.162
    IPv62001:de8:c::2:2697:2
    Speed100000 Mbps (100G)

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

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