Cooolbox: PeeringDB fix list

AS9070 · peeringdb.com/net/1442

PeeringDB

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

Make the changes on Cooolbox'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 Cooolbox'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
    IPv4185.1.226.94
    IPv62001:67c:29f0::9070:2
    SpeedNot published
    RS peerYes

    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. Bulgaria BIX.BG Sofia, Bulgaria · PeeringDB 331
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDB2001:7f8:58::236e:0:62001:7f8:58::236e:0:1 2001:7f8:58::236e:0:6
    • In the entry with IPv4 193.169.198.116: set IPv6 to 2001:7f8:58::236e:0:1 (now empty).
    • In the entry with IPv4 193.169.198.121: set IPv6 to 2001:7f8:58::236e:0:6 (now empty).
    • In the entry with IPv4 193.169.198.122: set IPv6 to (empty) (now 2001:7f8:58::236e:0:6).

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