asn.dev

Observed topology

AS141317 NEHAINFO-AS-IN - Neha Infonet

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS141317: 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 IPv6196
AS18229CtrlSHostingIPv4135
AS151690FAB FIVE NETWORK PRIVATE LIMITEDResidentialIPv460

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS135715INet Services Pvt LtdHostingIPv4155
AS136278KARAD D INFRA GIGA NET PRIVATE LIMITEDUnclassifiedIPv4118
AS149610It Service CenterUnclassifiedIPv460
AS141533J K ConnectUnclassifiedIPv459

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS18229CtrlSHostingIPv4495
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv6228
AS135715INet Services Pvt LtdHostingIPv4155
AS136278KARAD D INFRA GIGA NET PRIVATE LIMITEDUnclassifiedIPv4118
AS149610It Service CenterUnclassifiedIPv460
AS151690FAB FIVE NETWORK PRIVATE LIMITEDResidentialIPv460
AS141533J K ConnectUnclassifiedIPv459

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.