ixreport

HitMe.pl

AS50840

HITME.PL

3Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
ContentType
OpenPeering policy
3Using the route servers
1To fix in PeeringDB
1Facility in PeeringDB

Tools: Where can I peer with HitMe.pl? · Where should HitMe.pl peer next? · Compare HitMe.pl with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

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

Make the changes on HitMe.pl'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. Poland THINX Warsaw Warsaw, Poland · PeeringDB 481
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G100G
    • Add an entry: IPv4 212.91.1.128, IPv6 –, speed 100000 (100G).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

Exchanges over time

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

Map

Where HitMe.pl'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 220G across 3 exchanges.

Poland EPIX.Warszawa Warsaw, Poland 89.46.145.92 2001:678:3ac::345 10G Yes Both
Poland Equinix Warsaw Warsaw, Poland 195.182.218.59 10G Yes PeeringDB
Poland THINX Warsaw Warsaw, Poland 212.91.1.128
212.91.1.129
2001:7f8:60:0:5011:5:840:1 2 × 100G Yes Both Speed differs

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

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

Poland TPIX PLWarsaw, Poland 480 ATMAN Data Center Warsaw-2 (WAW-2, Konstruktorska 5)
Poland 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland 283 ATMAN Data Center Warsaw-2 (WAW-2, Konstruktorska 5)
Ukraine Giganet IXNAmsterdam, Frankfurt am Main, Kharkiv, Kyiv, Lviv, Odesa, Warsaw, Zaporizhzhia, Zhytomyr, Ukraine 268 ATMAN Data Center Warsaw-2 (WAW-2, Konstruktorska 5)
Poland Giganet IXN WarsawWarsaw, Poland 49 ATMAN Data Center Warsaw-2 (WAW-2, Konstruktorska 5)
Netherlands Giganet IXN AmsterdamAmsterdam, Netherlands 47 ATMAN Data Center Warsaw-2 (WAW-2, Konstruktorska 5)
Poland 1-PL FREEWarsaw, Wroclaw, Katowice, Poland 32 ATMAN Data Center Warsaw-2 (WAW-2, Konstruktorska 5)
Facilities (1)

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

Poland ATMAN Data Center Warsaw-2 (WAW-2, Konstruktorska 5)Warsaw 2 of 8