AS4766Korea Telecom
As of 26th September 2026, AS4766 (Korea Telecom), a transit carrier registered in South Korea with APNIC, originates 2,719 IPv4 prefixes covering 70M addresses and 59 IPv6 prefixes. By IPv4 address space that makes it the 7th-largest of the 79,480 networks we see originating IPv4, and the largest of 908 in South Korea. It is seen behind 39 upstream networks, most often AS6939 (Hurricane Electric LLC) and AS132337 (Axclusive), and in front of 613 downstream networks. 5% of its announcements have a valid RPKI ROA; 6 are RPKI-invalid. 78% of its routes reach at least 90% of full-feed peers, and 3 prefixes are also originated by another network.
At a glance
IPv4 prefixes
IPv6 prefixes
IPv4 addresses
IPv6 /64s
Upstream graph
The networks AS4766 is seen behind, one and two hops out, drawn from real AS paths.
Networks observed one and two hops upstream of AS4766 in real AS paths. A thicker line means more vantage points saw that adjacency, so weight tracks how well attested it is — not how much traffic it carries. Adjacency is an observation; whether it is a transit purchase or a settlement-free peering is an inference, and is labelled as one wherever we show it.
Neighbouring networks
1,343
adjacent networks
- Upstreams
- 393%
- Peers
- 69151%
- Downstreams
- 61346%
Networks carrying this one's traffic toward the rest of the internet.
| Network | Country | Relationship | Paths | Vantage pts |
|---|---|---|---|---|
| AS6939Hurricane Electric LLC | Peer | 264,435 | 66 | |
| AS132337Axclusive | Peer | 68,671 | 2 | |
| AS1299Arelion (fka. Telia Carrier) | Peer | 54,810 | 62 | |
| AS2914NTT America, Inc. | Peer | 30,806 | 28 | |
| AS3356Lumen (Level 3) | Peer | 28,421 | 37 | |
| AS9002RETN Limited | Peer | 25,140 | 14 | |
| AS3257GTT Communications Inc. | Peer | 23,341 | 29 | |
| AS174Cogent Communications, LLC | Peer | 23,155 | 32 | |
| AS2497Internet Initiative Japan Inc. | Peer | 22,450 | 6 | |
| AS3491PCCW Global (HK) Ltd. | Peer | 13,960 | 8 |
Prefixes
All 2,778The largest blocks AS4766 originates, widest first.
| Prefix | Addresses | Visibility |
|---|---|---|
| 59.0.0.0/11 | 2.1M | 80/81 |
| 121.128.0.0/11 | 2.1M | 80/81 |
| 121.160.0.0/11 | 2.1M | 80/81 |
| 125.128.0.0/11 | 2.1M | 80/81 |
| 14.64.0.0/12 | 1M | 80/81 |
| 14.80.0.0/12 | 1M | 80/81 |
| 59.0.0.0/12 | 1M | 80/81 |
| 59.16.0.0/12 | 1M | 80/81 |
| 112.160.0.0/12 | 1M | 80/81 |
| 112.176.0.0/12 | 1M | 80/81 |
Routing health
How AS4766's own announcements validate against RPKI and how far they propagate. The same measures for the whole routing table are on the routing table in numbers.
RPKI origin validation
- Valid5.0%139
- Invalid0.2%6
- No ROA94.8%2,633
Propagation
- Globally propagated90% of full-feed peers or more77.9%2,163
- Partially propagated40% to 90%<0.1%1
- Seen by few peersUnder 40%22.1%614
Prefix sizes
IPv4 — 2,719 prefixes
- /112.1M addresses0.1%4
- /121M addresses0.9%24
- /13524k addresses1.8%50
- /14262k addresses0.5%13
- /15131k addresses0.5%13
- /1665.5k addresses1.3%34
- /1732.8k addresses1.3%36
- /1816.4k addresses1.0%28
- /198.2k addresses1.3%34
- /204.1k addresses1.5%42
- /212k addresses2.4%64
- /221k addresses4.7%128
- /23512 addresses7.0%190
- /24256 addresses54.7%1,486
- /25128 addresses7.9%214
- /2664 addresses3.5%96
- /2732 addresses3.2%88
- /2816 addresses2.8%76
- /298 addresses3.6%99
IPv6 — 59 prefixes
- /3017.2B × /646.8%4
- /318.6B × /646.8%4
- /324.3B × /6435.6%21
- /441M × /6411.9%7
- /4865.5k × /6418.6%11
- /49 and longerAggregated20.3%12
Recent changes
Announcements that started or stopped since 27th Aug 2026.
- Announced109.66.168.0/2122nd Sept 2026
- Announced109.66.234.0/2322nd Sept 2026
- Announced109.66.246.0/2322nd Sept 2026
- Announced170.130.68.0/2322nd Sept 2026
- Announced192.25.130.0/2322nd Sept 2026
- Announced192.25.178.0/2322nd Sept 2026
- Announced192.48.206.0/2322nd Sept 2026
- Announced192.6.170.0/2322nd Sept 2026
- Announced210.97.33.160/2722nd Sept 2026
- Announced211.184.64.0/2422nd Sept 2026
- Announced211.184.71.0/2422nd Sept 2026
- Announced211.184.72.0/2422nd Sept 2026
30 announced and 23 withdrawn in all; the most recent are shown.
Routing data derived from RouteViews MRT archives, BGPKIT relationship inference and public registry data.