asn.dev

Observed topology

AS4785 XTOM-AS-JP xTom

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS4785: 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
AS2497Internet Initiative Japan Inc.UnclassifiedIPv41,409
AS6939Hurricane Electric LLCTransitIPv4 IPv61,165
AS17676SoftBank Corp.MobileIPv4873

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS25820IT7 Networks IncHostingIPv41,318
AS149440Evoxt Sdn. Bhd.UnclassifiedIPv4 IPv6836
AS400464VMISS Inc.UnclassifiedIPv4464
AS23959Owl LimitedUnclassifiedIPv4 IPv6154
AS206216Advin Services LLCHostingIPv4 IPv6125
AS197767ZgoShop, Inc.UnclassifiedIPv4 IPv695
AS24013SB Professional ServicesHostingIPv4 IPv618
AS8888xTom Pty LtdHostingIPv414

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS17676SoftBank Corp.MobileIPv42,774
AS2497Internet Initiative Japan Inc.UnclassifiedIPv4 IPv62,028
AS6939Hurricane Electric LLCTransitIPv4 IPv61,743
AS25820IT7 Networks IncHostingIPv41,318
AS149440Evoxt Sdn. Bhd.UnclassifiedIPv4 IPv6836
AS400464VMISS Inc.UnclassifiedIPv4464
AS23959Owl LimitedUnclassifiedIPv4 IPv6154
AS206216Advin Services LLCHostingIPv4 IPv6125
AS197767ZgoShop, Inc.UnclassifiedIPv4 IPv695
AS23748Cat Networks K.K.ResidentialIPv675

All 13 adjacent →

Provenance

Where this comes from

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