asn.dev

Observed topology

AS7361 DATAZONE

Unclassified ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS7361: 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
AS40676Psychz NetworksHostingIPv41,176
AS152179GLOBAL COMMUNICATION NETWORK LIMITEDResidentialIPv41,011
AS7473Singapore Telecommunications LtdUnclassifiedIPv4689
AS21859Zenlayer IncHostingIPv4291
AS142064VergeTelUnclassifiedIPv4240
AS25369Hydra Communications LtdHostingIPv4237
AS401450Pluxcon Network USA LLCUnclassifiedIPv4120
AS146943Tier 4 Cloud ServicesHostingIPv460
AS20473The Constant Company, LLCHostingIPv459
AS214483FiberPower LLCUnclassifiedIPv458

Transit

Downstream networks

inferred

Networks for which AS7361 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

observed

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

ASNetworkTypeFamiliesPaths seen
AS40676Psychz NetworksHostingIPv41,176
AS152179GLOBAL COMMUNICATION NETWORK LIMITEDResidentialIPv41,011
AS7473Singapore Telecommunications LtdUnclassifiedIPv4689
AS21859Zenlayer IncHostingIPv4291
AS142064VergeTelUnclassifiedIPv4240
AS25369Hydra Communications LtdHostingIPv4237
AS401450Pluxcon Network USA LLCUnclassifiedIPv4120
AS146943Tier 4 Cloud ServicesHostingIPv460
AS20473The Constant Company, LLCHostingIPv459
AS214483FiberPower LLCUnclassifiedIPv458

Provenance

Where this comes from

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