ixreport

DCC-BG

AS51582

Cifrova Kabelna Korporacia EOOD

4Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
SelectivePeering policy
4Using the route servers
3To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with DCC-BG? · Where should DCC-BG peer next? · Compare DCC-BG with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

3 things to fix in DCC-BG's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on DCC-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 (3)

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.197 193.169.199.73193.169.198.196 193.169.198.197 193.169.199.73
    • In the entry with IPv4 193.169.199.73: set IPv4 to 193.169.198.196 (now 193.169.199.73).
    • Add an entry: IPv4 193.169.199.73, IPv6 –.
  2. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2a03:5f80:4:2::236:117
    • In the entry with IPv4 178.18.236.117: set IPv6 to 2a03:5f80:4:2::236:117 (now empty).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  3. Bulgaria MegaIX Sofia Sofia, Bulgaria · PeeringDB 1056
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB91.212.235.5391.212.235.10 91.212.235.53
    IPv6 address missing from PeeringDBnone2001:7f8:9f::a 2001:7f8:9f::a5:1582:2
    • In the entry with IPv4 91.212.235.53: set IPv6 to 2001:7f8:9f::a5:1582:2 (now empty).
    • Add an entry: IPv4 91.212.235.10, IPv6 2001:7f8:9f::a, RS peer no.

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Exchanges over time

01234Oct 3, 2026Nov 19, 20264
Show as a table
DateExchanges
Nov 19, 20264
Nov 18, 20264
Nov 17, 20264
Nov 16, 20264
Nov 15, 20264
Nov 14, 20264
Nov 13, 20264
Nov 12, 20264
Nov 11, 20264
Nov 10, 20264
Nov 9, 20264
Nov 8, 20264
Nov 7, 20264
Nov 6, 20264
Nov 5, 20264
Nov 4, 20264
Nov 3, 20264
Nov 2, 20264
Nov 1, 20264
Oct 31, 20264
Oct 30, 20264
Oct 29, 20264
Oct 28, 20264
Oct 27, 20264
Oct 26, 20264
Oct 25, 20264
Oct 24, 20264
Oct 23, 20264
Oct 22, 20264
Oct 21, 20264
Oct 20, 20264
Oct 19, 20264
Oct 18, 20264
Oct 17, 20264
Oct 16, 20264
Oct 15, 20264
Oct 14, 20264
Oct 13, 20264
Oct 12, 20264
Oct 11, 20264
Oct 10, 20264
Oct 9, 20264
Oct 8, 20264
Oct 7, 20264
Oct 6, 20264
Oct 5, 20264
Oct 4, 20264
Oct 3, 20264

Map

Where DCC-BG's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 320G across 4 exchanges.

Bulgaria BIX.BG Sofia, Bulgaria 193.169.198.197
193.169.199.73
2001:7f8:58::c97e:0:1
2001:7f8:58::c97e:0:2
2 × 100G Yes Both IPv4 not in PeeringDB
Netherlands Global-IX Amsterdam, Netherlands 109.239.137.140 10G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.236.117 10G Yes Both IPv6 not in PeeringDB
Bulgaria MegaIX Sofia Sofia, Bulgaria 91.212.235.53 100G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDB

DCC-BG lists no facilities in PeeringDB.