Observed topology

AS141492 SUNBEAM-AS-IN Amk Sunbeam Communication Private Limited

Unclassified ARIN

Upstreams 4 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 4

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS141492: 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
AS17762	Tata Teleservices Maharashtra Ltd	Unclassified	IPv4	77
AS18229	CtrlS	Hosting	IPv4	74
AS133720	Zess Networks Private Limited	Residential	IPv6	37
AS17665	ONEOTT INTERTAINMENT LIMITED	Residential	IPv4	32

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS149549	AVD INFOCOM PRIVATE LIMITED	Unclassified	IPv4	244

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS149549	AVD INFOCOM PRIVATE LIMITED	Unclassified	IPv4	244
AS18229	CtrlS	Hosting	IPv4	185
AS17762	Tata Teleservices Maharashtra Ltd	Unclassified	IPv4	162
AS17665	ONEOTT INTERTAINMENT LIMITED	Residential	IPv4	80
AS133720	Zess Networks Private Limited	Residential	IPv6	37

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.