asn.dev

Observed topology

AS58778 MANGOTELESERVICES-ITC-AS-BD Mango Teleservices Limited for ITC

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS58778: 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
AS9583Sify LimitedUnclassifiedIPv4180

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS58945Virgo Communication LtdUnclassifiedIPv4 IPv688
AS17806Tire-1 IP Transit Provider of BangladeshMobileIPv4 IPv620

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9583Sify LimitedUnclassifiedIPv4 IPv6530
AS58945Virgo Communication LtdUnclassifiedIPv4 IPv6401
AS24482SG.GSHostingIPv4 IPv669
AS17806Tire-1 IP Transit Provider of BangladeshMobileIPv4 IPv620
AS58717Summit Communications LtdUnclassifiedIPv42

Provenance

Where this comes from

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