Observed topology
AS8242 INTELWAY-AS
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS8242: 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 |
|---|---|---|---|---|
| AS28968 | JSC "Evrasia Telecom Ru" | Unclassified | IPv4 | 481 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 | 177 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 16 |
| AS24482 | SG.GS | Hosting | IPv4 | 6 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 6 |
| AS25091 | IP-Max SA | Unclassified | IPv4 | 5 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 2 |
| AS8447 | A1 Telekom Austria AG | Residential | IPv4 | 1 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 1 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS8242 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS61410 | KSB Stealth LLC | Unclassified | IPv4 | 63 |
Adjacency
Adjacent networks
Every AS seen directly next to AS8242 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS28968 | JSC "Evrasia Telecom Ru" | Unclassified | IPv4 | 528 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 | 192 |
| AS61410 | KSB Stealth LLC | Unclassified | IPv4 | 63 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 17 |
| AS24482 | SG.GS | Hosting | IPv4 | 6 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 6 |
| AS25091 | IP-Max SA | Unclassified | IPv4 | 5 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 2 |
| AS8447 | A1 Telekom Austria AG | Residential | IPv4 | 1 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 1 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-18 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.