asn.dev

Observed topology

AS131464 DJBL-AS-AP - Digi Jadoo Broadband Ltd

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS131464: 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
AS134734Velocity Networks LimitedUnclassifiedIPv4 IPv61,903
AS58682Level3 Carrier Ltd.HostingIPv4189

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS152856Genex Infosys LimitedUnclassifiedIPv459
AS154131Seven Stars Hospital & Diagnostic CenterHostingIPv637
AS15015699ITHostingIPv4 IPv615
AS149783Intelwebhost LtdUnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS134734Velocity Networks LimitedUnclassifiedIPv4 IPv62,016
AS58682Level3 Carrier Ltd.HostingIPv4189
AS152856Genex Infosys LimitedUnclassifiedIPv459
AS154131Seven Stars Hospital & Diagnostic CenterHostingIPv637
AS15015699ITHostingIPv4 IPv615
AS149783Intelwebhost LtdUnclassifiedIPv42

Provenance

Where this comes from

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