Anexia: PeeringDB fix list

AS42473 · peeringdb.com/net/3241

PeeringDB

11 things to fix in Anexia's PeeringDB record, from what its exchanges publish: 3 to add, 8 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Anexia'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 (3)

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

  1. Finland FICIX 2 (Helsinki) Helsinki, Finland · PeeringDB 98From 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. Sweden Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden · PeeringDB 2847From its IX-F export
    IPv4195.69.119.18
    IPv62001:7f8:d:fb::18
    SpeedNot published
    RS peerYes
  3. Sweden Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden · PeeringDB 2845From its IX-F export
    IPv4195.245.240.18
    IPv62001:7f8:d:fc::18
    SpeedNot published
    RS peerYes

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. India DE-CIX Chennai Chennai, India · PeeringDB 2588
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 103.228.174.14: set Speed to 10000 (10G) (now 1000).
  2. United States DE-CIX Dallas Dallas, United States · PeeringDB 1249
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 206.53.202.81: set Speed to 10000 (10G) (now 1000).
  3. India DE-CIX Mumbai Mumbai, India · PeeringDB 832
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export103.27.170.39none
    IPv6 address in PeeringDB, not in the export2401:7500:fff6::39none
    • The entry with IPv4 103.27.170.39, IPv6 2401:7500:fff6::39 isn't in the export: delete it if that connection is gone.
  4. Indonesia JKT-IX Jakarta, Indonesia · PeeringDB 2476
    ProblemPeeringDB hasThe export has
    Port speed differs10G1G
    • In the entry with IPv4 119.11.185.100: set Speed to 1000 (1G) (now 10000).
  5. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs10G9G
    • In the entry with IPv4 195.66.226.113: set Speed to 9000 (9G) (now 10000).
  6. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 195.66.238.113: set Speed to 10000 (10G) (now 1000).
  7. Luxembourg LU-CIX Luxembourg, Luxembourg · PeeringDB 297
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 188.93.170.15: set Speed to 10000 (10G) (now 1000).

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

  8. Singapore SGIX Singapore, Singapore · PeeringDB 429
    ProblemPeeringDB hasThe export has
    Port speed differs10G1G
    • In the entry with IPv4 103.16.102.59: set Speed to 1000 (1G) (now 10000).

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