asn.dev

Observed topology

AS48078 DAGOMYS-AS

Unclassified RIPE

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS48078: 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 RostelecomResidentialIPv4 IPv6797
AS31500Global Network Management IncUnclassifiedIPv4206
AS8359MTS PJSCMobileIPv4 IPv630
AS50673Serverius Holding B.V.UnclassifiedIPv4 IPv619
AS24482SG.GSHostingIPv4 IPv618
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4 IPv618
AS37721Virtual Technologies & SolutionsResidentialIPv417
AS49673Truenetwork LLCUnclassifiedIPv417
AS50629LWLcom GmbHUnclassifiedIPv416
AS6939Hurricane Electric LLCTransitIPv48

All 13 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS57629LLC IVI.RUHostingIPv633

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4 IPv6797
AS31500Global Network Management IncUnclassifiedIPv4206
AS8359MTS PJSCMobileIPv4 IPv652
AS57629LLC IVI.RUHostingIPv633
AS24482SG.GSHostingIPv4 IPv619
AS50673Serverius Holding B.V.UnclassifiedIPv4 IPv619
AS6939Hurricane Electric LLCTransitIPv4 IPv618
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4 IPv618
AS37721Virtual Technologies & SolutionsResidentialIPv417
AS49673Truenetwork LLCUnclassifiedIPv417

All 14 adjacent →

Provenance

Where this comes from

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