asn.dev

Observed topology

AS137645 MSPL-AS - Macro Signal Pvt Ltd

Residential APNIC Cable/DSL/ISP

Upstreams 4 carry this network
Downstreams 3 this network carries
Adjacent (IPv4) 7
Adjacent (IPv6) 4
Upstream graph Who carries AS137645, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS137645 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS133296Web Werks India Pvt. Ltd.ResidentialIPv4354
AS18229CtrlSHostingIPv4348
AS24482SG.GSHostingIPv4 IPv613
AS35280F5 Networks SARLHostingIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS135268As Broadband Pvt LtdUnclassifiedIPv4 IPv6181
AS150584Badlapur Broabband Services Private LimitedUnclassifiedIPv433
AS138771Specific Net Pvt. Ltd.ResidentialIPv4 IPv612

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS133296Web Werks India Pvt. Ltd.ResidentialIPv4519
AS18229CtrlSHostingIPv4380
AS135268As Broadband Pvt LtdUnclassifiedIPv4 IPv6181
AS24482SG.GSHostingIPv4 IPv634
AS150584Badlapur Broabband Services Private LimitedUnclassifiedIPv433
AS138771Specific Net Pvt. Ltd.ResidentialIPv4 IPv616
AS5WFA Group LLCUnclassifiedIPv412
AS35280F5 Networks SARLHostingIPv61

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-08 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.