asn.dev

Observed topology

AS46829 LAMHOSTING - Lamhosting LLC

Unclassified ARIN

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS46829: 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
AS143151GSERVERS, LLCHostingIPv4 IPv6140
AS216211CYBERVERSE LLCHostingIPv4 IPv6115
AS151338POLONETWORK LIMITEDResidentialIPv4 IPv695
AS18041Taiwan Digital Streaming Co.HostingIPv459
AS6939Hurricane Electric LLCTransitIPv4 IPv647
AS214454PoloNetwork LimitedUnclassifiedIPv446
AS40792CYBERVERSEUnclassifiedIPv4 IPv631
AS134823Sky Digital Co., Ltd.ResidentialIPv45
AS51847Nearoute LimitedHostingIPv43
AS24482SG.GSHostingIPv4 IPv62

All 12 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS143151GSERVERS, LLCHostingIPv4 IPv6140
AS216211CYBERVERSE LLCHostingIPv4 IPv6115
AS151338POLONETWORK LIMITEDResidentialIPv4 IPv695
AS18041Taiwan Digital Streaming Co.HostingIPv459
AS6939Hurricane Electric LLCTransitIPv4 IPv647
AS214454PoloNetwork LimitedUnclassifiedIPv446
AS40792CYBERVERSEUnclassifiedIPv4 IPv631
AS134823Sky Digital Co., Ltd.ResidentialIPv45
AS51847Nearoute LimitedHostingIPv43
AS24482SG.GSHostingIPv4 IPv62

All 12 adjacent →

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.