DCC-BG
AS51582
Cifrova Kabelna Korporacia EOOD
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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 193.169.198.197 193.169.199.73 193.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 –.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2a03: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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 91.212.235.53 91.212.235.10 91.212.235.53 IPv6 address missing from PeeringDB none 2001: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
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 4 |
| Nov 18, 2026 | 4 |
| Nov 17, 2026 | 4 |
| Nov 16, 2026 | 4 |
| Nov 15, 2026 | 4 |
| Nov 14, 2026 | 4 |
| Nov 13, 2026 | 4 |
| Nov 12, 2026 | 4 |
| Nov 11, 2026 | 4 |
| Nov 10, 2026 | 4 |
| Nov 9, 2026 | 4 |
| Nov 8, 2026 | 4 |
| Nov 7, 2026 | 4 |
| Nov 6, 2026 | 4 |
| Nov 5, 2026 | 4 |
| Nov 4, 2026 | 4 |
| Nov 3, 2026 | 4 |
| Nov 2, 2026 | 4 |
| Nov 1, 2026 | 4 |
| Oct 31, 2026 | 4 |
| Oct 30, 2026 | 4 |
| Oct 29, 2026 | 4 |
| Oct 28, 2026 | 4 |
| Oct 27, 2026 | 4 |
| Oct 26, 2026 | 4 |
| Oct 25, 2026 | 4 |
| Oct 24, 2026 | 4 |
| Oct 23, 2026 | 4 |
| Oct 22, 2026 | 4 |
| Oct 21, 2026 | 4 |
| Oct 20, 2026 | 4 |
| Oct 19, 2026 | 4 |
| Oct 18, 2026 | 4 |
| Oct 17, 2026 | 4 |
| Oct 16, 2026 | 4 |
| Oct 15, 2026 | 4 |
| Oct 14, 2026 | 4 |
| Oct 13, 2026 | 4 |
| Oct 12, 2026 | 4 |
| Oct 11, 2026 | 4 |
| Oct 10, 2026 | 4 |
| Oct 9, 2026 | 4 |
| Oct 8, 2026 | 4 |
| Oct 7, 2026 | 4 |
| Oct 6, 2026 | 4 |
| Oct 5, 2026 | 4 |
| Oct 4, 2026 | 4 |
| Oct 3, 2026 | 4 |
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.
| BIX.BG Sofia, Bulgaria | 2 × 100G | Both IPv4 not in PeeringDB | |
| Global-IX Amsterdam, Netherlands | 10G | PeeringDB | |
| GNM-IX Amsterdam, Netherlands | 10G | Both IPv6 not in PeeringDB | |
| MegaIX Sofia Sofia, Bulgaria | 100G | Both IPv4 not in PeeringDBIPv6 not in PeeringDB |
DCC-BG lists no facilities in PeeringDB.