VimpelCom
AS3216 · Beeline, VimpelCom, Sovintel, Golden Telecom, Sovam
VimpelCom / Beeline / Golden Telecom / Sovam
Tools: Where can I peer with VimpelCom? · Where should VimpelCom peer next? · Compare VimpelCom with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
4 things to fix in VimpelCom's PeeringDB record, from what its exchanges publish: 2 to add, 2 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on VimpelCom'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 (2)
On the exchange's own member list, but not in VimpelCom's PeeringDB record. Add one entry per connection with these values.
-
IPv4 195.69.119.151 IPv6 2001:7f8:d:fb::151 Speed Not published RS peer Yes -
IPv4 195.245.240.151 IPv6 2001:7f8:d:fc::151 Speed Not published RS peer Yes
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 Port speed differs 100G 200G - In the entry with IPv4 80.81.192.243: set Speed to 200000 (200G) (now 100000).
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 178.18.236.95 178.18.225.35 178.18.236.95 IPv6 address missing from PeeringDB 2a03:5f80:4:2::236:95 2a03:5f80:4::225:35 2a03:5f80:4:2::236:95 - Add an entry: IPv4 178.18.225.35, IPv6 2a03:5f80:4::225:35, speed 100000 (100G), 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
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 15 |
| Nov 18, 2026 | 15 |
| Nov 17, 2026 | 15 |
| Nov 16, 2026 | 15 |
| Nov 15, 2026 | 15 |
| Nov 14, 2026 | 15 |
| Nov 13, 2026 | 15 |
| Nov 12, 2026 | 15 |
| Nov 11, 2026 | 15 |
| Nov 10, 2026 | 15 |
| Nov 9, 2026 | 15 |
| Nov 8, 2026 | 15 |
| Nov 7, 2026 | 15 |
| Nov 6, 2026 | 15 |
| Nov 5, 2026 | 15 |
| Nov 4, 2026 | 15 |
| Nov 3, 2026 | 15 |
| Nov 2, 2026 | 15 |
| Nov 1, 2026 | 15 |
| Oct 31, 2026 | 15 |
| Oct 30, 2026 | 15 |
| Oct 29, 2026 | 15 |
| Oct 28, 2026 | 15 |
| Oct 27, 2026 | 15 |
| Oct 26, 2026 | 15 |
| Oct 25, 2026 | 15 |
| Oct 24, 2026 | 15 |
| Oct 23, 2026 | 15 |
| Oct 22, 2026 | 15 |
| Oct 21, 2026 | 15 |
| Oct 20, 2026 | 15 |
| Oct 19, 2026 | 15 |
| Oct 18, 2026 | 15 |
| Oct 17, 2026 | 15 |
| Oct 16, 2026 | 15 |
| Oct 15, 2026 | 15 |
| Oct 14, 2026 | 15 |
| Oct 13, 2026 | 15 |
| Oct 12, 2026 | 15 |
| Oct 11, 2026 | 15 |
| Oct 10, 2026 | 15 |
| Oct 9, 2026 | 15 |
| Oct 8, 2026 | 15 |
| Oct 7, 2026 | 15 |
| Oct 6, 2026 | 13 |
| Oct 5, 2026 | 13 |
| Oct 4, 2026 | 13 |
| Oct 3, 2026 | 13 |
Map
Where VimpelCom'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.
| AMS-IX Amsterdam, Netherlands | 200G | Both | |
| BBIX Hong Kong Hong Kong, Hong Kong | 10G | PeeringDB | |
| BBIX Tokyo Tokyo, Japan | 20G | Both | |
| DE-CIX Frankfurt Frankfurt, Germany | 100G | Both Speed differs | |
| Equinix Hong Kong Hong Kong, Hong Kong | 10G | PeeringDB | |
| Equinix New York New York, United States | 10G | PeeringDB | |
| GNM-IX Amsterdam, Netherlands | 100G | Both IPv4 not in PeeringDBIPv6 not in PeeringDB | |
| HKIX Hong Kong, Hong Kong | 10G | Both | |
| JPNAP Tokyo Tokyo, Japan | 10G | PeeringDB | |
| LINX LON1 London, United Kingdom | 100G | Both | |
| Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden | 100G | Both | |
| 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 | 400G | Both |
These exchanges have a switch in a facility where VimpelCom lists itself in PeeringDB, but don't have VimpelCom 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.
| MSK-IX MoscowMoscow, Russia | 638 | |
| FogIXPAvers, Switzerland | 532 | |
| TPIX PLWarsaw, Poland | 480 | |
| KleyReXFrankfurt, Germany | 471 | |
| Frys-IXFryslân, Netherlands | 338 | |
| 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland | 283 | |
| Giganet IXNAmsterdam, Frankfurt am Main, Kharkiv, Kyiv, Lviv, Odesa, Warsaw, Zaporizhzhia, Zhytomyr, Ukraine | 268 | |
| INTERIXAmsterdam, Netherlands | 262 | |
| PITER-IX Saint-PetersburgSaint-Petersburg, Russia | 246 | |
| ERA-IX AmsterdamAmsterdam, Netherlands | 244 | |
| PITER-IX MoscowMoscow, Russia | 243 | |
| NIX.CZPrague, Czechia | 225 | |
| Peering.czPrague, Bratislava, Vienna, Frankfurt, Czechia | 207 | |
| LOCIX FRANKFURTFrankfurt am Main, Germany | 205 | |
| NetIXSofia, Bulgaria | 204 | |
| THINX WarsawWarsaw, Poland | 194 | |
| PITER-IX FrankfurtFrankfurt, Germany | 172 | |
| nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France | 160 | |
| InterLAN-IXBucharest, Romania | 149 | |
| Global-IXAmsterdam, Netherlands | 138 | |
| Eurasia Peering IXMoscow, Russia | 136 | |
| PITER-IX HelsinkiHelsinki, Finland | 127 | |
| BIXBudapest, Hungary | 122 | |
| MegaIX FrankfurtFrankfurt, Germany | 114 | |
| LSIXAmsterdam, The Hague, Rotterdam, Naaldwijk, Netherlands | 105 | |
| ERA-IX FrankfurtFrankfurt, Germany | 85 | |
| STHIX - StockholmStockholm, Sweden | 84 | |
| SONIX StockholmStockholm, Sweden | 81 | |
| Equinix FrankfurtFrankfurt, Germany | 78 | |
| BALT-IXVilnius, Lithuania | 77 | |
| FICIX 2 (Helsinki)Helsinki, Finland | 71 | |
| NIX.SKBratislava, Slovakia | 68 | |
| FogIXP FrankfurtFrankfurt, Germany | 67 | |
| W-IXMoscow, Russia | 66 | |
| 1-NL FREEAmsterdam, Netherlands | 60 | |
| SOLIX MTU1500Stockholm, Sweden | 58 | |
| CLOUD-IX MSKMoscow, Russia | 52 | |
| Equinix AmsterdamAmsterdam, Netherlands | 51 | |
| Giganet IXN FrankfurtFrankfurt, Germany | 50 | |
| RoNIXBucharest, Romania | 43 | |
| Hong Kong Global Internet ExchangeHong Kong, Hong Kong | 33 | |
| SFO-IXBarnaul, Novosibirsk, Russia | 30 | |
| Balcan-IXBucharest, Romania | 29 | |
| 1-DE FREEFrankfurt, Germany | 27 | |
| Netnod Helsinki BLUE -- MTU9KHelsinki, Finland | 21 | |
| Netnod Helsinki GREEN -- MTU9KHelsinki, Finland | 21 | |
| NL-ix 2Amsterdam, Netherlands | 19 | |
| SOLIX MTU4470Stockholm, Sweden | 18 | |
| Equinix HelsinkiHelsinki, Finland | 17 | |
| Equinix StockholmStockholm, Sweden | 17 | |
| MAINPORT Peer-ExchangeFrankfurt am Main, Germany | 14 | |
| KeFF-IXStockholm, Gothenburg, Malmö, Amsterdam, Sweden | 11 | |
| NIX.CZ FENIXPrague, Czechia | 8 | |
| City-IX FrankfurtFrankfurt, Germany | 7 | |
| EURASIA-IX.NETIstanbul, Türkiye | 6 | |
| Global Peer ExchangeWashington, United States | 6 | |
| FICIX 2 (Helsinki) IPv6 MTU 9000Helsinki, Finland | 5 |
Facilities (7)
The buildings VimpelCom lists in PeeringDB, and how many of the exchanges in each it's on.
| Equinix FR5 - Frankfurt, KleyerStrasseFrankfurt | 3 of 33 | |
| Equinix SK1 - Stockholm, BrommaStockholm | 5 of 14 | |
| Equinix AM1/AM2 - Amsterdam, LuttenbergwegAmsterdam | 2 of 13 | |
| Digita Helsinki Pasila Broadcasting TowerHelsinki | 1 of 11 | |
| Moscow M9Moscow | 1 of 9 | |
| Equinix HK1 - Hong KongTsuen Wan | 2 of 6 | |
| Moscow M10Moscow | 0 of 1 |