ixreport

VanIsle-Networks

AS219254 · VanIsle Networks

VanIsle Networks

2Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
NSPType
OpenPeering policy
1Using the route servers
2To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with VanIsle-Networks? · Where should VanIsle-Networks peer next? · Compare VanIsle-Networks with another network

This network elsewhere: its registry history on RIR Tracker

PeeringDB fix list Printable page · CSV

2 things to fix in VanIsle-Networks's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on VanIsle-Networks'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. Canada ONIX Toronto, Canada · PeeringDB 4059
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone149.112.50.131
    • In the entry with IPv6 2001:504:125:e1::183: set IPv4 to 149.112.50.131 (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

  2. Canada UNM-Exch Canada-West Vancouver, Canada · PeeringDB 2452
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone192.34.27.144
    • Add an entry: IPv4 192.34.27.144, IPv6 –.

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

Exchanges over time

012Oct 3, 2026Nov 19, 20262
Show as a table
DateExchanges
Nov 19, 20262
Nov 18, 20262
Nov 17, 20262
Nov 16, 20262
Nov 15, 20262
Nov 14, 20262
Nov 13, 20262
Nov 12, 20262
Nov 11, 20262
Nov 10, 20262
Nov 9, 20262
Nov 8, 20262
Nov 7, 20262
Nov 6, 20262
Nov 5, 20262
Nov 4, 20262
Nov 3, 20262
Nov 2, 20262
Nov 1, 20262
Oct 31, 20262
Oct 30, 20262
Oct 29, 20262
Oct 28, 20262
Oct 27, 20262
Oct 26, 20262
Oct 25, 20262
Oct 24, 20262
Oct 23, 20262
Oct 22, 20262
Oct 21, 20262
Oct 20, 20262
Oct 19, 20262
Oct 18, 20262
Oct 17, 20262
Oct 16, 20262
Oct 15, 20262
Oct 14, 20262
Oct 13, 20262
Oct 12, 20262
Oct 11, 20262
Oct 10, 20262
Oct 9, 20262
Oct 8, 20262
Oct 7, 20262
Oct 6, 20262
Oct 5, 20262
Oct 4, 20262
Oct 3, 20262

Map

Where VanIsle-Networks's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 1G, at the 1 of 2 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Canada ONIX Toronto, Canada 2001:504:125:e1::183 1G Yes Both IPv4 not in PeeringDB
Canada UNM-Exch Canada-West Vancouver, Canada 2602:ffb1:200:0:192:34:27:144 Both IPv4 not in PeeringDB

VanIsle-Networks lists no facilities in PeeringDB.