ixreport

awhost

AS201112

awHost

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

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

Make the changes on awhost'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 awhost'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

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 awhost'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 20G, at the 2 of 3 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.39 2001:7f8:16e::39 10G Yes PeeringDB
Poland THINX Warsaw Warsaw, Poland 212.91.0.94 2001:7f8:60:0:13:20:1112:1 10G Both

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

These exchanges have a switch in a facility where awhost lists itself in PeeringDB, but don't have awhost 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
Poland EPIX.WarszawaWarsaw, Poland 483 LIM Warsaw
Poland TPIX PLWarsaw, Poland 480 LIM Warsaw
Ukraine Giganet IXNAmsterdam, Frankfurt am Main, Kharkiv, Kyiv, Lviv, Odesa, Warsaw, Zaporizhzhia, Zhytomyr, Ukraine 268 LIM Warsaw
Bulgaria NetIXSofia, Bulgaria 204 LIM Warsaw
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 awhost lists in PeeringDB, and how many of the exchanges in each it's on.

Poland LIM WarsawWarsaw 3 of 11
Poland Datahouse WarsawWarsaw No exchange