JSC Chitatehenergo: PeeringDB fix list
AS58067 · peeringdb.com/net/11818
2 things to fix in JSC Chitatehenergo's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on JSC Chitatehenergo's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Add these exchanges (1)
On the exchange's own member list, but not in JSC Chitatehenergo's PeeringDB record. Add one entry per connection with these values.
-
IPv4 195.208.210.27 IPv6 2001:7f8:20:101::210:27 Speed Not published 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.
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 178.18.225.105 178.18.225.166 178.18.224.26 178.18.225.105 178.18.225.166 IPv6 address missing from PeeringDB 2a03:5f80:4::225:166 2a03:5f80:4::224:26 2a03:5f80:4::225:105 2a03:5f80:4::225:166 Port speed differs 20G + 10G 70G + 20G + 10G - In the entry with IPv4 178.18.225.105: set IPv6 to 2a03:5f80:4::225:105 (now empty).
- Add an entry: IPv4 178.18.224.26, IPv6 2a03:5f80:4::224:26, speed 70000 (70G), 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/58067/: 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.