Observed topology

AS136956 ANATPL-AS-AP Assistive Networks and technologies Pvt Ltd

Residential APNIC Cable/DSL/ISP

Upstreams 4 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 1

Upstream graph Who carries AS136956, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS136956 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS136956: 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.

AS	Network	Type	Families	Paths seen
AS133296	Web Werks India Pvt. Ltd.	Residential	IPv4	118
AS9498	BHARTI Airtel Ltd.	Mobile	IPv4	59
AS35280	F5 Networks SARL	Hosting	IPv4	8
AS17665	ONEOTT INTERTAINMENT LIMITED	Residential	IPv6	1

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS146992	SAS COMMUNICATIONS	Unclassified	IPv4	59

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS133296	Web Werks India Pvt. Ltd.	Residential	IPv4	118
AS9498	BHARTI Airtel Ltd.	Mobile	IPv4	59
AS133593	VIZAG BROADCASTING COMPANY PVT. LTD	Unclassified	IPv4	59
AS146992	SAS COMMUNICATIONS	Unclassified	IPv4	59
AS35280	F5 Networks SARL	Hosting	IPv4	8
AS17665	ONEOTT INTERTAINMENT LIMITED	Residential	IPv6	1

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.