Observed topology

AS151967 DLIS-AS-AP DLITS

Unclassified APNIC

Upstreams 2 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS151967: 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
AS58826	ping by ICOM Bangladesh Ltd	Unclassified	IPv4	60
AS132298	Antaranga Dot Com Ltd	Unclassified	IPv4	60

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS147303	ColoCone	Unclassified	IPv4	124
AS148993	Diana Host Ltd	Unclassified	IPv4	65
AS131192	BD WEBS DOT COM	Unclassified	IPv4	60
AS138145	Web Host BD	Unclassified	IPv4	5

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS63996	Mazeda Networks Limited	Residential	IPv4	148
AS147303	ColoCone	Unclassified	IPv4	124
AS133112	Spectra Technologies Limited	Unclassified	IPv4	105
AS148993	Diana Host Ltd	Unclassified	IPv4	65
AS58826	ping by ICOM Bangladesh Ltd	Unclassified	IPv4	60
AS131192	BD WEBS DOT COM	Unclassified	IPv4	60
AS132298	Antaranga Dot Com Ltd	Unclassified	IPv4	60
AS138145	Web Host BD	Unclassified	IPv4	5
AS137425	INCOMIT SOLUTION	Residential	IPv4	1

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-28 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.