M3.NET Transit
AS51465
Fixmap Group
Tools: Where can I peer with M3.NET Transit? · Where should M3.NET Transit peer next? · Compare M3.NET Transit 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 M3.NET Transit's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on M3.NET Transit'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 (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 10G 100G - In the entry with IPv4 80.81.192.60: set Speed to 100000 (100G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 20G 5G - In the entry with IPv4 185.0.21.40: set Speed to 5000 (5G) (now 20000).
-
Problem PeeringDB has The export has Port speed differs 2 × 20G 30G - In the entry with IPv4 212.91.0.95: set Speed to 30000 (30G) (now 20000).
- In the entry with IPv4 212.91.1.146: set Speed to 30000 (30G) (now 20000).
- Add an entry: IPv4 212.91.0.95, IPv6 –, speed 30000 (30G).
- Add an entry: IPv4 212.91.1.146, IPv6 –, speed 30000 (30G).
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 | 5 |
| Nov 18, 2026 | 5 |
| Nov 17, 2026 | 5 |
| Nov 16, 2026 | 5 |
| Nov 15, 2026 | 5 |
| Nov 14, 2026 | 5 |
| Nov 13, 2026 | 5 |
| Nov 12, 2026 | 5 |
| Nov 11, 2026 | 5 |
| Nov 10, 2026 | 5 |
| Nov 9, 2026 | 5 |
| Nov 8, 2026 | 5 |
| Nov 7, 2026 | 5 |
| Nov 6, 2026 | 5 |
| Nov 5, 2026 | 5 |
| Nov 4, 2026 | 5 |
| Nov 3, 2026 | 5 |
| Nov 2, 2026 | 5 |
| Nov 1, 2026 | 5 |
| Oct 31, 2026 | 5 |
| Oct 30, 2026 | 5 |
| Oct 29, 2026 | 5 |
| Oct 28, 2026 | 5 |
| Oct 27, 2026 | 5 |
| Oct 26, 2026 | 5 |
| Oct 25, 2026 | 5 |
| Oct 24, 2026 | 5 |
| Oct 23, 2026 | 5 |
| Oct 22, 2026 | 5 |
| Oct 21, 2026 | 5 |
| Oct 20, 2026 | 5 |
| Oct 19, 2026 | 5 |
| Oct 18, 2026 | 5 |
| Oct 17, 2026 | 5 |
| Oct 16, 2026 | 5 |
| Oct 15, 2026 | 5 |
| Oct 14, 2026 | 5 |
| Oct 13, 2026 | 5 |
| Oct 12, 2026 | 5 |
| Oct 11, 2026 | 5 |
| Oct 10, 2026 | 5 |
| Oct 9, 2026 | 5 |
| Oct 8, 2026 | 5 |
| Oct 7, 2026 | 5 |
| Oct 6, 2026 | 5 |
| Oct 5, 2026 | 5 |
| Oct 4, 2026 | 5 |
| Oct 3, 2026 | 5 |
Map
Where M3.NET Transit'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.
| DE-CIX Frankfurt Frankfurt, Germany | 10G | Both Speed differs | |
| EPIX.Katowice Katowice/Silesia, Poland | 100G | Both | |
| Equinix Warsaw Warsaw, Poland | 100G | PeeringDB | |
| Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia | 20G | Both Speed differs | |
| THINX Warsaw Warsaw, Poland | 2 × 20G | Both Speed differs |
These exchanges have a switch in a facility where M3.NET Transit lists itself in PeeringDB, but don't have M3.NET Transit 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.
| GNM-IXAmsterdam, Netherlands | 741 | |
| NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 672 | |
| FogIXPAvers, Switzerland | 532 | |
| EPIX.WarszawaWarsaw, Poland | 483 | |
| TPIX PLWarsaw, Poland | 480 | |
| KleyReXFrankfurt, Germany | 471 | |
| 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland | 283 | |
| Giganet IXNAmsterdam, Frankfurt am Main, Kharkiv, Kyiv, Lviv, Odesa, Warsaw, Zaporizhzhia, Zhytomyr, Ukraine | 268 | |
| NIX.CZPrague, Czechia | 225 | |
| LOCIX FRANKFURTFrankfurt am Main, Germany | 205 | |
| NetIXSofia, Bulgaria | 204 | |
| PITER-IX FrankfurtFrankfurt, Germany | 172 | |
| nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France | 160 | |
| InterLAN-IXBucharest, Romania | 149 | |
| Global-IXAmsterdam, Netherlands | 138 | |
| BIXBudapest, Hungary | 122 | |
| MegaIX FrankfurtFrankfurt, Germany | 114 | |
| ERA-IX FrankfurtFrankfurt, Germany | 85 | |
| Equinix FrankfurtFrankfurt, Germany | 78 | |
| BALT-IXVilnius, Lithuania | 77 | |
| NIX.SKBratislava, Slovakia | 68 | |
| FogIXP FrankfurtFrankfurt, Germany | 67 | |
| RUDAKI-IXKiev, Ukraine | 53 | |
| Giganet IXN FrankfurtFrankfurt, Germany | 50 | |
| Giganet IXN WarsawWarsaw, Poland | 49 | |
| RoNIXBucharest, Romania | 43 | |
| 1-PL FREEWarsaw, Wroclaw, Katowice, Poland | 32 | |
| Balcan-IXBucharest, Romania | 29 | |
| POZIXPoznan, Poland | 28 | |
| 1-DE FREEFrankfurt, Germany | 27 | |
| Giganet IXN OdesaOdessa, Ukraine | 22 | |
| MAINPORT Peer-ExchangeFrankfurt am Main, Germany | 14 | |
| Giganet IXN KharkіvKharkiv, Ukraine | 13 | |
| NIX.CZ FENIXPrague, Czechia | 8 | |
| City-IX FrankfurtFrankfurt, Germany | 7 | |
| 1-CZ FREEPrague, Czechia | 6 | |
| EURASIA-IX.NETIstanbul, Türkiye | 6 | |
| Global Peer ExchangeWashington, United States | 6 |
Facilities (7)
The buildings M3.NET Transit lists in PeeringDB, and how many of the exchanges in each it's on.
| Equinix FR5 - Frankfurt, KleyerStrasseFrankfurt | 3 of 33 | |
| Equinix WA1 - Warsaw, Centrum LIMWarsaw | 2 of 13 | |
| LIM WarsawWarsaw | 1 of 11 | |
| CE Colo PraguePrague | 1 of 8 | |
| 4 Data CenterKatowice | 2 of 7 | |
| ATMAN Data Center Warsaw-1 (WAW-1, Grochowska 21A)Warsaw | 1 of 6 | |
| Quicktel Sp. z o.o.Katowice | No exchange |