Observed topology
AS44267 ENPLUS-TELECOM EN+ TELECOM LLC
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS44267: 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 |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 328 |
| AS8359 | MTS PJSC | Mobile | IPv4 IPv6 | 225 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 165 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 55 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 26 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 IPv6 | 14 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 13 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 13 |
| AS1299 | Arelion Sweden AB | Transit | IPv6 | 3 |
| AS24482 | SG.GS | Hosting | IPv6 | 1 |
Transit
Downstream networks
Networks for which AS44267 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS35608 | R-LINE 1 LLC | Unclassified | IPv4 IPv6 | 397 |
| AS56535 | Alpari Ltd. | Unclassified | IPv4 | 314 |
| AS202011 | EN+ TELECOM LLC | Unclassified | IPv4 | 186 |
| AS43594 | Svyaz LLC | Unclassified | IPv4 IPv6 | 180 |
| AS51428 | IRONNET Ltd. | Unclassified | IPv4 | 124 |
| AS50187 | BaikalWestCom Ltd | Unclassified | IPv4 IPv6 | 98 |
| AS214091 | LLC "Nord.Com" | Unclassified | IPv4 | 85 |
| AS43274 | Teleradiocompany Teleos-1 Ltd | Unclassified | IPv4 | 69 |
| AS199110 | R-18 Ltd. | Unclassified | IPv4 | 56 |
| AS60452 | En+ Hydro LLC | Unclassified | IPv4 | 42 |
Adjacency
Adjacent networks
Every AS seen directly next to AS44267 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 936 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 763 |
| AS35608 | R-LINE 1 LLC | Unclassified | IPv4 IPv6 | 397 |
| AS8359 | MTS PJSC | Mobile | IPv4 IPv6 | 375 |
| AS56535 | Alpari Ltd. | Unclassified | IPv4 | 314 |
| AS202011 | EN+ TELECOM LLC | Unclassified | IPv4 | 186 |
| AS43594 | Svyaz LLC | Unclassified | IPv4 IPv6 | 180 |
| AS50187 | BaikalWestCom Ltd | Unclassified | IPv4 IPv6 | 130 |
| AS51428 | IRONNET Ltd. | Unclassified | IPv4 | 124 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 119 |
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.