asn.dev

Observed topology

AS49791 AS-3HCLOUD Newserverlife LLC

Hosting DROP-listed space RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS49791: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv61,593
AS9198JSC KazakhtelecomUnclassifiedIPv4 IPv61,046
AS174Cogent Communications, LLCTransitIPv4 IPv6475
AS19151BroadbandONE, LLCHostingIPv4 IPv6391
AS28917Fiord Networks, UABUnclassifiedIPv4 IPv6144

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS214456ServerSP LLCHostingIPv4 IPv6475
AS401133TSIANA INC.HostingIPv4 IPv6138
AS401332TriplebitUnclassifiedIPv4 IPv6102
AS211305HOSTBITS SOLUCOES EM NUVEM LTDAUnclassifiedIPv466

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv62,219
AS9198JSC KazakhtelecomUnclassifiedIPv4 IPv61,046
AS174Cogent Communications, LLCTransitIPv4 IPv6608
AS214456ServerSP LLCHostingIPv4 IPv6475
AS19151BroadbandONE, LLCHostingIPv4 IPv6391
AS28917Fiord Networks, UABUnclassifiedIPv4 IPv6166
AS401133TSIANA INC.HostingIPv4 IPv6138
AS401332TriplebitUnclassifiedIPv4 IPv6102
AS211305HOSTBITS SOLUCOES EM NUVEM LTDAUnclassifiedIPv466

Provenance

Where this comes from

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