asn.dev

Observed topology

AS28840 TATTELECOM-AS PJSC "TATTELECOM"

Unclassified RIPE

Upstreams 15 carry this network
Downstreams 8 this network carries
Adjacent (IPv4) 23
Adjacent (IPv6) 0
Upstream graph Who carries AS28840, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS28840 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 15

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.

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv410,331
AS31133PJSC MegaFonMobileIPv45,768
AS57304JSC "RetnNet"UnclassifiedIPv43,251
AS9002RETN LimitedUnclassifiedIPv4349
AS6939Hurricane Electric LLCTransitIPv4294
AS50673Serverius Holding B.V.UnclassifiedIPv4107
AS24482SG.GSHostingIPv486
AS49673Truenetwork LLCUnclassifiedIPv486
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv479
AS37721Virtual Technologies & SolutionsResidentialIPv457

All 15 upstreams →

Transit

Downstream networks

inferred

Networks for which AS28840 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS49280Ruslan SaifullinUnclassifiedIPv461
AS51027JSC TatmediaUnclassifiedIPv461
AS197873JSCB "ENERGOBANK"UnclassifiedIPv461
AS48676LLC "Svyazenergo"UnclassifiedIPv437
AS214066Tatspirtprom JSCUnclassifiedIPv437
AS203509ANO VO Universitet InnopolisUnclassifiedIPv433
AS208547LLC "NPK "VOLGA-AVTOMATIKA""UnclassifiedIPv46
AS50164PJSC TATNEFT N.A. V.D. SHASHINUnclassifiedIPv42

Adjacency

Adjacent networks

All 23

Every AS seen directly next to AS28840 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv410,642
AS31133PJSC MegaFonMobileIPv45,860
AS57304JSC "RetnNet"UnclassifiedIPv43,302
AS9002RETN LimitedUnclassifiedIPv4349
AS6939Hurricane Electric LLCTransitIPv4294
AS50673Serverius Holding B.V.UnclassifiedIPv4113
AS49673Truenetwork LLCUnclassifiedIPv488
AS24482SG.GSHostingIPv487
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv483
AS49280Ruslan SaifullinUnclassifiedIPv461

All 23 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M 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.