asn.dev

Observed topology

AS58762 CANDOR-AS-IN Candor infosolution Pvt Ltd

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS58762: 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
AS45820Tata Teleservices ISP ASResidentialIPv4 IPv61,617
AS24482SG.GSHostingIPv4 IPv622
AS18229CtrlSHostingIPv4 IPv67

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS139538MOVEX DIGITAL TECHNOLOGY PRIVATE LIMITEDUnclassifiedIPv4 IPv6211
AS134946Indophone NetworksUnclassifiedIPv4177
AS153289GIGAZONE SOLUTION PRIVATE LIMITEDHostingIPv4 IPv668
AS132627FIBERMETRIC BROADBAND PRIVATE LIMITEDUnclassifiedIPv4 IPv63

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS45820Tata Teleservices ISP ASResidentialIPv4 IPv62,033
AS139538MOVEX DIGITAL TECHNOLOGY PRIVATE LIMITEDUnclassifiedIPv4 IPv6211
AS134946Indophone NetworksUnclassifiedIPv4177
AS153289GIGAZONE SOLUTION PRIVATE LIMITEDHostingIPv4 IPv668
AS18002AS Number for Interdomain RoutingUnclassifiedIPv636
AS24482SG.GSHostingIPv4 IPv629
AS18229CtrlSHostingIPv4 IPv67
AS132627FIBERMETRIC BROADBAND PRIVATE LIMITEDUnclassifiedIPv4 IPv63

Provenance

Where this comes from

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