asn.dev

Observed topology

AS44185 BONET UPSTREAM

Hosting RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS44185: 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 ABTransitIPv4 IPv6106
AS6939Hurricane Electric LLCTransitIPv4 IPv643
AS174Cogent Communications, LLCTransitIPv439
AS31230Slovak University of Technology in BratislavaUnclassifiedIPv4 IPv66
AS24482SG.GSHostingIPv4 IPv64
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv64
AS8218Zayo Infrastructure France SAUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS196944bonet.systems, s. r. o.UnclassifiedIPv4 IPv689
AS48304Digmia s.r.o.UnclassifiedIPv4 IPv67

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6151
AS196944bonet.systems, s. r. o.UnclassifiedIPv4 IPv689
AS6939Hurricane Electric LLCTransitIPv4 IPv665
AS174Cogent Communications, LLCTransitIPv455
AS24482SG.GSHostingIPv4 IPv610
AS31230Slovak University of Technology in BratislavaUnclassifiedIPv4 IPv610
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv69
AS48304Digmia s.r.o.UnclassifiedIPv4 IPv67
AS6855Slovak Telekom, a.s.MobileIPv43
AS8218Zayo Infrastructure France SAUnclassifiedIPv62

Provenance

Where this comes from

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