AS250.net: PeeringDB fix list

AS250 · peeringdb.com/net/942

PeeringDB

4 things to fix in AS250.net's PeeringDB record, from what its exchanges publish: 2 to add, 2 to check. As of 2026-10-08 20:58 UTC.

Make the changes on AS250.net'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 (2)

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

  1. Germany Community-IX Berlin, Frankfurt, Germany · PeeringDB 1329From 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.

  2. Finland TREX Tampere Tampere, Finland · PeeringDB 328From its IX-F export
    IPv4195.140.192.19
    IPv62001:7f8:1d:4::fa: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.

Check these entries (2)

In PeeringDB, but on none of the exchange's own lists. If AS250.net has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Norway FIXO Oslo, Norway · PeeringDB 453Not on its website members list
    IPv491.198.176.52
    IPv6–
    Speed1000 Mbps (1G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

  2. Sweden SOLIX MTU1500 Stockholm, Sweden · PeeringDB 128Not on its website members list
    IPv4193.110.13.139
    IPv62001:7f8:21:9::139
    Speed1000 Mbps (1G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

From ixreport.com/net/250/: 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.