Neotel: PeeringDB fix list

AS34772 · peeringdb.com/net/2306

PeeringDB

One thing to fix in Neotel's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Neotel's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

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. Bulgaria NetIX Sofia, Bulgaria · PeeringDB 699
    ProblemPeeringDB hasThe export has
    IPv6 address differs2001:67c:29f0::3:4772:22001:67c:29f0::3:4772:1
    • In the entry with IPv4 185.1.226.232: set IPv6 to 2001:67c:29f0::3:4772:1 (now 2001:67c:29f0::3:4772:2).

    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/34772/: 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.