Observed topology
AS51904 UTEX-AS
Residential RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS51904: 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 |
|---|---|---|---|---|
| AS8641 | LLC "Nauka-Svyaz" | Unclassified | IPv4 | 84 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 | 18 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 | 14 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 2 |
| AS24482 | SG.GS | Hosting | IPv4 | 2 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 2 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 2 |
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv4 | 2 |
Transit
Downstream networks
Networks for which AS51904 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS51538 | Lavrentyev Aleksandr Arkadievich | Unclassified | IPv4 | 63 |
Adjacency
Adjacent networks
Every AS seen directly next to AS51904 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS8641 | LLC "Nauka-Svyaz" | Unclassified | IPv4 | 159 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 | 88 |
| AS51538 | Lavrentyev Aleksandr Arkadievich | Unclassified | IPv4 | 63 |
| AS57724 | DDOS-GUARD LTD | Unclassified | IPv4 | 38 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 | 27 |
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv4 | 8 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 4 |
| AS24482 | SG.GS | Hosting | IPv4 | 3 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 3 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 3 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-25 12: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.