Observed topology

AS138244 HOSTZOP-AS-IN - HOSTZOP CLOUD SERVICES PRIVATE LIMITED

Unclassified APNIC Network Services

Upstreams 1 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS138244: 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
AS9498	BHARTI Airtel Ltd.	Mobile	IPv4	232

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS134904	Code Technology	Unclassified	IPv4	118
AS150024	Key Stones Cloud Tech Private Limited	Unclassified	IPv4	59
AS136375	Chl Technology	Unclassified	IPv4	58
AS154063	RF Solutions	Unclassified	IPv4	58
AS152485	Hosterdaddy Private Limited	Unclassified	IPv4	1

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS9498	BHARTI Airtel Ltd.	Mobile	IPv4	467
AS134904	Code Technology	Unclassified	IPv4	118
AS45117	Ishan's Network	Residential	IPv4	59
AS150024	Key Stones Cloud Tech Private Limited	Unclassified	IPv4	59
AS136375	Chl Technology	Unclassified	IPv4	58
AS154063	RF Solutions	Unclassified	IPv4	58
AS152485	Hosterdaddy Private Limited	Unclassified	IPv4	1

Provenance

Where this comes from

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