ixreport

kbto: PeeringDB fix list

AS200437

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

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

Add these exchanges (2)

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

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

    2 connections, so 2 entries:

    IPv4–
    IPv62001:7f8:60::2:1
    Speed2000 Mbps (2G)
    RS peerNot published
    IPv4212.91.0.162
    IPv6–
    Speed2000 Mbps (2G)
    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.

  2. Poland TPIX PL Warsaw, Poland · PeeringDB 482From its IX-F export and website members list
    IPv4195.149.232.225
    IPv62001:7f8:27::20:437: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/200437/: 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.