ixreport

MyNetwork

AS215664 · MyNetWork

Nguyen Doan Hung, ROUTE64-VERIFY: R64-ef7b5f9fcc1418e24cd47292a18da33e49c0cef78ad8e59bba144102777f54ce

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

Tools: Where can I peer with MyNetwork? · Where should MyNetwork peer next? · Compare MyNetwork with another network

This network elsewhere: its registry history on RIR Tracker

PeeringDB fix list Printable page · CSV

2 things to fix in MyNetwork's PeeringDB record, from what its exchanges publish: 1 to add, 1 to check. As of 2026-11-19 12:40 UTC.

Make the changes on MyNetwork'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 MyNetwork'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
    IPv4185.1.125.16
    IPv62001:7f8:d0::3:4a70:1
    SpeedNot published
    RS peerYes

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If MyNetwork has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Hong Kong HKIX Hong Kong, Hong Kong · PeeringDB 42Not on its IX-F export or website members list
    IPv4123.255.91.5
    IPv62001:7fa:0:1::c28:a5d
    SpeedNot published

Exchanges over time

02468Oct 3, 2026Nov 19, 20267
Show as a table
DateExchanges
Nov 19, 20267
Nov 18, 20267
Nov 17, 20267
Nov 16, 20267
Nov 15, 20267
Nov 14, 20267
Nov 13, 20267
Nov 12, 20267
Nov 11, 20267
Nov 10, 20267
Nov 9, 20267
Nov 8, 20267
Nov 7, 20267
Nov 6, 20267
Nov 5, 20267
Nov 4, 20267
Nov 3, 20267
Nov 2, 20267
Nov 1, 20267
Oct 31, 20267
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

Map

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

Switzerland 4b42 Internet Exchange Point Zurich, Switzerland 185.1.125.16 2001:7f8:d0::3:4a70:1 Yes Not in PeeringDB
Hong Kong HKIX Hong Kong, Hong Kong 123.255.91.5 2001:7fa:0:1::c28:a5d Yes PeeringDB only
Switzerland ixFabric - Zurich Zurich, Switzerland 2a0e:8f01:1000:25::100 1G Yes PeeringDB
Netherlands PeersIX Amsterdam Amsterdam, Netherlands 2a0a:6044:a1ff::5
2a0a:6044:a1ff::6
2a0a:6044:a1ff::7
2a0a:6044:a1ff::8
2a0a:6044:a1ff::9
Yes PeeringDB
Vietnam VNIX-DN Da Nang, Vietnam 218.100.60.5 2001:de8:3::5 1G Yes PeeringDB
Vietnam VNIX-HCM Ho Chi Minh City, Vietnam 218.100.14.5 2001:de8:a::5 1G Yes PeeringDB
Vietnam VNIX-HN Hanoi, Vietnam 218.100.10.5 2001:7fa:6::5 Yes PeeringDB

Exchanges in its buildings that it isn't on (18)

These exchanges have a switch in a facility where MyNetwork lists itself in PeeringDB, but don't have MyNetwork as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Facilities (5)

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

Singapore Equinix SG1 - SingaporeSingapore 0 of 11
Singapore Global Switch SingaporeSingapore 0 of 7
Japan Equinix TY2 - TokyoTokyo 0 of 6
Hong Kong MEGA-i (iAdvantage Hong Kong)Hong Kong 1 of 4
Vietnam FPT Fornix HNI 02Hanoi No exchange