asn.dev

Observed topology

AS997 BSL-AS-AP - Beyotta Services LLP

Unclassified APNIC

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS997: 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
AS23961Misaka Network, Inc.UnclassifiedIPv4587
AS6939Hurricane Electric LLCTransitIPv4 IPv6176
AS35487Misaka Network, Inc.UnclassifiedIPv462
AS57695Misaka Network, Inc.UnclassifiedIPv452
AS136826PT TITIK TERANG MAKMURUnclassifiedIPv443
AS134196ANYUN INTERNET TECHNOLOGY (HK) CO.,LIMITEDUnclassifiedIPv441
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv615
AS24482SG.GSHostingIPv4 IPv615
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv615
AS55933Cloudie LimitedHostingIPv412

All 12 upstreams →

Transit

Downstream networks

inferred

Networks for which AS997 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 AS997 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS23961Misaka Network, Inc.UnclassifiedIPv4587
AS6939Hurricane Electric LLCTransitIPv4 IPv6176
AS35487Misaka Network, Inc.UnclassifiedIPv462
AS57695Misaka Network, Inc.UnclassifiedIPv452
AS136826PT TITIK TERANG MAKMURUnclassifiedIPv443
AS134196ANYUN INTERNET TECHNOLOGY (HK) CO.,LIMITEDUnclassifiedIPv441
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv615
AS24482SG.GSHostingIPv4 IPv615
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv615
AS55933Cloudie LimitedHostingIPv412

All 12 adjacent →

Provenance

Where this comes from

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