asn.dev

Observed topology

AS63150 BAGE - BAGE CLOUD LLC

Hosting ARIN

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

Transit

Upstream networks

All 19

Networks observed carrying traffic for AS63150: 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
AS137409GSL Networks Pty LTDUnclassifiedIPv4 IPv6934
AS49304SAKURA LINK LIMITEDUnclassifiedIPv4 IPv6814
AS26042FiberState, LLCHostingIPv4 IPv6543
AS17433Hytron Network Services LimitedResidentialIPv4 IPv6519
AS9516SAKURA LINK LIMITEDUnclassifiedIPv4 IPv6515
AS30058FDCservers.netUnclassifiedIPv4 IPv6498
AS58212dataforest GmbHUnclassifiedIPv4 IPv6372
AS18450WebNX, Inc.HostingIPv4 IPv6268
AS53667FranTech SolutionsHostingIPv4 IPv6245
AS6939Hurricane Electric LLCTransitIPv4 IPv6198

All 19 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS152913BAGE CLOUD LLCUnclassifiedIPv459

Adjacency

Adjacent networks

All 20

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

ASNetworkTypeFamiliesPaths seen
AS137409GSL Networks Pty LTDUnclassifiedIPv4 IPv6934
AS49304SAKURA LINK LIMITEDUnclassifiedIPv4 IPv6814
AS9516SAKURA LINK LIMITEDUnclassifiedIPv4 IPv6561
AS26042FiberState, LLCHostingIPv4 IPv6543
AS17433Hytron Network Services LimitedResidentialIPv4 IPv6519
AS30058FDCservers.netUnclassifiedIPv4 IPv6498
AS58212dataforest GmbHUnclassifiedIPv4 IPv6372
AS18450WebNX, Inc.HostingIPv4 IPv6268
AS53667FranTech SolutionsHostingIPv4 IPv6245
AS6939Hurricane Electric LLCTransitIPv4 IPv6207

All 20 adjacent →

Provenance

Where this comes from

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