Observed topology

AS135248 VORTEXIPL-AS-IN VORTEX INFOCOM PRIVATE LIMITED

Unclassified APNIC

Upstreams 1 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 1

Upstream graph Who carries AS135248, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS135248 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS135248: 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.

AS	Network	Type	Families	Paths seen
AS136334	Vortex Netsol Private Limited	Residential	IPv4 IPv6	392

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS136300	Tgn Networks Private Limited	Unclassified	IPv4	120
AS150579	Wonderworld Communication	Unclassified	IPv4	120
AS146921	Linked Net Techno Services Pvt Ltd	Unclassified	IPv4	119
AS136723	MLG ENTERPRISES	Unclassified	IPv4	118

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS136334	Vortex Netsol Private Limited	Residential	IPv4 IPv6	989
AS136300	Tgn Networks Private Limited	Unclassified	IPv4	240
AS150579	Wonderworld Communication	Unclassified	IPv4	120
AS146921	Linked Net Techno Services Pvt Ltd	Unclassified	IPv4	119
AS136723	MLG ENTERPRISES	Unclassified	IPv4	118

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.