Observed topology
AS28840 TATTELECOM-AS
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS28840: 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 | 10,569 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 5,055 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 2,849 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 | 1,398 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 518 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 88 |
| AS24482 | SG.GS | Hosting | IPv4 | 76 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 76 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 69 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 47 |
Transit
Downstream networks
Networks for which AS28840 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS49280 | Ruslan Saifullin | Unclassified | IPv4 | 62 |
| AS51027 | JSC Tatmedia | Unclassified | IPv4 | 62 |
| AS197873 | JSCB "ENERGOBANK" | Unclassified | IPv4 | 62 |
| AS48676 | LLC "Svyazenergo" | Unclassified | IPv4 | 49 |
| AS214066 | Tatspirtprom JSC | Unclassified | IPv4 | 42 |
| AS203509 | ANO VO Universitet Innopolis | Unclassified | IPv4 | 39 |
| AS50164 | PJSC TATNEFT N.A. V.D. SHASHIN | Unclassified | IPv4 | 27 |
| AS208547 | LLC "NPK "VOLGA-AVTOMATIKA"" | Unclassified | IPv4 | 10 |
Adjacency
Adjacent networks
Every AS seen directly next to AS28840 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 10,878 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 5,151 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 2,944 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 | 1,439 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 518 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 94 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 78 |
| AS24482 | SG.GS | Hosting | IPv4 | 77 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 73 |
| AS49280 | Ruslan Saifullin | Unclassified | IPv4 | 62 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.25M 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.