ixreport

Forthnet: PeeringDB fix list

AS1241 · peeringdb.com/net/3567

PeeringDB

2 things to fix in Forthnet's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 21:56 UTC.

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

  1. Bulgaria NetIX Sofia, Bulgaria · PeeringDB 699From its IX-F export and website members list

    The exchange's IX-F export and website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

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

Correct these entries (1)

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. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 40G2 × 300G
    • In the entry with IPv4 80.81.193.231: set Speed to 300000 (300G) (now 40000).
    • In the entry with IPv4 80.81.195.130: set Speed to 300000 (300G) (now 40000).

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