ixreport

ClimaxNET

AS198525 · ClimaxNET

ClimaxNET Sp. z o.o.

5Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
3Using the route servers
1To fix in PeeringDB
2Facilities in PeeringDB

Tools: Where can I peer with ClimaxNET? · Where should ClimaxNET peer next? · Compare ClimaxNET 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 ClimaxNET's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-11-19 12:40 UTC.

Make the changes on ClimaxNET'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 ClimaxNET's PeeringDB record. Add one entry per connection with these values.

  1. Poland 1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland · PeeringDB 3958From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

Exchanges over time

0246Oct 3, 2026Nov 19, 20265
Show as a table
DateExchanges
Nov 19, 20265
Nov 18, 20265
Nov 17, 20265
Nov 16, 20265
Nov 15, 20265
Nov 14, 20265
Nov 13, 20265
Nov 12, 20265
Nov 11, 20265
Nov 10, 20265
Nov 9, 20265
Nov 8, 20265
Nov 7, 20265
Nov 6, 20265
Nov 5, 20265
Nov 4, 20265
Nov 3, 20265
Nov 2, 20265
Nov 1, 20265
Oct 31, 20265
Oct 30, 20265
Oct 29, 20265
Oct 28, 20265
Oct 27, 20265
Oct 26, 20265
Oct 25, 20265
Oct 24, 20265
Oct 23, 20265
Oct 22, 20265
Oct 21, 20265
Oct 20, 20265
Oct 19, 20265
Oct 18, 20265
Oct 17, 20265
Oct 16, 20265
Oct 15, 20265
Oct 14, 20265
Oct 13, 20265
Oct 12, 20265
Oct 11, 20265
Oct 10, 20265
Oct 9, 20265
Oct 8, 20265
Oct 7, 20265
Oct 6, 20265
Oct 5, 20265
Oct 4, 20265
Oct 3, 20265

Map

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

Poland 1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland Not in PeeringDB
Poland 1-PL FREE Warsaw, Wroclaw, Katowice, Poland 194.246.39.36 2001:7f8:16e::36 10G Yes PeeringDB
Poland EPIX.Katowice Katowice/Silesia, Poland 178.216.41.120 2001:7f8:5b::376 40G Yes Both
Poland EPIX.Warszawa Warsaw, Poland 89.46.144.131 2001:678:3ac::131 10G Yes Both
Poland TPIX PL Warsaw, Poland 195.149.233.224 2001:7f8:27::19:8525:1 10G Both

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

These exchanges have a switch in a facility where ClimaxNET lists itself in PeeringDB, but don't have ClimaxNET 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.

Netherlands GNM-IXAmsterdam, Netherlands 741 LIM Warsaw; 4 Data Center
Ukraine Giganet IXNAmsterdam, Frankfurt am Main, Kharkiv, Kyiv, Lviv, Odesa, Warsaw, Zaporizhzhia, Zhytomyr, Ukraine 268 LIM Warsaw
Bulgaria NetIXSofia, Bulgaria 204 LIM Warsaw
Poland THINX WarsawWarsaw, Poland 194 LIM Warsaw; 4 Data Center
Netherlands Global-IXAmsterdam, Netherlands 138 4 Data Center
Ukraine RUDAKI-IXKiev, Ukraine 53 LIM Warsaw
Poland Giganet IXN WarsawWarsaw, Poland 49 LIM Warsaw
Poland POZIXPoznan, Poland 28 LIM Warsaw
Facilities (2)

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

Poland LIM WarsawWarsaw 4 of 11
Poland 4 Data CenterKatowice 4 of 7