MoeDove Global
AS44324
MoeDove LLC
Tools: Where can I peer with MoeDove Global? · Where should MoeDove Global peer next? · Compare MoeDove Global with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
6 things to fix in MoeDove Global's PeeringDB record, from what its exchanges publish: 2 to add, 3 to correct, 1 to check. As of 2026-11-19 12:40 UTC.
Make the changes on MoeDove Global'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 (2)
On the exchange's own member list, but not in MoeDove Global's PeeringDB record. Add one entry per connection with these values.
-
IPv4 149.112.29.116 IPv6 2001:504:125:e0::116 Speed Not published RS peer Not published -
IPv4 – IPv6 2602:f919:90f:fffa::4432:4 Speed Not published RS peer Not published
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 IPv4 address in PeeringDB, not in the export 185.1.125.244 none - In the entry with IPv4 185.1.125.244: set IPv4 to (empty) (now 185.1.125.244).
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 185.0.24.195 185.0.24.195 185.0.24.249 IPv6 address missing from PeeringDB 2001:7f8:aa::195 2001:7f8:aa::195 2001:7f8:aa::249 Port speed differs 10G 2 × 10G - Add an entry: IPv4 185.0.24.249, IPv6 2001:7f8:aa::249, speed 10000 (10G), RS peer yes.
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 1G 100M - In the entry with IPv4 149.112.50.101: set Speed to 100 (100M) (now 1000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If MoeDove Global has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 – IPv6 2001:7f8:11f:be00:44:324:0:1 Speed 10000 Mbps (10G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 26 |
| Nov 18, 2026 | 26 |
| Nov 17, 2026 | 26 |
| Nov 16, 2026 | 25 |
| Nov 15, 2026 | 25 |
| Nov 14, 2026 | 25 |
| Nov 13, 2026 | 25 |
| Nov 12, 2026 | 26 |
| Nov 11, 2026 | 26 |
| Nov 10, 2026 | 26 |
| Nov 9, 2026 | 26 |
| Nov 8, 2026 | 26 |
| Nov 7, 2026 | 26 |
| Nov 6, 2026 | 26 |
| Nov 5, 2026 | 26 |
| Nov 4, 2026 | 26 |
| Nov 3, 2026 | 26 |
| Nov 2, 2026 | 26 |
| Nov 1, 2026 | 26 |
| Oct 31, 2026 | 26 |
| Oct 30, 2026 | 26 |
| Oct 29, 2026 | 26 |
| Oct 28, 2026 | 26 |
| Oct 27, 2026 | 26 |
| Oct 26, 2026 | 26 |
| Oct 25, 2026 | 26 |
| Oct 24, 2026 | 26 |
| Oct 23, 2026 | 26 |
| Oct 22, 2026 | 26 |
| Oct 21, 2026 | 26 |
| Oct 20, 2026 | 26 |
| Oct 19, 2026 | 26 |
| Oct 18, 2026 | 26 |
| Oct 17, 2026 | 26 |
| Oct 16, 2026 | 26 |
| Oct 15, 2026 | 26 |
| Oct 14, 2026 | 26 |
| Oct 13, 2026 | 26 |
| Oct 12, 2026 | 26 |
| Oct 11, 2026 | 26 |
| Oct 10, 2026 | 26 |
| Oct 9, 2026 | 26 |
| Oct 8, 2026 | 25 |
| Oct 7, 2026 | 25 |
| Oct 6, 2026 | 25 |
| Oct 5, 2026 | 25 |
| Oct 4, 2026 | 25 |
| Oct 3, 2026 | 25 |
Map
Where MoeDove Global'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 IPv4 not in export | |
| Barcelona-IX Barcelona, Spain | 1G | Both | |
| BEE-IX Lviv, Ukraine | 10G | PeeringDB only | |
| EVIXVIX Fremont, United States | 1G | Both | |
| FogIXP Avers, Switzerland | 1G | Both | |
| FREMIX Fremont, United States | Not in PeeringDB | ||
| Frys-IX Fryslân, Netherlands | 10G | Both | |
| HOUIX Houston, United States | 10G | Both | |
| KCIX Kansas City, United States | 10G | Both | |
| Kent Internet Exchange Point Kent, United Kingdom | 10G | Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs | |
| LOCIX FRANKFURT Frankfurt am Main, Germany | 10G | PeeringDB | |
| LONAP London, United Kingdom | 1G | Both | |
| MSR IX shibuya, Japan | Not in PeeringDB | ||
| NRIX Taipei City, Taiwan | 10G | Both | |
| ONIX Toronto, Canada | 1G | Both Speed differs | |
| Poema IXVIX Taipei City, Taiwan | 500M | PeeringDB only | |
| Protocol 7 IX - Lycheen Japan Tokyo, Japan | 10G | PeeringDB | |
| RUDAKI-IX Kiev, Ukraine | 10G | Both | |
| STLIX Saint Louis, MO, United States | 10G | Both | |
| STUIX Taipei City, Taiwan | 10G + 1G | Both | |
| TPIX-TW Taipei/Taiwan, Taiwan | 20G | PeeringDB | |
| TYIX Tokyo, Japan | 10G | Both | |
| UNM-Exch Canada-West Vancouver, Canada | 1G | Both | |
| YYCIX Calgary, Canada | 10G | Both | |
| ZXIX Hangzhou Hangzhou, China | 1G | PeeringDB | |
| ZXIX Hong Kong Hong Kong, Hong Kong | 10G | PeeringDB |
These exchanges have a switch in a facility where MoeDove Global lists itself in PeeringDB, but don't have MoeDove Global 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.
| AMS-IXAmsterdam, Netherlands | 920 | |
| NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 672 | |
| KleyReXFrankfurt, Germany | 471 | |
| SIX SeattleSeattle, United States | 372 | |
| INTERIXAmsterdam, Netherlands | 262 | |
| ERA-IX AmsterdamAmsterdam, Netherlands | 244 | |
| NetIXSofia, Bulgaria | 204 | |
| ixFabric - AmsterdamAmsterdam, Netherlands | 181 | |
| nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France | 160 | |
| MICEMinneapolis, MN, United States | 157 | |
| Equinix TokyoTokyo, Japan | 127 | |
| IX-DenverDenver, United States | 96 | |
| SIX Seattle (Jumbo)Seattle, United States | 69 | |
| F4IX MCIKansas City, United States | 67 | |
| FogIXP FrankfurtFrankfurt, Germany | 67 | |
| FogIXP AmsterdamAmsterdam, Netherlands | 57 | |
| Kawaii IX AMSAmsterdam, Netherlands | 52 | |
| 3AM Network IXAmsterdam, Netherlands | 28 | |
| HN Internet Exchange (Main)North Kansas City, United States | 27 | |
| FOXTainan, Taiwan | 22 | |
| SpringIXSpringfield, MO, United States | 22 | |
| NSIX AmsterdamAmsterdam, Netherlands | 13 | |
| DesMoinesIXDes Moines, United States | 11 | |
| PeersIX AmsterdamAmsterdam, Netherlands | 11 | |
| Global Peer ExchangeWashington, United States | 6 | |
| STACIXFrankfurt, Germany | 5 | |
| TMW-iXFrankfurt am Main, Germany | 5 | |
| SIOUIXSioux City, United States | 4 | |
| MOCIXKansas City, United States | 3 |
Facilities (9)
The buildings MoeDove Global lists in PeeringDB, and how many of the exchanges in each it's on.
| 1530 SWIFT - NOCIXNorth Kansas City | 3 of 13 | |
| Qupra DCAmsterdam | 2 of 9 | |
| Digital Realty AMS17 - AmsterdamAmsterdam | 2 of 8 | |
| firstcolo - FRA4Frankfurt | 2 of 6 | |
| Chief LY Building TaipeiTaipei | 2 of 5 | |
| Chief HD Building TaipeiTaipei | 3 of 4 | |
| Equinix TY8 - TokyoTokyo | 1 of 4 | |
| Vinters ConnectMaidstone | 1 of 1 | |
| EdgeX by HGCTsing Yi | No exchange |
Recent changes Search them
- Oct 15, 2026 [PDB] AS44324 MoeDove Global now in PeeringDB at YYCIX
- Oct 9, 2026 [WEB] AS44324 MoeDove Global added to YYCIX
- Oct 3, 2026 AS44324 MoeDove Global added to TPIX-TW