ixreport

Virtualize-Network

AS216056 · XaVen-Network

11Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Educational/ResearchType
OpenPeering policy
10Using the route servers
4To fix in PeeringDB
1Facility in PeeringDB

Tools: Where can I peer with Virtualize-Network? · Where should Virtualize-Network peer next? · Compare Virtualize-Network with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

4 things to fix in Virtualize-Network's PeeringDB record, from what its exchanges publish: 1 to add, 3 to correct. As of 2026-11-19 12:40 UTC.

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

  1. Switzerland 4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members list
    IPv4–
    IPv62001:7f8:d0::3:4bf8:1
    SpeedNot published
    RS peerYes

Correct these entries (3)

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. Germany Core01-IX Velbert, Germany · PeeringDB 5128
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv6 2a13:c8c4:fc08:1000::17: set Speed to 10000 (10G) (now 1000).

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

  2. United States CXIX - Great Lakes NewYork, United States · PeeringDB 4721
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone33.0.0.81
    • In the entry with IPv6 2a0f:7803:fc60:aaaa::2160:56: set IPv4 to 33.0.0.81 (now empty).

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

  3. ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone185.0.24.214
    Port speed differs1G10G
    • In the entry with IPv6 2001:7f8:aa::214: set IPv4 to 185.0.24.214 (now empty); set Speed to 10000 (10G) (now 1000).

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

Exchanges over time

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

In the last 30 days Virtualize-Network joined 4 exchanges and left 0. Growing networks

Joined

Map

Where Virtualize-Network'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 37.1G, at the 10 of 11 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Switzerland 4b42 Internet Exchange Point Zurich, Switzerland 2001:7f8:d0::3:4bf8:1 Yes Not in PeeringDB
Germany 91-IX Frankfurt, Germany 185.0.41.91 2001:7f8:1a:91::91 1G Yes PeeringDB
China Better CNIX 上海, China 2a0f:1cc7:fff0:1::20 1G Yes PeeringDB
Germany Core01-IX Velbert, Germany 2a13:c8c4:fc08:1000::17 1G Yes Both Speed differs
United States CXIX - Great Lakes NewYork, United States 2a0f:7803:fc60:aaaa::2160:56 10G Yes Both IPv4 not in PeeringDB
Hong Kong DataSphere Internet Exchange (Hong Kong) Hong Kong, Hong Kong 2602:f613::2160:56:1 10G Yes PeeringDB
United States FREMIX Fremont, United States 2001:504:125:e0::abf 100M Both
United Kingdom Kent Internet Exchange Point Kent, United Kingdom 2001:7f8:aa::214 1G Yes Both IPv4 not in PeeringDBSpeed differs
Hong Kong Protocol 7 IX - Hong Kong Hong Kong, Hong Kong 2602:f92a:1315:2::1a 10G Yes PeeringDB
Japan TYIX Tokyo, Japan 23.154.164.180 2602:f429:31::35 1G Yes Both
Hong Kong ZXIX Hong Kong Hong Kong, Hong Kong 2406:840:1f:1000:0:21:6056:1
2406:840:1f:1000:0:21:6056:2
2 × 1G Yes PeeringDB
Facilities (1)

The buildings Virtualize-Network lists in PeeringDB, and how many of the exchanges in each it's on.

United Kingdom Vinters ConnectMaidstone 1 of 1

Recent changes Search them

  • Nov 14, 2026 [IXF] AS216056 Virtualize-Network now on Core01-IX's IX-F list
  • Nov 14, 2026 [PDB] AS216056 Virtualize-Network added to Core01-IX
  • Nov 10, 2026 [IXF] AS216056 Virtualize-Network now on TYIX's IX-F list
  • Nov 10, 2026 [PDB] AS216056 Virtualize-Network added to TYIX
  • Nov 1, 2026 [PDB] AS216056 Virtualize-Network added to 91-IX
  • Oct 31, 2026 [PDB] AS216056 Virtualize-Network now in PeeringDB at FREMIX
  • Oct 31, 2026 [PDB] AS216056 Virtualize-Network now in PeeringDB at CXIX - Great Lakes
  • Oct 31, 2026 [PDB] AS216056 Virtualize-Network added to Better CNIX