asn.dev

Observed topology

AS142485 SUNDARAMBROADBAND-AS SUNDARAM BROADBAND PRIVATE LIMITED

Unclassified APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS142485: 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
AS18229CtrlSHostingIPv4 IPv6267
AS9583Sify LimitedUnclassifiedIPv4 IPv6136

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS147255Tj Brodband Network Pvt LtdUnclassifiedIPv4244
AS152498UNIQUE BROADBAND SERVICE PRIVATE LIMITEDUnclassifiedIPv4 IPv6214
AS154846CALCUTTA TELEVISION NETWORK PVT LTDUnclassifiedIPv44
AS142451AKD NETWORK PVT LTDResidentialIPv42
AS149268Roarnet Broadband Pvt LtdUnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS18229CtrlSHostingIPv4 IPv6633
AS147255Tj Brodband Network Pvt LtdUnclassifiedIPv4244
AS9583Sify LimitedUnclassifiedIPv4 IPv6236
AS152498UNIQUE BROADBAND SERVICE PRIVATE LIMITEDUnclassifiedIPv4 IPv6214
AS154846CALCUTTA TELEVISION NETWORK PVT LTDUnclassifiedIPv44
AS142451AKD NETWORK PVT LTDResidentialIPv42
AS149268Roarnet Broadband Pvt LtdUnclassifiedIPv42

Provenance

Where this comes from

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