asn.dev

Observed topology

AS141846 NETFIX-AS-IN Netfix Networks Opc Pvt Ltd

Residential APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS141846: 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
AS17762Tata Teleservices Maharashtra LtdUnclassifiedIPv4 IPv6443
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4 IPv661
AS24482SG.GSHostingIPv4 IPv67

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS133249SEVEN INFOTECHUnclassifiedIPv4 IPv6155
AS137625Blue Vision Cable Network Pvt LtdUnclassifiedIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS17762Tata Teleservices Maharashtra LtdUnclassifiedIPv4 IPv6628
AS133249SEVEN INFOTECHUnclassifiedIPv4 IPv6155
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4 IPv662
AS137625Blue Vision Cable Network Pvt LtdUnclassifiedIPv460
AS138296Juweriyah Networks Private LimitedResidentialIPv427
AS24482SG.GSHostingIPv4 IPv69

Provenance

Where this comes from

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