ixreport

TSFY: PeeringDB fix list

AS204536 · peeringdb.com/net/17225

PeeringDB

2 things to fix in TSFY's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on TSFY'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 (2)

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. Ireland INEX LAN1 Dublin, Ireland · PeeringDB 48
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB185.6.36.134185.6.36.134 185.6.36.137
    Port speed differs1G2 × 1G
    • Add an entry: IPv4 185.6.36.137, IPv6 –, speed 1000 (1G), RS peer yes.

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

  2. Ireland INEX LAN2 Dublin, Ireland · PeeringDB 387
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB194.88.240.72194.88.240.72 194.88.240.74
    Port speed differs1G2 × 1G
    • Add an entry: IPv4 194.88.240.74, IPv6 –, speed 1000 (1G), RS peer yes.

    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/204536/: 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.