ixreport

BITel: PeeringDB fix list

AS198967 · peeringdb.com/net/12340

PeeringDB

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

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

  1. Germany MegaIX Frankfurt Frankfurt, Germany · PeeringDB 676From its IX-F export
    IPv462.69.146.27
    IPv62001:7f8:8:20:3:937:0:1
    SpeedNot published
    RS peerNo

    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 differs70G400G
    • In the entry with IPv4 80.81.195.90: set Speed to 400000 (400G) (now 70000).

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