asn.dev

Observed topology

AS141549 KFONLTD-AS-IN - KERALA FIBRE OPTIC NETWORK LIMITED

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS141549: 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
AS55410Vodafone Idea LtdMobileIPv4 IPv6921
AS9498BHARTI Airtel Ltd.MobileIPv4476
AS9829National Internet BackboneResidentialIPv4 IPv6181
AS55836Reliance Jio Infocomm LimitedMobileIPv4 IPv6125

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS141306Centre For Development Of Imaging TechnologyUnclassifiedIPv458
AS133037KERALA STATE IT MISSIONUnclassifiedIPv425
AS131787Keltron HouseUnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS55410Vodafone Idea LtdMobileIPv4 IPv6992
AS9498BHARTI Airtel Ltd.MobileIPv4485
AS9829National Internet BackboneResidentialIPv4 IPv6186
AS55836Reliance Jio Infocomm LimitedMobileIPv4 IPv6125
AS141306Centre For Development Of Imaging TechnologyUnclassifiedIPv458
AS133037KERALA STATE IT MISSIONUnclassifiedIPv425
AS131787Keltron HouseUnclassifiedIPv42

Provenance

Where this comes from

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