Observed topology
AS48327 RAY-AS
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS48327: 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 |
|---|---|---|---|---|
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 181 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 120 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 48 |
| AS48858 | JSC "ER-Telecom Holding" | Unclassified | IPv4 | 28 |
| AS13094 | JSC "ER-Telecom Holding" | Unclassified | IPv6 | 23 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 7 |
| AS56655 | Gigahost AS | Unclassified | IPv4 | 7 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 7 |
| AS24482 | SG.GS | Hosting | IPv4 | 6 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 6 |
Transit
Downstream networks
Networks for which AS48327 was observed as the last hop before the origin, meaning it appears to provide them transit.
Adjacency
Adjacent networks
Every AS seen directly next to AS48327 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS51583 | Ray-Svyaz Ltd. | Unclassified | IPv4 | 960 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 792 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 345 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 137 |
| AS39061 | Ray-Svyaz Ltd. | Unclassified | IPv4 | 59 |
| AS48858 | JSC "ER-Telecom Holding" | Unclassified | IPv4 | 35 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 24 |
| AS56655 | Gigahost AS | Unclassified | IPv4 | 24 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 24 |
| AS13094 | JSC "ER-Telecom Holding" | Unclassified | IPv6 | 23 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-19 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.