Observed topology

AS150022 METAWAVES-AS-IN - METAWAVES PVT LTD

Unclassified APNIC

Upstreams 1 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS150022: 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
AS45117	Ishan's Network	Residential	IPv4 IPv6	151

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS150051	Skynet Broadband	Unclassified	IPv4	120
AS141296	Daman I Net	Unclassified	IPv4	119
AS137152	Ap Netcom Services	Unclassified	IPv4	81
AS149255	Bhavya Net	Unclassified	IPv4	59

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS45117	Ishan's Network	Residential	IPv4 IPv6	530
AS150051	Skynet Broadband	Unclassified	IPv4	120
AS141296	Daman I Net	Unclassified	IPv4	119
AS137152	Ap Netcom Services	Unclassified	IPv4	81
AS149255	Bhavya Net	Unclassified	IPv4	59

Provenance

Where this comes from

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