asn.dev

Observed topology

AS18068 ACROSS - Dream Wave Shizuoka Co. Ltd.

Unclassified DROP-listed space APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS18068: 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
AS146986SUZUYO SHINWART CORPORATIONUnclassifiedIPv4967
AS2519ARTERIA Networks CorporationUnclassifiedIPv4 IPv6800
AS2518BIGLOBE Inc.ResidentialIPv4 IPv6514
AS17676SoftBank Corp.MobileIPv4 IPv6467
AS3491PCCW Global (HK) Ltd.TransitIPv4167
AS24482SG.GSHostingIPv4 IPv633
AS9304HGC Global Communications LimitedHostingIPv428
AS9002RETN LimitedUnclassifiedIPv4 IPv65

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS55907GMO Internet, Inc.UnclassifiedIPv4 IPv692

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS146986SUZUYO SHINWART CORPORATIONUnclassifiedIPv4967
AS2519ARTERIA Networks CorporationUnclassifiedIPv4 IPv6838
AS2518BIGLOBE Inc.ResidentialIPv4 IPv6549
AS17676SoftBank Corp.MobileIPv4 IPv6480
AS3491PCCW Global (HK) Ltd.TransitIPv4173
AS55907GMO Internet, Inc.UnclassifiedIPv4 IPv692
AS24482SG.GSHostingIPv4 IPv633
AS9304HGC Global Communications LimitedHostingIPv428
AS9002RETN LimitedUnclassifiedIPv4 IPv65

Provenance

Where this comes from

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