asn.dev

Observed topology

AS135259 SKYSIKAR-AS SKYLINE INFONET PRIVATE LIMITED

Unclassified APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS135259: 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
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4 IPv6477
AS24482SG.GSHostingIPv4 IPv621

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS135685Deserver Hosting Hub Private LimitedUnclassifiedIPv4 IPv696
AS136346Sanishth Internet Services Private LimitedUnclassifiedIPv461
AS149537VAST WEB INDIA PRIVATE LIMITEDUnclassifiedIPv460
AS136361Click4net Internet Services P LtdUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4 IPv6688
AS135685Deserver Hosting Hub Private LimitedUnclassifiedIPv4 IPv696
AS136346Sanishth Internet Services Private LimitedUnclassifiedIPv461
AS149537VAST WEB INDIA PRIVATE LIMITEDUnclassifiedIPv460
AS24482SG.GSHostingIPv4 IPv630
AS136361Click4net Internet Services P LtdUnclassifiedIPv43

Provenance

Where this comes from

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