ixreport

TBISS: PeeringDB fix list

AS42295 · peeringdb.com/net/18478

PeeringDB

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

Make the changes on TBISS'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 TBISS'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 and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

  2. Bulgaria TurkIX Sofia Sofia, Bulgaria · PeeringDB 4186From 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.

Correct these entries (3)

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 differs400G800G
    • In the entry with IPv4 80.81.196.159: set Speed to 800000 (800G) (now 400000).
  2. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G100G

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

  3. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs2G1G
    • In the entry with IPv4 195.66.231.71: set Speed to 1000 (1G) (now 2000).

Check these entries (1)

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

  1. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846Not on its IX-F export
    IPv4194.68.128.156
    IPv62001:7f8:d:fe::156
    Speed1000 Mbps (1G)

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