Network operator
HiNet (Chunghwa Telecom)
2 networks combined into one view.
Operators are grouped by registered network name. Each figure below is the total across every network on this page, which is what a single network page cannot show.
What this tells you
- An estimated 9,031,711 people use this operator's 2 networks, from 7,793,576 observations over a 60 day window.
- 9,030,595 of those are in Taiwan, 34% of everyone online there.
- Address space is concentrated in Taiwan (100% of the IPv4 space), across 2 countries in total.
Countries in this space
Space we can place in a country covers 100% of these networks' IPv4 space and 100% of their IPv6 space. The table below divides that space.
| Country | IPv4 share | IPv6 share | |
|---|---|---|---|
| Taiwan | 100% | 99% | |
| United States | <0.1% | 0.9% |
Organisations holding assignments here
Registered organisations account for <0.1% of these networks' IPv4 space. The table below divides that space. Registered holders come from the bulk whois that RIPE, APNIC and AFRINIC publish. ARIN and LACNIC do not publish theirs, so space held in North and South America is largely unattributed here.
| Organisation | IPv4 share | |
|---|---|---|
| Taiwan Semiconductor Manufacturing Company, Ltd. | 100% |
Anonymizer signals
Flagged space covers 1% of these networks' IPv4 space and <0.1% of their IPv6 space. The table below divides that space.
| Category | IPv4 share | IPv6 share | |
|---|---|---|---|
| Open proxy | 53% | 100% | |
| Datacenter | 48% | 100% | |
| VPN | 0.2% | 100% | |
| Not covered by any of these | - | - |
One address can carry more than one of these, so the rows add up to more than the space they cover.
All 2 networks run by this operator
| ASN | Name | Estimated users |
|---|---|---|
| AS3462 | HiNet (Chunghwa Telecom) | 9,030,595 |
| AS33717 | HiNet (Chunghwa Telecom) | 1,116 |
Every figure on this page is also JSON: /api/v2/directory/isp/hinet-chunghwa-telecom. Breakdowns paginate from there, so a table showing the largest rows here returns all of them. Read the API.