asn.dev

Observed topology

AS28891 CITTEL CJSC City Telecom

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28891: 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
AS8359MTS PJSCMobileIPv451
AS57304JSC "RetnNet"UnclassifiedIPv451
AS6939Hurricane Electric LLCTransitIPv424
AS29124Iskratelecom JSCResidentialIPv421
AS31133PJSC MegaFonMobileIPv421
AS24482SG.GSHostingIPv43
AS37721Virtual Technologies & SolutionsResidentialIPv43
AS49673Truenetwork LLCUnclassifiedIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS47808Freight Link OJSCUnclassifiedIPv422
AS197273PJSC UniproUnclassifiedIPv46

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS57304JSC "RetnNet"UnclassifiedIPv464
AS8359MTS PJSCMobileIPv452
AS29124Iskratelecom JSCResidentialIPv428
AS31133PJSC MegaFonMobileIPv426
AS6939Hurricane Electric LLCTransitIPv424
AS47808Freight Link OJSCUnclassifiedIPv422
AS197273PJSC UniproUnclassifiedIPv46
AS37721Virtual Technologies & SolutionsResidentialIPv44
AS49673Truenetwork LLCUnclassifiedIPv44
AS24482SG.GSHostingIPv43

Provenance

Where this comes from

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