asn.dev

Observed topology

AS15146 CABLEBAHAMAS

Residential ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS15146: 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 IPv610,834
AS1299Arelion Sweden ABTransitIPv4 IPv62,046
AS23520Columbus Networks USA, Inc.ResidentialIPv4 IPv6729
AS3257GTT Communications Inc.TransitIPv4 IPv6395
AS24482SG.GSHostingIPv4 IPv6338

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS18635Secure Hosting Ltd.HostingIPv4512
AS19377Cloud Carib LimitedHostingIPv4 IPv6135
AS22357Secure Shores Data CenterUnclassifiedIPv4126
AS397914Commonwealth Bank LtdUnclassifiedIPv464
AS397972Baha MarUnclassifiedIPv463

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv611,542
AS1299Arelion Sweden ABTransitIPv4 IPv62,173
AS23520Columbus Networks USA, Inc.ResidentialIPv4 IPv6768
AS18635Secure Hosting Ltd.HostingIPv4512
AS3257GTT Communications Inc.TransitIPv4 IPv6421
AS24482SG.GSHostingIPv4 IPv6338
AS19377Cloud Carib LimitedHostingIPv4 IPv6135
AS22357Secure Shores Data CenterUnclassifiedIPv4126
AS397914Commonwealth Bank LtdUnclassifiedIPv464
AS397972Baha MarUnclassifiedIPv463

Provenance

Where this comes from

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