ixreport

mitko.com (tivi.bg): PeeringDB fix list

AS35761 · peeringdb.com/net/8511

PeeringDB

2 things to fix in mitko.com (tivi.bg)'s PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on mitko.com (tivi.bg)'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
    IPv4 address missing from PeeringDB185.1.30.61185.1.30.7 185.1.30.61
    IPv6 address missing from PeeringDBnone2001:7f8:8e:4::7
    Port speed differs10G1G
    • In the entry with IPv4 185.1.30.61: set Speed to 1000 (1G) (now 10000).
    • Add an entry: IPv4 185.1.30.7, IPv6 2001:7f8:8e:4::7, speed 1000 (1G), RS peer yes.
  2. Bulgaria BIX.BG Sofia, Bulgaria · PeeringDB 331
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB193.169.198.176 193.169.198.178193.169.198.175 193.169.198.176 193.169.198.178
    • In the entry with IPv4 193.169.198.176: set IPv4 to 193.169.198.175 (now 193.169.198.176).
    • In the entry with IPv4 193.169.198.178: set IPv4 to 193.169.198.176 (now 193.169.198.178).
    • Add an entry: IPv4 193.169.198.178, IPv6 –.

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