asn.dev

Observed topology

AS45763 OPTICOMMCOPTYLTD-AS-AP - Opticomm Co Pty Ltd

Residential APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS45763: 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
AS4764Aussie BroadbandResidentialIPv4 IPv62,900
AS1221Telstra LimitedMobileIPv4 IPv62,888
AS6939Hurricane Electric LLCTransitIPv41,176
AS24482SG.GSHostingIPv4 IPv6127
AS64073Vetta GroupUnclassifiedIPv4 IPv6127
AS4608Asia Pacific Network Information CentreUnclassifiedIPv4126

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS45594Opticomm Pty LtdUnclassifiedIPv4986

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS4764Aussie BroadbandResidentialIPv4 IPv63,494
AS1221Telstra LimitedMobileIPv4 IPv63,076
AS6939Hurricane Electric LLCTransitIPv41,329
AS45594Opticomm Pty LtdUnclassifiedIPv4986
AS24482SG.GSHostingIPv4 IPv6144
AS64073Vetta GroupUnclassifiedIPv4 IPv6144
AS4608Asia Pacific Network Information CentreUnclassifiedIPv4143

Provenance

Where this comes from

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