MYIP
AS215956 · AS215956
Tools: Where can I peer with MYIP? · Where should MYIP peer next? · Compare MYIP with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
3 things to fix in MYIP's PeeringDB record, from what its exchanges publish: 2 to correct, 1 at exchanges that look shut down. As of 2026-11-19 18:41 UTC.
Make the changes on MYIP'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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB none 80.249.215.87 - In the entry with IPv6 2001:7f8:1:0:a500:21:5956:1: set IPv4 to 80.249.215.87 (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 Port speed differs 2.5G 1G - In the entry with IPv6 2602:fed2:fff:ffff:6::f7: set Speed to 1000 (1G) (now 2500).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Exchanges that look shut down (1)
In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.
-
Only one outside network
IPv4 – IPv6 2a14:7580:eff0:ab9e:0:21:5956:1 Speed 1000 Mbps (1G)
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 33 |
| Nov 18, 2026 | 33 |
| Nov 17, 2026 | 33 |
| Nov 16, 2026 | 33 |
| Nov 15, 2026 | 33 |
| Nov 14, 2026 | 33 |
| Nov 13, 2026 | 33 |
| Nov 12, 2026 | 33 |
| Nov 11, 2026 | 33 |
| Nov 10, 2026 | 33 |
| Nov 9, 2026 | 33 |
| Nov 8, 2026 | 33 |
| Nov 7, 2026 | 33 |
| Nov 6, 2026 | 33 |
| Nov 5, 2026 | 33 |
| Nov 4, 2026 | 33 |
| Nov 3, 2026 | 33 |
| Nov 2, 2026 | 33 |
| Nov 1, 2026 | 33 |
| Oct 31, 2026 | 33 |
| Oct 30, 2026 | 33 |
| Oct 29, 2026 | 33 |
| Oct 28, 2026 | 33 |
| Oct 27, 2026 | 33 |
| Oct 26, 2026 | 33 |
| Oct 25, 2026 | 33 |
| Oct 24, 2026 | 33 |
| Oct 23, 2026 | 33 |
| Oct 22, 2026 | 33 |
| Oct 21, 2026 | 33 |
| Oct 20, 2026 | 33 |
| Oct 19, 2026 | 33 |
| Oct 18, 2026 | 33 |
| Oct 17, 2026 | 33 |
| Oct 16, 2026 | 33 |
| Oct 15, 2026 | 33 |
| Oct 14, 2026 | 33 |
| Oct 13, 2026 | 33 |
| Oct 12, 2026 | 33 |
| Oct 11, 2026 | 33 |
| Oct 10, 2026 | 33 |
| Oct 9, 2026 | 33 |
| Oct 8, 2026 | 33 |
| Oct 7, 2026 | 33 |
| Oct 6, 2026 | 33 |
| Oct 5, 2026 | 33 |
| Oct 4, 2026 | 33 |
| Oct 3, 2026 | 33 |
Map
Where MYIP'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 | 1G | Both | |
| AMS-IX Amsterdam, Netherlands | 1G | Both IPv4 not in PeeringDB | |
| DataSphere Internet Exchange (Hong Kong) Hong Kong, Hong Kong | 10G | PeeringDB | |
| EVIXVIX Fremont, United States | 2.5G | Both Speed differs | |
| FogIXP Avers, Switzerland | 2 × 1G | Both | |
| HN Internet Exchange (Main)VIX North Kansas City, United States | 10G | PeeringDB | |
| ixFabric - Amsterdam Amsterdam, Netherlands | 2 × 1G + 500M | PeeringDB | |
| ixFabric - Barcelona Barcelona, Spain | 1G | PeeringDB | |
| ixFabric - ChicagoVIX Chicago, United States | 100M | PeeringDB | |
| ixFabric - Dallas Dallas, United States | 10G + 1G | PeeringDB | |
| ixFabric - Dusseldorf Dusseldorf, Germany | 10G + 1G | PeeringDB | |
| ixFabric - Frankfurt Frankfurt, Germany | 10G + 1G + 500M | PeeringDB | |
| ixFabric - Fremont Fremont, United States | 1G | PeeringDB | |
| ixFabric - Hong Kong Hong Kong, Hong Kong | 2 × 10G | PeeringDB | |
| ixFabric - London London, United Kingdom | 1G + 500M + 2 × 100M | PeeringDB | |
| ixFabric - Los AngelesVIX Los Angeles, United States | 3 × 1G | PeeringDB | |
| ixFabric - Lyon Lyon, France | 1G | PeeringDB | |
| ixFabric - MiamiVIX Miami, United States | 1G + 100M | PeeringDB | |
| ixFabric - New York New York, United States | 1G | PeeringDB | |
| ixFabric - ParisVIX Paris, France | 100M | PeeringDB | |
| ixFabric - Rome Rome, Italy | 1G | PeeringDB | |
| ixFabric - Zurich Zurich, Switzerland | 10G + 1G + 500M | PeeringDB | |
| IXP FI HEL Helsinki, Finland | 1G | PeeringDB | |
| IXP LI VAD Vaduz, Liechtenstein | 1G | PeeringDB | |
| IXP NL DRO Dronten, Netherlands | 100M | PeeringDB | |
| IXP UK LON London, United Kingdom | 500M | PeeringDB | |
| Lynqia IX Berlinghost Berlin, Germany | 1G | PeeringDB | |
| NorthIX Copenhagen, Denmark | 1G | PeeringDB | |
| ONIX Toronto, Canada | 1G | Both | |
| PeersIX Amsterdam Amsterdam, Netherlands | 3 × 1G | PeeringDB | |
| Poema IXVIX Taipei City, Taiwan | 500M | PeeringDB only | |
| Protocol 7 IX - Hong Kong Hong Kong, Hong Kong | 10G | PeeringDB | |
| ZXIX Hong Kong Hong Kong, Hong Kong | 10G | PeeringDB |
MYIP lists no facilities in PeeringDB.