asn.dev

Observed topology

AS141536 INTERLOK-AS-IN - Interlock Communication

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS141536: 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
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv689
AS18229CtrlSHostingIPv4 IPv612

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS138297Netlink Websolution Pvt. Ltd.UnclassifiedIPv4240
AS135748Radiant Network Technologies Pvt LtdUnclassifiedIPv4122
AS153704GUJNET INFRALINK PRIVATE LIMITEDUnclassifiedIPv4120
AS154464OSPOT CONSULTINGUnclassifiedIPv477
AS140122Omnet Infratech Pvt LtdUnclassifiedIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv6426
AS18229CtrlSHostingIPv4 IPv6294
AS138297Netlink Websolution Pvt. Ltd.UnclassifiedIPv4240
AS135748Radiant Network Technologies Pvt LtdUnclassifiedIPv4122
AS153704GUJNET INFRALINK PRIVATE LIMITEDUnclassifiedIPv4120
AS154464OSPOT CONSULTINGUnclassifiedIPv477
AS140122Omnet Infratech Pvt LtdUnclassifiedIPv460

Provenance

Where this comes from

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