ixreport

EMITEL: PeeringDB fix list

AS197064

3 things to fix in EMITEL's PeeringDB record, from what its exchanges publish: 3 to add. As of 2026-10-08 18:53 UTC.

AS197064 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.

Add these exchanges (3)

On the exchange's own member list, but not in EMITEL's PeeringDB record. Add one entry per connection with these values.

  1. Poland EPIX.Katowice Katowice/Silesia, Poland · PeeringDB 491From its IX-F export
    IPv4178.216.41.88
    IPv62001:7f8:5b::344
    Speed10000 Mbps (10G)
    RS peerYes

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

  2. Poland THINX Warsaw Warsaw, Poland · PeeringDB 481From its IX-F export

    2 connections, so 2 entries:

    IPv4–
    IPv62001:7f8:60::13:11
    Speed10000 Mbps (10G)
    RS peerNot published
    IPv4212.91.0.89
    IPv6–
    Speed10000 Mbps (10G)
    RS peerNot published

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

  3. Poland TPIX PL Warsaw, Poland · PeeringDB 482From its IX-F export and website members list
    IPv4195.149.232.15
    IPv62001:7f8:27::19:7064:1
    SpeedNot published
    RS peerNot published

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

From ixreport.com/net/197064/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.