ixreport

PROIPLOM: PeeringDB fix list

AS49715

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

AS49715 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 PROIPLOM's PeeringDB record. Add one entry per connection with these values.

  1. Poland EPIX.Warszawa Warsaw, Poland · PeeringDB 474From its IX-F export
    IPv489.46.144.134
    IPv62001:678:3ac::712
    Speed100000 Mbps (100G)
    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

    4 connections, so 4 entries:

    IPv4212.91.0.156
    IPv6–
    Speed30000 Mbps (30G)
    RS peerNot published
    IPv4212.91.0.149
    IPv6–
    Speed30000 Mbps (30G)
    RS peerNot published
    IPv4212.91.1.77
    IPv6–
    Speed30000 Mbps (30G)
    RS peerNot published
    IPv4212.91.1.78
    IPv6–
    Speed30000 Mbps (30G)
    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.233.208
    IPv6–
    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/49715/: 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.