ixreport

North-West branch of PJSC Megafon

AS20632

1Exchange
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
SelectivePeering policy
0Using the route servers
1To fix in PeeringDB
3Facilities in PeeringDB

Tools: Where can I peer with North-West branch of PJSC Megafon? · Where should North-West branch of PJSC Megafon peer next? · Compare North-West branch of PJSC Megafon with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in North-West branch of PJSC Megafon's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-11-19 12:40 UTC.

Make the changes on North-West branch of PJSC Megafon'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 North-West branch of PJSC Megafon's PeeringDB record. Add one entry per connection with these values.

  1. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

Exchanges over time

01Oct 26, 2026Nov 19, 20261
Show as a table
DateExchanges
Nov 19, 20261
Nov 18, 20261
Nov 17, 20261
Nov 16, 20261
Nov 15, 20261
Nov 14, 20261
Nov 13, 20261
Nov 12, 20261
Nov 11, 20261
Nov 10, 20261
Nov 9, 20261
Nov 8, 20261
Nov 7, 20261
Nov 6, 20261
Nov 5, 20261
Nov 4, 20261
Nov 3, 20261
Nov 2, 20261
Nov 1, 20261
Oct 31, 20261
Oct 30, 20261
Oct 29, 20261
Oct 28, 20261
Oct 27, 20261
Oct 26, 20261

Map

Where North-West branch of PJSC Megafon'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

Russia MSK-IX Moscow Moscow, Russia Website list only

Exchanges in its buildings that it isn't on (11)

These exchanges have a switch in a facility where North-West branch of PJSC Megafon lists itself in PeeringDB, but don't have North-West branch of PJSC Megafon 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.

Netherlands GNM-IXAmsterdam, Netherlands 741 Moscow M9; Bolshaya Morskaya 18
Russia PITER-IX Saint-PetersburgSaint-Petersburg, Russia 246 Moscow M9; Bolshaya Morskaya 18
Russia PITER-IX MoscowMoscow, Russia 243 Moscow M9; Bolshaya Morskaya 18
Netherlands Global-IXAmsterdam, Netherlands 138 Moscow M9; Bolshaya Morskaya 18
Russia Eurasia Peering IXMoscow, Russia 136 Moscow M9
Russia MSK-IX Saint-PetersburgSt.Petersburg, Russia 71 Bolshaya Morskaya 18; RETNNet OV DC
Russia W-IXMoscow, Russia 66 Moscow M9; Bolshaya Morskaya 18
Russia CLOUD-IX MSKMoscow, Russia 52 Moscow M9; Bolshaya Morskaya 18
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 Moscow M9
Russia CLOUD-IX SPBSt. Petersburg, Russia 25 Bolshaya Morskaya 18
Russia PIRIXSt.Petersburg, Russia 6 Bolshaya Morskaya 18; RETNNet OV DC
Facilities (3)

The buildings North-West branch of PJSC Megafon lists in PeeringDB, and how many of the exchanges in each it's on.

Russia Bolshaya Morskaya 18St. Petersburg 0 of 9
Russia Moscow M9Moscow 1 of 9
Russia RETNNet OV DCSt. Petersburg 0 of 2