asn.dev

Observed topology

AS58768 DAFFODILNET-BD - Daffodil Online Ltd.

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS58768: 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
AS58717Summit Communications LtdUnclassifiedIPv4 IPv6676
AS58715EARTH TELECOMMUNICATION (Pvt) LTD.UnclassifiedIPv4114
AS58656bdHUB LimitedUnclassifiedIPv466

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS139016EXONHOSTUnclassifiedIPv4 IPv6445
AS150142Wolast TechnologiesUnclassifiedIPv4348
AS141988Optimus TechnologiesUnclassifiedIPv4 IPv693
AS154109Hosting OxygenUnclassifiedIPv4 IPv684
AS151954Kushtia ColoUnclassifiedIPv458
AS153981Daffodil International UniversityUnclassifiedIPv458

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS58717Summit Communications LtdUnclassifiedIPv4 IPv61,962
AS139016EXONHOSTUnclassifiedIPv4 IPv6536
AS150142Wolast TechnologiesUnclassifiedIPv4348
AS141988Optimus TechnologiesUnclassifiedIPv4 IPv6265
AS58715EARTH TELECOMMUNICATION (Pvt) LTD.UnclassifiedIPv4132
AS58656bdHUB LimitedUnclassifiedIPv492
AS154109Hosting OxygenUnclassifiedIPv4 IPv684
AS151954Kushtia ColoUnclassifiedIPv458
AS153981Daffodil International UniversityUnclassifiedIPv458
AS138358Purple IT LtdUnclassifiedIPv423

Provenance

Where this comes from

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