asn.dev

Observed topology

AS44927 Telecom-MPK LLC Telecom MPK

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS44927: 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
AS1299Arelion Sweden ABTransitIPv4170
AS31500Global Network Management IncUnclassifiedIPv4147
AS8641LLC "Nauka-Svyaz"UnclassifiedIPv4114
AS6939Hurricane Electric LLCTransitIPv490
AS29076Citytelecom LLCHostingIPv451
AS24482SG.GSHostingIPv410
AS37721Virtual Technologies & SolutionsResidentialIPv410
AS49673Truenetwork LLCUnclassifiedIPv410
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv410

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS209950GIGAVIDER LLCUnclassifiedIPv453

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4186
AS31500Global Network Management IncUnclassifiedIPv4160
AS8641LLC "Nauka-Svyaz"UnclassifiedIPv4122
AS6939Hurricane Electric LLCTransitIPv495
AS29076Citytelecom LLCHostingIPv457
AS209950GIGAVIDER LLCUnclassifiedIPv453
AS24482SG.GSHostingIPv411
AS37721Virtual Technologies & SolutionsResidentialIPv411
AS49673Truenetwork LLCUnclassifiedIPv411
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv411

All 11 adjacent →

Provenance

Where this comes from

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