Autonomous System
AS4670 — HYUNDAI-KR - Shinbiro(KR)
Last fetched
AS4670 is an Autonomous System operated by HYUNDAI-KR - Shinbiro and registered in KR. As of Tue, 04 Aug 2026 17:02:30 GMT, it announces 360 routed IP prefixes and peers with 7 other Autonomous Systems in the WhisperGraph BGP dataset.
Nutrition Label
Routing footprint
AS4670 announces 360 distinct routed prefixes. The 25-prefix sample below links to per-prefix pages with full conflict and reverse-DNS detail.
- 58.180.0.0/24
- 58.180.2.0/24
- 58.180.3.0/24
- 58.180.4.0/24
- 58.180.5.0/24
- 58.180.8.0/24
- 58.180.9.0/24
- 58.180.10.0/24
- 58.180.13.0/24
- 58.180.15.0/24
- 58.180.16.0/24
- 58.180.17.0/24
- 58.180.19.0/24
- 58.180.23.0/24
- 58.180.24.0/24
- 58.180.26.0/24
- 58.180.27.0/24
- 58.180.28.0/24
- 58.180.30.0/24
- 58.180.32.0/24
- 58.180.33.0/24
- 58.180.34.0/24
- 58.180.36.0/24
- 58.180.40.0/24
- 58.180.43.0/24
Peering ecosystem
7 distinct peers via BGP. The first 7 are listed below.
| Peer ASN | Operator | Country |
|---|---|---|
| AS138195 | MOACKCOLTD-AS-AP - MOACK.Co.LTD | KR |
| AS20940 | AKAMAI-ASN1 - Akamai International B.V. | NL |
| AS38429 | BORYUNG-AS-KR-KR - Boryung Pharmaceutical Co.,Ltd. | KR |
| AS9645 | HYUNDAIFUTURES-AS-KR - NEXT SECURITIES CORPORATION | KR |
| AS9842 | LDCC-AS-KR - LOTTE INNOVATE Co.,Ltd | KR |
| AS9848 | SejongTelecom-AS-KR-KR - SEJONG NETWORKS | KR |
| AS9980 | LDCC-AS-KR-KR - LOTTE INNOVATE Co.,Ltd | KR |
Blast radius
Count of dependent hostnames if AS4670 disappeared from the routing table.
Blast radius: Computing — check back later. The precompute pipeline refreshes this panel within a few days.
MOAS / hijack watch
Prefixes routed by AS4670 that another Autonomous System also announces. A non-empty list is one of the strongest BGP-hijack signals available without active probes.
No active MOAS conflicts. Every prefix announced by AS4670 is unique to AS4670 in the current routing snapshot.
Threat posture
Related pages
Pivot deeper into the graph from AS4670.
Cypher and MCP
Reproduce the headline metric directly against graph.whisper.security:
MATCH (a:ASN {name: "AS4670"})-[:HAS_NAME]->(n:ASN_NAME)
OPTIONAL MATCH (a)-[:HAS_COUNTRY]->(c:COUNTRY)
RETURN a.name AS asn, n.name AS operator, c.name AS countryOr query Whisper from your own LLM workflow via the Whisper MCP server.