Rostelecom
AS12389 · RT
ROSTELECOM
Tools: Where can I peer with Rostelecom? · Where should Rostelecom peer next? · Compare Rostelecom with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
12 things to fix in Rostelecom's PeeringDB record, from what its exchanges publish: 9 to add, 2 to correct, 1 to check. As of 2026-11-19 12:40 UTC.
Make the changes on Rostelecom'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 (9)
On the exchange's own member list, but not in Rostelecom's PeeringDB record. Add one entry per connection with these values.
-
IPv4 194.85.107.74 IPv6 2001:7f8:20:301::107:74 Speed Not published 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.
-
3 connections, so 3 entries:
IPv4 195.208.208.238 IPv6 2001:7f8:20:101::208:238 Speed Not published RS peer Yes IPv4 195.208.209.65 IPv6 2001:7f8:20:101::209:65 Speed Not published RS peer Yes IPv4 195.208.208.183 IPv6 2001:7f8:20:101::208:183 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.
-
IPv4 193.232.87.43 IPv6 2001:7f8:20:401::87:43 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.
-
IPv4 193.232.140.42 IPv6 2001:7f8:20:501::140:42 Speed Not published 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.
-
6 connections, so 6 entries:
IPv4 194.226.102.135 IPv6 2001:7f8:20:202::102:135 Speed Not published RS peer Yes IPv4 194.226.102.140 IPv6 2001:7f8:20:202::102:140 Speed Not published RS peer Yes IPv4 194.226.100.140 IPv6 2001:7f8:20:201::100:140 Speed Not published RS peer Yes IPv4 194.226.100.135 IPv6 2001:7f8:20:201::100:135 Speed Not published RS peer Yes IPv4 194.226.100.93 IPv6 2001:7f8:20:201::100:93 Speed Not published RS peer Yes IPv4 194.226.102.93 IPv6 2001:7f8:20:202::102:93 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.
-
IPv4 193.232.135.47 IPv6 2001:7f8:20:601::135:47 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.
-
IPv4 193.232.136.46 IPv6 2001:7f8:20:701::136:46 Speed Not published 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.
-
IPv4 195.69.119.182 IPv6 2001:7f8:d:fb::182 Speed Not published RS peer No -
IPv4 195.245.240.182 IPv6 2001:7f8:d:fc::182 Speed Not published RS peer No
Correct these entries (2)
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.153 178.18.225.220 178.18.236.63 178.18.224.129 178.18.225.153 178.18.225.220 178.18.225.239 178.18.236.63 IPv6 address missing from PeeringDB 2a03:5f80:4::225:153 2a03:5f80:4::225:220 2a03:5f80:4:2::236:63 2a03:5f80:4::224:129 2a03:5f80:4::225:153 2a03:5f80:4::225:220 2a03:5f80:4::225:239 2a03:5f80:4:2::236:63 Port speed differs 2 × 200G + 100G 400G + 2 × 200G + 2 × 100G - Add an entry: IPv4 178.18.225.239, IPv6 2a03:5f80:4::225:239, speed 100000 (100G), RS peer no.
- Add an entry: IPv4 178.18.224.129, IPv6 2a03:5f80:4::224:129, speed 400000 (400G), 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.
-
Problem PeeringDB has The export has IPv4 address differs 194.68.128.27 194.68.128.182 IPv6 address differs 2001:7f8:d:fe::27 2001:7f8:d:fe::182 - In the entry with IPv4 194.68.128.27: set IPv4 to 194.68.128.182 (now 194.68.128.27); set IPv6 to 2001:7f8:d:fe::182 (now 2001:7f8:d:fe::27).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Rostelecom has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 101.203.88.213 IPv6 2001:de8:c::1:2389:1 Speed 100000 Mbps (100G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 19 |
| Nov 18, 2026 | 19 |
| Nov 17, 2026 | 17 |
| Nov 16, 2026 | 19 |
| Nov 15, 2026 | 19 |
| Nov 14, 2026 | 19 |
| Nov 13, 2026 | 19 |
| Nov 12, 2026 | 19 |
| Nov 11, 2026 | 19 |
| Nov 10, 2026 | 19 |
| Nov 9, 2026 | 19 |
| Nov 8, 2026 | 19 |
| Nov 7, 2026 | 19 |
| Nov 6, 2026 | 19 |
| Nov 5, 2026 | 19 |
| Nov 4, 2026 | 19 |
| Nov 3, 2026 | 19 |
| Nov 2, 2026 | 19 |
| Nov 1, 2026 | 19 |
| Oct 31, 2026 | 19 |
| Oct 30, 2026 | 19 |
| Oct 29, 2026 | 19 |
| Oct 28, 2026 | 19 |
| Oct 27, 2026 | 19 |
| Oct 26, 2026 | 19 |
| Oct 25, 2026 | 19 |
| Oct 24, 2026 | 19 |
| Oct 23, 2026 | 19 |
| Oct 22, 2026 | 19 |
| Oct 21, 2026 | 19 |
| Oct 20, 2026 | 19 |
| Oct 19, 2026 | 17 |
| Oct 18, 2026 | 19 |
| Oct 17, 2026 | 19 |
| Oct 16, 2026 | 19 |
| Oct 15, 2026 | 19 |
| Oct 14, 2026 | 19 |
| Oct 13, 2026 | 19 |
| Oct 12, 2026 | 19 |
| Oct 11, 2026 | 19 |
| Oct 10, 2026 | 19 |
| Oct 9, 2026 | 17 |
| Oct 8, 2026 | 19 |
| Oct 7, 2026 | 19 |
| Oct 6, 2026 | 17 |
| Oct 5, 2026 | 17 |
| Oct 4, 2026 | 17 |
| Oct 3, 2026 | 17 |
Map
Where Rostelecom'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.
| BBIX Hong Kong Hong Kong, Hong Kong | 20G | PeeringDB | |
| BBIX Tokyo Tokyo, Japan | 100G | PeeringDB only | |
| DE-CIX Frankfurt Frankfurt, Germany | 700G | Both | |
| Equinix Hong Kong Hong Kong, Hong Kong | 20G | PeeringDB | |
| Equinix Tokyo Tokyo, Japan | 20G | PeeringDB | |
| GNM-IX Amsterdam, Netherlands | 2 × 200G + 100G | Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs | |
| JPNAP Tokyo Tokyo, Japan | 10G | PeeringDB | |
| MSK-IX Ekaterinburg Ekaterinburg, Russia | Not in PeeringDB | ||
| MSK-IX Moscow Moscow, Russia | Not in PeeringDB | ||
| MSK-IX Novosibirsk Novosibirsk, Russia | Not in PeeringDB | ||
| MSK-IX Rostov-on-Don Rostov-on-Don, Russia | Not in PeeringDB | ||
| MSK-IX Saint-Petersburg St.Petersburg, Russia | Not in PeeringDB | ||
| MSK-IX Samara Samara, Russia | Not in PeeringDB | ||
| MSK-IX Vladivostok Vladivostok, Russia | Not in PeeringDB | ||
| Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden | 100G | Both IPv4 differsIPv6 differs | |
| Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden | Not in PeeringDB | ||
| Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden | 100G | Both | |
| Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden | Not in PeeringDB | ||
| NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 200G | Both |
These exchanges have a switch in a facility where Rostelecom lists itself in PeeringDB, but don't have Rostelecom as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.
| KleyReXFrankfurt, Germany | 471 | |
| HKIXHong Kong, Hong Kong | 300 | |
| 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland | 283 | |
| JPIX TOKYOTokyo, Japan | 275 | |
| NetIXSofia, Bulgaria | 204 | |
| Global-IXAmsterdam, Netherlands | 138 | |
| ERA-IX FrankfurtFrankfurt, Germany | 85 | |
| STHIX - StockholmStockholm, Sweden | 84 | |
| SONIX StockholmStockholm, Sweden | 81 | |
| BALT-IXVilnius, Lithuania | 77 | |
| SOLIX MTU1500Stockholm, Sweden | 58 | |
| Hong Kong Global Internet ExchangeHong Kong, Hong Kong | 33 | |
| Japan Community IXJapan, Japan | 32 | |
| DIX-IETokyo, Japan | 22 | |
| IAIXHong Kong, Hong Kong | 20 | |
| SOLIX MTU4470Stockholm, Sweden | 18 | |
| Equinix StockholmStockholm, Sweden | 17 | |
| Japan Community IX - INIXPJapan, Japan | 15 | |
| MAINPORT Peer-ExchangeFrankfurt am Main, Germany | 14 | |
| KeFF-IXStockholm, Gothenburg, Malmö, Amsterdam, Sweden | 11 | |
| Global Peer ExchangeWashington, United States | 6 |
Facilities (5)
The buildings Rostelecom lists in PeeringDB, and how many of the exchanges in each it's on.
| Equinix SK1 - Stockholm, BrommaStockholm | 5 of 14 | |
| Equinix HK1 - Hong KongTsuen Wan | 2 of 6 | |
| NTT DATA Otemachi BldgTokyo | 1 of 6 | |
| ITENOS Frankfurt (FRA1)Frankfurt | 2 of 5 | |
| MEGA-i (iAdvantage Hong Kong)Hong Kong | 1 of 4 |
Recent changes Search them
- Nov 18, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Novosibirsk
- Nov 18, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Vladivostok
- Nov 17, 2026 [IXF] AS12389 Rostelecom left MSK-IX Novosibirsk
- Nov 17, 2026 [IXF] AS12389 Rostelecom left MSK-IX Vladivostok
- Nov 9, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Novosibirsk
- Nov 9, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Vladivostok
- Nov 9, 2026 [IXF] AS12389 Rostelecom left MSK-IX Novosibirsk
- Nov 9, 2026 [IXF] AS12389 Rostelecom left MSK-IX Vladivostok
- Nov 5, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Novosibirsk
- Nov 5, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Vladivostok
- Nov 5, 2026 [IXF] AS12389 Rostelecom left MSK-IX Novosibirsk
- Nov 5, 2026 [IXF] AS12389 Rostelecom left MSK-IX Vladivostok
- Nov 2, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Novosibirsk
- Nov 2, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Vladivostok
- Nov 2, 2026 [IXF] AS12389 Rostelecom left MSK-IX Novosibirsk
- Nov 2, 2026 [IXF] AS12389 Rostelecom left MSK-IX Vladivostok
- Oct 29, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Novosibirsk
- Oct 29, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Vladivostok
- Oct 29, 2026 [IXF] AS12389 Rostelecom left MSK-IX Novosibirsk
- Oct 29, 2026 [IXF] AS12389 Rostelecom left MSK-IX Vladivostok
- Oct 21, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Novosibirsk
- Oct 21, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Vladivostok
- Oct 21, 2026 [IXF] AS12389 Rostelecom left MSK-IX Novosibirsk
- Oct 21, 2026 [IXF] AS12389 Rostelecom left MSK-IX Vladivostok
- Oct 20, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Novosibirsk
- Oct 20, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Vladivostok
- Oct 19, 2026 [IXF] AS12389 Rostelecom left MSK-IX Novosibirsk
- Oct 19, 2026 [IXF] AS12389 Rostelecom left MSK-IX Vladivostok
- Oct 10, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Novosibirsk
- Oct 10, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Vladivostok
- Oct 9, 2026 [IXF] AS12389 Rostelecom left MSK-IX Novosibirsk
- Oct 9, 2026 [IXF] AS12389 Rostelecom left MSK-IX Vladivostok
- Oct 8, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Novosibirsk
- Oct 8, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Vladivostok
- Oct 8, 2026 [IXF] AS12389 Rostelecom left MSK-IX Novosibirsk
- Oct 8, 2026 [IXF] AS12389 Rostelecom left MSK-IX Vladivostok