asn.dev

Observed topology

AS4670 HYUNDAI-KR Shinbiro

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS4670: 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
AS9848SEJONG NETWORKSResidentialIPv4 IPv623,220
AS3786LG DACOM CorporationUnclassifiedIPv446

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS9980LOTTE INNOVATE Co.,LtdUnclassifiedIPv4834
AS20940Akamai International B.V.HostingIPv4 IPv6154
AS38429Boryung Pharmaceutical Co.,Ltd.UnclassifiedIPv439
AS9645NEXT SECURITIES CORPORATIONUnclassifiedIPv423
AS9842LOTTE INNOVATE Co.,LtdUnclassifiedIPv412
AS138195MOACK.Co.LTDUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9848SEJONG NETWORKSResidentialIPv4 IPv624,343
AS9980LOTTE INNOVATE Co.,LtdUnclassifiedIPv4834
AS20940Akamai International B.V.HostingIPv4 IPv6214
AS3786LG DACOM CorporationUnclassifiedIPv446
AS38429Boryung Pharmaceutical Co.,Ltd.UnclassifiedIPv439
AS9645NEXT SECURITIES CORPORATIONUnclassifiedIPv423
AS9842LOTTE INNOVATE Co.,LtdUnclassifiedIPv412
AS138195MOACK.Co.LTDUnclassifiedIPv41

Provenance

Where this comes from

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