ixreport

INEA

AS13110

INEA sp. z o.o.

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

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

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

  1. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31From its IX-F export and website members list
    IPv480.81.195.92
    IPv62001:7f8::3336:0:1
    Speed1200000 Mbps (1.2T)
    RS peerYes

Correct these entries (2)

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 differs100G200G
    • In the entry with IPv4 212.91.1.23: set Speed to 200000 (200G) (now 100000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. Poland TPIX PL Warsaw, Poland · PeeringDB 482
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:27::1:3110:2
    • In the entry with IPv4 195.149.232.217: set IPv6 to 2001:7f8:27::1:3110:2 (now empty).

    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

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

Map

Where INEA'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 1.4T across 4 exchanges.

Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.195.92 2001:7f8::3336:0:1 1.2T 69 routes Not in PeeringDB
Poland Equinix Warsaw Warsaw, Poland 195.182.218.31 100G Yes PeeringDB
Poland THINX Warsaw Warsaw, Poland 212.91.1.23 100G Both Speed differs
Poland TPIX PL Warsaw, Poland 195.149.232.217 40G Yes Both IPv6 not in PeeringDB

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

These exchanges have a switch in a facility where INEA lists itself in PeeringDB, but don't have INEA 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 EPIX.PoznanPoznan, Poland 23 Beyond.pl - DC2 / Poznan
Facilities (2)

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

Poland Beyond.pl - DC1 / PoznanPoznan 2 of 2
Poland Beyond.pl - DC2 / PoznanPoznan 1 of 2