Observed topology
AS200044 stackgroup Stack Group, LLC
Unclassified RIPE Content
Transit
Upstream networks
Networks observed carrying traffic for AS200044: 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 |
|---|---|---|---|---|
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 485 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 388 |
| AS43298 | Storm Networks LLC | Unclassified | IPv4 | 59 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 21 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 16 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 14 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 14 |
Transit
Downstream networks
Networks for which AS200044 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS16083 | StackNet Service, LLC | Unclassified | IPv4 IPv6 | 283 |
| AS199582 | LLC Specialized Developer A101 | Unclassified | IPv4 | 175 |
| AS59513 | SevenTech LLC | Unclassified | IPv4 | 124 |
| AS25530 | SFT Company LLC | Unclassified | IPv4 | 120 |
| AS56671 | MEDIS LLC | Unclassified | IPv4 | 62 |
| AS210726 | ADV Launchpad Limited Liability Company | Unclassified | IPv4 | 62 |
| AS57671 | JSC Oil Processing Company | Unclassified | IPv4 | 58 |
| AS43009 | Infobip Limited | Unclassified | IPv4 IPv6 | 57 |
| AS211078 | JSC "Online Reservation System" | Unclassified | IPv4 | 33 |
| AS197808 | Technical Services Company Ltd | Unclassified | IPv4 | 28 |
Adjacency
Adjacent networks
Every AS seen directly next to AS200044 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 951 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 833 |
| AS16083 | StackNet Service, LLC | Unclassified | IPv4 IPv6 | 283 |
| AS199582 | LLC Specialized Developer A101 | Unclassified | IPv4 | 175 |
| AS59513 | SevenTech LLC | Unclassified | IPv4 | 124 |
| AS25530 | SFT Company LLC | Unclassified | IPv4 | 120 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 71 |
| AS56671 | MEDIS LLC | Unclassified | IPv4 | 62 |
| AS210726 | ADV Launchpad Limited Liability Company | Unclassified | IPv4 | 62 |
| AS43298 | Storm Networks LLC | Unclassified | IPv4 | 59 |
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.