ixreport

Tech Futures Interactive Inc.: PeeringDB fix list

AS394256 · peeringdb.com/net/9874

PeeringDB

One thing to fix in Tech Futures Interactive Inc.'s PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on Tech Futures Interactive Inc.'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 (1)

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. Canada UNM-Exch Canada-West Vancouver, Canada · PeeringDB 2452
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB192.34.27.5 192.34.27.105192.34.27.5 192.34.27.105 192.34.27.205
    IPv6 address missing from PeeringDB2602:ffb1:200:0:192:34:27:5 2602:ffb1:200:0:192:34:27:1052602:ffb1:200:0:192:34:27:5 2602:ffb1:200:0:192:34:27:105 2602:ffb1:200:0:192:34:27:205
    • In the entry with IPv4 192.34.27.105: set IPv6 to (empty) (now 2602:ffb1:200:0:192:34:27:105).
    • In the entry with IPv4 192.34.27.5: set IPv6 to (empty) (now 2602:ffb1:200:0:192:34:27:5).
    • Add an entry: IPv4 192.34.27.205, IPv6 –.
    • Add an entry: IPv4 –, IPv6 2602:ffb1:200:0:192:34:27:5.
    • Add an entry: IPv4 –, IPv6 2602:ffb1:200:0:192:34:27:105.
    • Add an entry: IPv4 –, IPv6 2602:ffb1:200:0:192:34:27:205.

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