Observed topology

AS153756 IRINN-DBYTE-AS-IN - DBYTE FACILITY NETWORK PRIVATE LIMITED

Unclassified APNIC

Upstreams 2 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS153756: 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 IPv6	150
AS55410	Vodafone Idea Ltd	Mobile	IPv4	4

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS136642	Aerocast Networks Private Limited	Unclassified	IPv4	299
AS135834	Multicraft Digital Technologies Private Limited	Residential	IPv4	61
AS147233	Aaacloud Telephony Pvt Ltd	Unclassified	IPv4	1

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS136642	Aerocast Networks Private Limited	Unclassified	IPv4	657
AS55410	Vodafone Idea Ltd	Mobile	IPv4	486
AS9498	BHARTI Airtel Ltd.	Mobile	IPv4 IPv6	209
AS133982	Excitel Broadband Private Limited	Residential	IPv4	177
AS135834	Multicraft Digital Technologies Private Limited	Residential	IPv4	61
AS24482	SG.GS	Hosting	IPv4	1
AS147233	Aaacloud Telephony Pvt Ltd	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.