ixreport

Phoenix Network

AS212237 · PXNET

7Exchanges, of which 2 VIX
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Educational/ResearchType
OpenPeering policy
7Using the route servers
1To fix in PeeringDB
0Facilities in PeeringDB

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

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

PeeringDB fix list Printable page · CSV

One thing to fix in Phoenix Network's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Phoenix Network'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. ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export185.1.125.193none
    • In the entry with IPv4 185.1.125.193: set IPv4 to (empty) (now 185.1.125.193).

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 Phoenix 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 3.4G across 7 exchanges.

Switzerland 4b42 Internet Exchange Point Zurich, Switzerland 185.1.125.193 2001:7f8:d0::3:3d0d:1 1G Yes Both IPv4 not in export
United States EVIXVIX Fremont, United States 206.81.104.49 2602:fed2:fff:ffff::49 1G 2 routes Both
Netherlands HamroIX-Amsterdam Amsterdam, Netherlands 2a0e:b107:f21::4 100M Yes PeeringDB
India OpenSwitch-IX Kolkata, India 2602:feda:afe::30 100M Yes PeeringDB
Egypt PyramIXVIX Cairo, Egypt 2a0e:46c4:102::212:237:1 100M Yes Both
China TOHU IX Guangzhou, China 2406:840:eb8f:1:0:21:2237:1 1G Yes PeeringDB
China ZXIX Hangzhou Hangzhou, China 2406:840:1f:1:0:21:2237:1 100M Yes PeeringDB

Phoenix Network lists no facilities in PeeringDB.