asn.dev

Observed topology

AS4680 MIND Mitsubishi Electric Information Network Corporation

Unclassified APNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS4680: 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
AS32787Akamai Technologies, Inc.HostingIPv4600
AS2497Internet Initiative Japan Inc.UnclassifiedIPv4 IPv6363
AS4713NTT DOCOMO BUSINESS,Inc.ResidentialIPv4295
AS4637Telstra GlobalUnclassifiedIPv4170
AS6939Hurricane Electric LLCTransitIPv4 IPv6100
AS9002RETN LimitedUnclassifiedIPv4 IPv611
AS9304HGC Global Communications LimitedHostingIPv4 IPv611
AS24482SG.GSHostingIPv4 IPv611
AS132132MyRepublic Ltd.ResidentialIPv410

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS32787Akamai Technologies, Inc.HostingIPv4600
AS2497Internet Initiative Japan Inc.UnclassifiedIPv4 IPv6363
AS4713NTT DOCOMO BUSINESS,Inc.ResidentialIPv4295
AS4637Telstra GlobalUnclassifiedIPv4170
AS6939Hurricane Electric LLCTransitIPv4 IPv6100
AS9002RETN LimitedUnclassifiedIPv4 IPv611
AS9304HGC Global Communications LimitedHostingIPv4 IPv611
AS24482SG.GSHostingIPv4 IPv611
AS132132MyRepublic Ltd.ResidentialIPv410

Provenance

Where this comes from

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