of the Internet infrastructure
Autonomous systems Autonomous system
List of Russian aut-num. Data sources are RIR databases.
×
Check IRR announcements (RIPE DB)
Connectivity graph
- researched
- traffic exchange points
- world's largest operators
- transit AS
Edge prefixes
The RouteViews and RIS projects are used as data sources to build a connectivity graph of a specific autonomous system.
These data sources are used for building routes to the largest AS operators (part of the graph to the right of the AS under study).
The routing information from route servers of traffic exchange points (IXP)
MSK-IX,
DATAIX,
PITER-IX,
EurasiaPeering-IX,
W-IX,
RED-IX,
SIBIR-IX,
SEA-IX,
CRIMEA-IX,
M-IX,
BAIKAL-IX,
RB-IX,
ULN-IX,
SFO-IX,
TSK-IX,
YAR-IX
is used to build routes to traffic exchange points (part of the graph to the left of the AS under study).
World's largest operators
| as-name | as-num |
|---|---|
| Cogent | 174 |
| AT&T | 7018 |
| GTT | 3257 |
| Level3 | 3356 |
| NTT | 2914 |
| TATA | 6453 |
| Telecom Italy | 6762 |
| Telia | 1299 |
| Vodafone | 1273 |
The graph vertices are autonomous systems, the numbers of which are indicated near each vertex. When you hover the cursor on any vertex of the graph, information about the owner of this autonomous system is displayed. Each vertex of the graph is clickable. When pressed, you can get information about the selected AS.
Each edge of the graph reflects the BGP neighborhood defined by the AS-PATH attribute. The straight edge between the AS and the AS of the IXP router server, means a direct link (Layer2) between the AS and IXP being examined. If the connection to the IXP consists of several edges via transit AS, then the direct link (Layer2) is absent and the prefixes of the AS under investigation are delivered to IXP via the intermediate routers (Layer3) of other ASs that can affect the availability of the prefixes of the AS under investigation. There might be situations when transit routers could remove their AS from AS-PATH, then this situation treated as direct connection to IXP (Layer 2) When you click on a graph edge in a separate window, prefixes are displayed, which AS-PATHs were used to build this edge. Сlicking on a graph edge shows in a separate window the prefixes, whose AS-PATHs were used to build this edge. Сlicking on the circle corresponding to the specific IXP, the graph "Chamomile" is drawn on a separate page.
Each edge of the graph reflects the BGP neighborhood defined by the AS-PATH attribute. The straight edge between the AS and the AS of the IXP router server, means a direct link (Layer2) between the AS and IXP being examined. If the connection to the IXP consists of several edges via transit AS, then the direct link (Layer2) is absent and the prefixes of the AS under investigation are delivered to IXP via the intermediate routers (Layer3) of other ASs that can affect the availability of the prefixes of the AS under investigation. There might be situations when transit routers could remove their AS from AS-PATH, then this situation treated as direct connection to IXP (Layer 2) When you click on a graph edge in a separate window, prefixes are displayed, which AS-PATHs were used to build this edge. Сlicking on a graph edge shows in a separate window the prefixes, whose AS-PATHs were used to build this edge. Сlicking on the circle corresponding to the specific IXP, the graph "Chamomile" is drawn on a separate page.
BGP-neighbors on exchange points
The "Chamomile" graph is built on the basis of the analysis of BGP communities provided by the IXP participants to the advertised prefixes within the BGP session with the IXP router server. It shows no more than 10 AS, with which the AS under investigation exchanges the greatest number of prefixes (by the sum in both directions) on IXP.
The edges of this graph are references, when you click on the link, the connectivity graph of the AS with the selected BGP-neighbor explores.
Route objects
Route6 objects
Number of services in Russian domain zones located at IP-addresses announced by
Number of unique domain names in Russian zones (ru, su, рф) with located services