Virtualize-Network
AS216056 · XaVen-Network
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.
-
4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members list
IPv4 – IPv6 2001:7f8:d0::3:4bf8:1 Speed Not published RS peer Yes
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.
-
Problem PeeringDB has The export has Port speed differs 1G 10G - 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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB none 33.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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB none 185.0.24.214 Port speed differs 1G 10G - 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
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 11 |
| Nov 18, 2026 | 11 |
| Nov 17, 2026 | 11 |
| Nov 16, 2026 | 11 |
| Nov 15, 2026 | 11 |
| Nov 14, 2026 | 11 |
| Nov 13, 2026 | 10 |
| Nov 12, 2026 | 10 |
| Nov 11, 2026 | 10 |
| Nov 10, 2026 | 10 |
| Nov 9, 2026 | 9 |
| Nov 8, 2026 | 9 |
| Nov 7, 2026 | 9 |
| Nov 6, 2026 | 9 |
| Nov 5, 2026 | 9 |
| Nov 4, 2026 | 9 |
| Nov 3, 2026 | 9 |
| Nov 2, 2026 | 9 |
| Nov 1, 2026 | 9 |
| Oct 31, 2026 | 8 |
| Oct 30, 2026 | 7 |
| Oct 29, 2026 | 7 |
| Oct 28, 2026 | 7 |
| Oct 27, 2026 | 7 |
| Oct 26, 2026 | 7 |
| Oct 25, 2026 | 7 |
| Oct 24, 2026 | 7 |
| Oct 23, 2026 | 7 |
| Oct 22, 2026 | 7 |
| Oct 21, 2026 | 7 |
| Oct 20, 2026 | 7 |
| Oct 19, 2026 | 7 |
| Oct 18, 2026 | 7 |
| Oct 17, 2026 | 7 |
| Oct 16, 2026 | 7 |
| Oct 15, 2026 | 7 |
| Oct 14, 2026 | 7 |
| Oct 13, 2026 | 7 |
| Oct 12, 2026 | 7 |
| Oct 11, 2026 | 7 |
| Oct 10, 2026 | 7 |
| Oct 9, 2026 | 7 |
| Oct 8, 2026 | 7 |
| Oct 7, 2026 | 7 |
| Oct 6, 2026 | 7 |
| Oct 5, 2026 | 7 |
| Oct 4, 2026 | 7 |
| Oct 3, 2026 | 7 |
In the last 30 days Virtualize-Network joined 4 exchanges and left 0. Growing networks
Joined
- Core01-IX Velbert Nov 14, 2026
- TYIX Tokyo Nov 10, 2026
- 91-IX Frankfurt Nov 1, 2026 PeeringDB only
- Better CNIX 上海 Oct 31, 2026 PeeringDB only
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.
| 4b42 Internet Exchange Point Zurich, Switzerland | Not in PeeringDB | ||
| 91-IX Frankfurt, Germany | 1G | PeeringDB | |
| Better CNIX 上海, China | 1G | PeeringDB | |
| Core01-IX Velbert, Germany | 1G | Both Speed differs | |
| CXIX - Great Lakes NewYork, United States | 10G | Both IPv4 not in PeeringDB | |
| DataSphere Internet Exchange (Hong Kong) Hong Kong, Hong Kong | 10G | PeeringDB | |
| FREMIX Fremont, United States | 100M | Both | |
| Kent Internet Exchange Point Kent, United Kingdom | 1G | Both IPv4 not in PeeringDBSpeed differs | |
| Protocol 7 IX - Hong Kong Hong Kong, Hong Kong | 10G | PeeringDB | |
| TYIX Tokyo, Japan | 1G | Both | |
| ZXIX Hong Kong Hong Kong, Hong Kong | 2 × 1G | PeeringDB |
Facilities (1)
The buildings Virtualize-Network lists in PeeringDB, and how many of the exchanges in each it's on.
| 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