Thales/Imperva: PeeringDB fix list

AS19551 · peeringdb.com/net/7063

PeeringDB

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

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

  1. Denmark Netnod Copenhagen GREEN -- MTU9K Malmo / Copenhagen, Denmark · PeeringDB 193From its IX-F export
    IPv4212.237.193.86
    IPv62001:7f8:d:203::86
    SpeedNot published
    RS peerYes

Correct these entries (7)

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. Indonesia AIX Tapos, Depok, Indonesia · PeeringDB 4449
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 43.254.82.7: 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.

  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs30G100G
    • In the entry with IPv4 80.81.193.87: set Speed to 100000 (100G) (now 30000).
  3. India DE-CIX Mumbai Mumbai, India · PeeringDB 832
    ProblemPeeringDB hasThe export has
    Port speed differs5G10G
    • In the entry with IPv4 103.27.170.142: set Speed to 10000 (10G) (now 5000).
  4. Indonesia JKT-IX Jakarta, Indonesia · PeeringDB 2476
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB119.11.186.90119.11.184.8 119.11.186.90
    IPv6 address missing from PeeringDB2404:c8:0:a:0:1:9551:22404:c8:0:a:0:1:9551:1 2404:c8:0:a:0:1:9551:2
    Port speed differs10G2 × 10G
    • Add an entry: IPv4 119.11.184.8, IPv6 2404:c8:0:a:0:1:9551:1, speed 10000 (10G), RS peer yes.
  5. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs50G + 30G2 × 100G
    • In the entry with IPv4 195.66.226.47: set Speed to 100000 (100G) (now 50000).
    • In the entry with IPv4 195.66.231.94: set Speed to 100000 (100G) (now 30000).
  6. Philippines Maharlika IX Manila, Philippines · PeeringDB 4167
    ProblemPeeringDB hasThe export has
    IPv4 address differs103.121.64.45163.223.201.45
    IPv6 address differs2400:efa0::1:9551:12001:df0:a940::1:9551:1
    • In the entry with IPv4 103.121.64.45: set IPv4 to 163.223.201.45 (now 103.121.64.45); set IPv6 to 2001:df0:a940::1:9551:1 (now 2400:efa0::1:9551:1).
  7. Italy MIX-IT Milan, Italy · PeeringDB 35
    ProblemPeeringDB hasThe export has
    Port speed differs10G20G
    • In the entry with IPv4 217.29.66.201: set Speed to 20000 (20G) (now 10000).

Check these entries (1)

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

  1. Spain CATNIX Barcelona, Spain · PeeringDB 62Not on its IX-F export
    IPv4193.242.98.127
    IPv62001:7f8:2a:0:2:1:1:9951
    Speed10000 Mbps (10G)

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