Observed topology
AS9123 TimeWeb-AS JSC "TIMEWEB"
Hosting ARIN NSP
Transit
Upstream networks
Networks observed carrying traffic for AS9123: 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 | 24,815 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 11,037 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 7,369 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 | 3,423 |
| AS50509 | Transroute Telecom LTD | Unclassified | IPv4 | 1,972 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 1,636 |
| AS59692 | IQWeb FZ-LLC | Unclassified | IPv4 | 1,426 |
| AS8359 | MTS PJSC | Mobile | IPv4 IPv6 | 945 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 939 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 IPv6 | 930 |
Transit
Downstream networks
Networks for which AS9123 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS210976 | Timeweb, LLP | Unclassified | IPv4 | 21,140 |
| AS205489 | CODE ASSET LTD | Hosting | IPv4 | 4,215 |
| AS214927 | PSB HOSTING LTD | Unclassified | IPv4 IPv6 | 310 |
| AS51789 | JSC "TIMEWEB" | Unclassified | IPv4 | 183 |
| AS62241 | Forest Net LTD | Unclassified | IPv4 IPv6 | 183 |
| AS216068 | Biapi LLC | Unclassified | IPv4 | 183 |
| AS199304 | Mikaia Iraklii Guramovich | Unclassified | IPv4 | 122 |
| AS204427 | Timeweb, LLP | Unclassified | IPv4 IPv6 | 77 |
| AS207461 | HOSTING INDUSTRY LIMITED | Unclassified | IPv4 | 69 |
| AS197139 | T-Man Software LLC | Unclassified | IPv4 | 59 |
Adjacency
Adjacent networks
Every AS seen directly next to AS9123 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 27,030 |
| AS210976 | Timeweb, LLP | Unclassified | IPv4 | 21,140 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 18,182 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 15,391 |
| AS205489 | CODE ASSET LTD | Hosting | IPv4 | 4,215 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 | 3,755 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 2,939 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 2,616 |
| AS50509 | Transroute Telecom LTD | Unclassified | IPv4 | 2,276 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 1,806 |
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.