Bulgartel: PeeringDB fix list
AS44814 · peeringdb.com/net/23513
One thing to fix in Bulgartel's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on Bulgartel'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 (1)
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.159 193.169.198.159 193.169.198.160 IPv6 address missing from PeeringDB none 2001:7f8:58::af0e:0:1 - In the entry with IPv4 193.169.198.159: set IPv6 to 2001:7f8:58::af0e:0:1 (now empty).
- Add an entry: IPv4 193.169.198.160, IPv6 –.
From ixreport.com/net/44814/: 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.