ixreport

EGT DIGITAL EOOD: PeeringDB fix list

AS215941 · peeringdb.com/net/35647

PeeringDB

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

Make the changes on EGT DIGITAL EOOD'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 B-IX Sofia, Bulgaria · PeeringDB 326
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:8e:4::6
    • In the entry with IPv4 185.1.30.6: set IPv6 to 2001:7f8:8e:4::6 (now empty).
  2. Bulgaria NetIX Sofia, Bulgaria · PeeringDB 699
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB185.1.227.22185.1.227.22 185.1.227.23
    IPv6 address missing from PeeringDBnone2001:67c:29f0::21:5941:1
    • Add an entry: IPv4 185.1.227.23, IPv6 2001:67c:29f0::21:5941:1, 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/215941/: 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.