ixreport

ESCOM: PeeringDB fix list

AS25374 · peeringdb.com/net/23379

PeeringDB

2 things to fix in ESCOM's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on ESCOM'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 (2)

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
    IPv4 address missing from PeeringDB193.169.198.225193.169.198.225 193.169.198.244
    IPv6 address missing from PeeringDB2001:7f8:58::631e:0:12001:7f8:58::631e:0:1 2001:7f8:58::631e:0:2
    • Add an entry: IPv4 193.169.198.244, IPv6 2001:7f8:58::631e:0:2.
  2. Bulgaria NetIX Sofia, Bulgaria · PeeringDB 699
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB185.1.226.41185.1.226.41 185.1.226.103
    IPv6 address missing from PeeringDB2001:67c:29f0::2:5374:12001:67c:29f0::2:5374:1 2001:67c:29f0::2:5374:2
    • Add an entry: IPv4 185.1.226.103, IPv6 2001:67c:29f0::2:5374:2, RS peer yes.

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