ixreport

JSC Chitatehenergo

AS58067

JSC Chitatechenergo

3Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
NSPType
OpenPeering policy
3Using the route servers
2To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with JSC Chitatehenergo? · Where should JSC Chitatehenergo peer next? · Compare JSC Chitatehenergo with another network

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

PeeringDB fix list Printable page · CSV

2 things to fix in JSC Chitatehenergo's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-11-19 12:40 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.

  1. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100From its IX-F export and website members list
    IPv4195.208.210.27
    IPv62001:7f8:20:101::210:27
    SpeedNot published
    RS peerYes

    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.

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv4 address differs178.18.225.105 178.18.225.166178.18.224.26 178.18.225.166
    IPv6 address missing from PeeringDB2a03:5f80:4::225:1662a03:5f80:4::224:26 2a03:5f80:4::225:166
    Port speed differs20G + 10G70G + 10G
    • The entry with IPv4 178.18.225.105, IPv6 – isn't in the export: delete it if that connection is gone.
    • In the entry with IPv4 178.18.225.166: set Speed to 10000 (10G) (now 20000).
    • 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.

Exchanges over time

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

Map

Where JSC Chitatehenergo'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 31G, at the 2 of 3 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Russia BAIKAL-IX Irkutsk, Russia 185.1.76.24 1G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.225.105
178.18.225.166
2a03:5f80:4::225:166 20G + 10G Yes Both IPv4 differsIPv6 not in PeeringDBSpeed differs
Russia MSK-IX Moscow Moscow, Russia 195.208.210.27 2001:7f8:20:101::210:27 Yes Not in PeeringDB

JSC Chitatehenergo lists no facilities in PeeringDB.