Runet connectivity

Definitions and area of investigation

This section presents data characterizing the connectivity of the Russian autonomous systems (AS). The affiliation of AS to the RF is determined by its registration data in the RIPE NCC, the city of registration of the AS is determined by the address of the organization-owner.

BGP-neighborhood is a relation of two autonomous systems, in which at least one BGP-session is established between them, in which at least one prefix (network route) is announced. In this case, we assume that there is a connection between these two autonomous systems. The BGP adjacency is determined from the AS-PATH attribute of the network route in the complete BGP routing table. A combined table of BGP routes collected from MSK-IX DNS Cloud routers, some telecom operators and from open sources (RIS projects, RouteViews), as well as from routing servers of traffic points MSK-IX, DATAIX, CLOUD-IX, W-IX, RED-IX, SIBIR-IX, SEA-IX, PITER-IX, CRIMEA-IX, BAIKAL-IX, RB-IX is used as a source of data on the state of connectivity between AS.

The data on three types of connectivity are given: general, intra-Russian and cross-border.

The general AS connectivity is the number of BGP neighbors with any other AS.

The intra-Russian connectivity of a separate Russian AS is the number of BGP neighbors with AS belonging to residents of the Russian Federation according to the RIPE NCC database. An indicator of intra-Russian connectivity is the number of BGP-neighborhoods with other Russian AS.

The cross-border connectivity of a separate Russian AS is the number of BGP neighborhoods with AS that are not owned by residents of the Russian Federation according to the RIPE NCC database. An indicator of cross-border connectivity is the number of BGP-neighborhoods with foreign AS.

Connectivity type:
Date:Today
Runet IPv4 AS,
Runet IPv6 AS,

The polar radius corresponds to the number of BGP neighbors of AS (on the reverse logarithmic scale), and the polar angle corresponds to the geographical longitude of the AS registration city (0 degrees - Kaliningrad, 359 degrees - Anadyr).

Geographical coordinates of the cities are determined using the geographical database MaxMind.

Stub AS is not displayed on circle charts.

The number of BGP neighborhoods characterizes the significance of this AS for the connectivity of the Runet.

All Runet IPv4 AS,
All Runet IPv6 AS,

There are several types of AS:

1) Relative to network routes:

  • Transit AS – is an autonomous system that announces at least one IP-prefix received from one BGP-neighbor to another BGP-neighbor.
Transit Runet IPv4 AS,
Transit Runet IPv6 AS,
  • End AS is an autonomous system that does not announces any IP prefix received from one BGP-neighbor to another BGP-neighbor.

2) By the number of BGP-neighbors:

  • Multihomed AS – is an autonomous system that has more than one BGP neighbor.
Multihomed Runet IPv4 AS,
Multihomed Runet IPv6 AS,
  • Stub AS - is an autonomous system that has exactly one BGP-neighbor.
Stub Runet IPv4 AS,
Amount of AS:
Stub Runet IPv6 AS,
Amount of AS:

The Runet core we define as the set of AS, with at least 100 BGP-neighbors for IPv4, and at least 40 BGP-neighbors for IPv6.

IPv4 Runet core,
IPv6 Runet core,

The AS list, in descending order of the number of connections:

The list of foreign AS, in descending order of the number of connections to russian AS: