Observed topology
AS31133 MF-MGSM-AS PJSC MegaFon
Mobile RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS31133: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 7,895 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 4,544 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 3,309 |
| AS23764 | CTGNet | Unclassified | IPv4 IPv6 | 1,996 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 | 1,374 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 550 |
| AS42708 | Glesys Sweden AB | Unclassified | IPv4 IPv6 | 548 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 548 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 546 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 546 |
Transit
Downstream networks
Networks for which AS31133 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12714 | PJSC MegaFon | Unclassified | IPv4 IPv6 | 18,461 |
| AS31163 | PJSC MegaFon | Unclassified | IPv4 IPv6 | 15,218 |
| AS29648 | PJSC MegaFon | Unclassified | IPv4 IPv6 | 7,817 |
| AS24955 | JSC "Ufanet" | Residential | IPv4 IPv6 | 6,438 |
| AS28840 | PJSC "TATTELECOM" | Unclassified | IPv4 | 5,738 |
| AS31195 | PJSC MegaFon | Unclassified | IPv4 IPv6 | 5,111 |
| AS25159 | PJSC MegaFon | Unclassified | IPv4 IPv6 | 4,764 |
| AS20632 | PJSC MegaFon | Unclassified | IPv4 IPv6 | 3,843 |
| AS31208 | PJSC MegaFon | Unclassified | IPv4 IPv6 | 3,154 |
| AS50928 | PJSC MegaFon | Unclassified | IPv4 IPv6 | 2,629 |
Adjacency
Adjacent networks
Every AS seen directly next to AS31133 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 57,156 |
| AS9198 | JSC Kazakhtelecom | Unclassified | IPv4 | 44,384 |
| AS23764 | CTGNet | Unclassified | IPv4 IPv6 | 32,064 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 30,882 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 27,626 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 23,212 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 | 19,253 |
| AS12714 | PJSC MegaFon | Unclassified | IPv4 IPv6 | 19,009 |
| AS31163 | PJSC MegaFon | Unclassified | IPv4 IPv6 | 15,635 |
| AS12552 | GlobalConnect AB | Unclassified | IPv4 | 11,056 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.
Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.
Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.