asn.dev

Observed topology

AS149781 STACKBIT-AS-AP STACKBIT INTERNET SERVICES PRIVATE LIMITED

Residential APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS149781: 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 IPv6329
AS24482SG.GSHostingIPv45

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS150151Evergreen InternetUnclassifiedIPv4180
AS141794THANGAM COMMUNICATION PRIVATE LIMITEDUnclassifiedIPv490
AS137620Pink Broadband Service Pvt LtdResidentialIPv462
AS136230Evergreen InternetResidentialIPv431
AS149245GTECH COMMUNICATION PRIVATE LIMITEDUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4 IPv6622
AS150151Evergreen InternetUnclassifiedIPv4180
AS141794THANGAM COMMUNICATION PRIVATE LIMITEDUnclassifiedIPv490
AS137620Pink Broadband Service Pvt LtdResidentialIPv462
AS58898Rainbow communications India Pvt LtdResidentialIPv458
AS136230Evergreen InternetResidentialIPv431
AS24482SG.GSHostingIPv418
AS149245GTECH COMMUNICATION PRIVATE LIMITEDUnclassifiedIPv41

Provenance

Where this comes from

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