AS38690 — HYOSUNGITX-AS-KR-KR - HyosungITX
🇰🇷 South Korea · APNIC region · approx. 37.48, 126.90
HYOSUNGITX-AS-KR-KR - HyosungITX (AS38690) in South Korea has 2 direct BGP neighbours, ranked #35162 of 88104 by observed links.
Network intelligence
Neighbourhood
What's directly and indirectly (up to two hops) connected to AS38690 — the same force-directed layout as the main Topology view, computed fresh on every page load (reload for a different arrangement), with AS38690 itself always centred. Drag to pan, scroll/pinch to zoom, click a dot to jump to that AS's own page. Explore the full interactive map →
Announced prefixes
RPKI route-origin validity badge per prefix, from this instance's self-hosted Routinator (see Credits). The full, de-duplicated set seen across every BGP collector this snapshot imports — usually more than the “IPv4/IPv6 prefixes” counts above, which only reflect a single collector's own routing table.
- 49.236.128.0/22 RPKI Not Found
- 49.236.128.0/23 RPKI Not Found
- 49.236.130.0/23 RPKI Not Found
- 49.236.168.0/21 RPKI Not Found
- 49.236.176.0/20 RPKI Not Found
- 49.238.128.0/18 RPKI Not Found
- 103.11.24.0/22 RPKI Not Found
- 103.79.132.0/23 RPKI Not Found
- 103.79.134.0/23 RPKI Not Found
- 106.10.0.0/19 RPKI Not Found
- 110.93.128.0/20 RPKI Not Found
- 110.93.128.0/21 RPKI Not Found
- 110.93.136.0/21 RPKI Not Found
- 110.93.160.0/19 RPKI Not Found
- 110.93.160.0/20 RPKI Not Found
- 110.93.176.0/20 RPKI Not Found
- 114.31.32.0/19 RPKI Not Found
- 114.31.32.0/20 RPKI Not Found
- 114.31.48.0/20 RPKI Not Found
- 182.173.176.0/22 RPKI Not Found
No loaded prefix matches that filter. Try loading more below, or narrow/widen the filter text.
...and 3 more.
Upstream providers (2)
Networks that this AS is a customer of (inferred from public BGP data by BGPKIT's as2rel dataset, a heuristic, not ground truth).
Geographic footprint
Geolocated (estimated) country of every prefix AS38690 announces, via IP geolocation against DB-IP City Lite — not AS38690's RIR registration country (see the stats above), and not necessarily where its infrastructure physically sits.