asn.dev

Observed topology

AS133593 VBCBROADBAND-AS VIZAG BROADCASTING COMPANY PVT. LTD

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS133593: 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
AS45820Tata Teleservices ISP ASResidentialIPv41,526
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv6397
AS35280F5 Networks SARLHostingIPv48

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS136715Datasoft Comnet Pvt LtdUnclassifiedIPv4 IPv6158
AS58457Gandhi NagarUnclassifiedIPv445

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS45820Tata Teleservices ISP ASResidentialIPv41,587
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv6599
AS136715Datasoft Comnet Pvt LtdUnclassifiedIPv4 IPv6158
AS136956Assistive Networks and technologies Pvt LtdResidentialIPv460
AS58457Gandhi NagarUnclassifiedIPv445
AS35280F5 Networks SARLHostingIPv48

Provenance

Where this comes from

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