ixreport

Fiber Telecom (FT): PeeringDB fix list

AS41327 · peeringdb.com/net/20933

PeeringDB

11 things to fix in Fiber Telecom (FT)'s PeeringDB record, from what its exchanges publish: 11 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on Fiber Telecom (FT)'s PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Correct these entries (11)

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. Netherlands AMS-IX Amsterdam, Netherlands · PeeringDB 26
    ProblemPeeringDB hasThe export has
    Port speed differs10G4G
    • In the entry with IPv4 80.249.208.112: set Speed to 4000 (4G) (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 Dusseldorf Düsseldorf, Germany · PeeringDB 1214
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 185.1.170.210: set Speed to 10000 (10G) (now 1000).
  3. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 185.1.210.187: set Speed to 10000 (10G) (now 1000).
  4. Spain DE-CIX Madrid Madrid, Spain · PeeringDB 1277
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 185.1.192.52: set Speed to 10000 (10G) (now 1000).
  5. France DE-CIX Marseille Marseille, France · PeeringDB 1149
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 185.1.47.100: set Speed to 10000 (10G) (now 1000).
  6. Germany DE-CIX Munich Munich, Germany · PeeringDB 248
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 185.1.208.193: set Speed to 10000 (10G) (now 1000).
  7. United States DE-CIX New York New York, United States · PeeringDB 804
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 206.82.105.11: set Speed to 10000 (10G) (now 1000).
  8. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G10G

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

  9. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs10G5G
    • In the entry with IPv4 195.66.227.128: set Speed to 5000 (5G) (now 10000).
  10. Italy MIX-IT Milan, Italy · PeeringDB 35
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB217.29.67.42 217.29.67.51217.29.67.42 217.29.67.51 217.29.67.215
    IPv6 address missing from PeeringDB2001:7f8:b:100:1d1:a5d4:1327:42 2001:7f8:b:100:1d1:a5d4:1327:512001:7f8:b:100:1d1:a5d4:1327:42 2001:7f8:b:100:1d1:a5d4:1327:51 2001:7f8:b:100:1d1:a5d4:1327:215
    Port speed differs20G + 10G20G + 2 × 10G
    • Add an entry: IPv4 217.29.67.215, IPv6 2001:7f8:b:100:1d1:a5d4:1327:215, speed 10000 (10G), RS peer yes.
  11. Italy VSIX Padova, Italy · PeeringDB 311
    ProblemPeeringDB hasThe export has
    Port speed differs100G10G
    • In the entry with IPv4 185.1.115.74: set Speed to 10000 (10G) (now 100000).

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

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