Observed topology
AS47626 ASTIMER Timer, LLC
Residential RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS47626: 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 |
|---|---|---|---|---|
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 290 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 278 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 163 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 126 |
| AS28917 | Fiord Networks, UAB | Unclassified | IPv4 | 109 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 25 |
| AS24482 | SG.GS | Hosting | IPv4 | 17 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 17 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 17 |
| AS56655 | Gigahost AS | Unclassified | IPv4 | 17 |
Transit
Downstream networks
Networks for which AS47626 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS45055 | Dontechsvyaz LLC | Unclassified | IPv4 | 440 |
| AS208720 | RegionInfoCom LLC | Unclassified | IPv4 | 65 |
| AS57766 | ENERGOINFORM Ltd | Unclassified | IPv4 | 62 |
| AS197185 | LLC T-Lan | Unclassified | IPv4 | 62 |
| AS58306 | PE Krylov Dmitriy Viktorovich | Unclassified | IPv4 | 61 |
| AS57534 | PE Ahmedov Alil Aliomarovich | Unclassified | IPv4 | 48 |
| AS56374 | Federal State Budgetary Educational Institution of Higher Education "M.I.Platov South-Russian State Polytechnic University (NPI)" | Unclassified | IPv4 | 34 |
| AS57531 | RegionInfoCom LLC | Unclassified | IPv4 | 34 |
| AS209393 | OOO Dontel | Unclassified | IPv4 | 34 |
| AS58096 | Viter Evgeniy Vasilevich | Residential | IPv4 | 31 |
Adjacency
Adjacent networks
Every AS seen directly next to AS47626 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 566 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 466 |
| AS45055 | Dontechsvyaz LLC | Unclassified | IPv4 | 440 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 327 |
| AS28917 | Fiord Networks, UAB | Unclassified | IPv4 | 252 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 214 |
| AS57766 | ENERGOINFORM Ltd | Unclassified | IPv4 | 65 |
| AS208720 | RegionInfoCom LLC | Unclassified | IPv4 | 65 |
| AS197185 | LLC T-Lan | Unclassified | IPv4 | 62 |
| AS58306 | PE Krylov Dmitriy Viktorovich | Unclassified | IPv4 | 61 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-09 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.03M 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.