AS17766
Transit ProviderNEXON-AS-AP
Also known as: GCOMM
Nexon Asia Pacific Pty Ltd
71
IPv4 Prefixes
0
IPv6 Prefixes
138.2K
IPv4 Addresses
RIR
APNIC
Scope
Australia
Traffic
50-100Gbps
Ratio
Mostly Inbound
Peering
Open
IRR AS-SET
AS-17766
Risk Score
25/100
Network Characteristics
Unknown
IPv6 Enabled
宣告的前缀 (显示前 71 个)
| 前缀 | 网络类型 | 风险分 | 标签 | 首次发现 |
|---|---|---|---|---|
| 43.251.108.0/22 | transit | 25 |
-
|
2026-01-31 |
| 43.251.108.0/23 | transit | 25 |
-
|
2026-01-31 |
| 43.251.110.0/23 | transit | 25 |
-
|
2026-01-31 |
| 103.1.228.0/24 | transit | 25 |
-
|
2026-01-31 |
| 103.1.229.0/24 | transit | 25 |
-
|
2026-01-31 |
| 103.1.230.0/23 | transit | 25 |
-
|
2026-01-31 |
| 103.10.32.0/22 | transit | 25 |
-
|
2026-01-31 |
| 103.10.35.0/24 | transit | 25 |
-
|
2026-01-31 |
| 103.16.148.0/22 | transit | 25 |
-
|
2026-01-31 |
| 103.60.107.0/24 | transit | 25 |
-
|
2026-01-31 |
| 103.113.250.0/23 | transit | 25 |
-
|
2026-01-31 |
| 103.204.228.0/24 | transit | 25 |
-
|
2026-01-31 |
| 103.252.191.0/24 | transit | 25 |
-
|
2026-01-31 |
| 116.213.0.0/23 | transit | 25 |
-
|
2026-01-31 |
| 116.213.3.0/24 | transit | 25 |
-
|
2026-01-31 |
| 116.213.6.0/23 | transit | 25 |
-
|
2026-01-31 |
| 116.213.8.0/22 | transit | 25 |
-
|
2026-01-31 |
| 116.213.12.0/22 | transit | 25 |
-
|
2026-01-31 |
| 116.213.16.0/22 | transit | 25 |
-
|
2026-01-31 |
| 124.109.64.0/19 | transit | 25 |
-
|
2026-01-31 |
| 150.129.84.0/22 | transit | 25 |
-
|
2026-01-31 |
| 192.150.129.0/24 | transit | 25 |
-
|
2026-01-31 |
| 199.58.4.0/24 | transit | 25 |
-
|
2026-01-31 |
| 202.9.87.0/24 | transit | 25 |
-
|
2026-01-31 |
| 202.125.164.0/23 | transit | 25 |
-
|
2026-01-31 |
| 202.125.168.0/21 | transit | 25 |
-
|
2026-01-31 |
| 202.155.160.0/20 | transit | 25 |
-
|
2026-01-31 |
| 203.3.166.0/24 | transit | 25 |
-
|
2026-01-31 |
| 203.9.152.0/22 | transit | 25 |
-
|
2026-01-31 |
| 203.9.246.0/23 | transit | 25 |
-
|
2026-01-31 |
| 203.9.248.0/23 | transit | 25 |
-
|
2026-01-31 |
| 203.12.234.0/24 | transit | 25 |
-
|
2026-01-31 |
| 203.17.76.0/22 | transit | 25 |
-
|
2026-01-31 |
| 203.19.214.0/23 | transit | 25 |
-
|
2026-01-31 |
| 203.19.244.0/22 | transit | 25 |
-
|
2026-01-31 |
| 203.22.188.0/24 | transit | 25 |
-
|
2026-01-31 |
| 203.25.97.0/24 | transit | 25 |
-
|
2026-02-10 |
| 203.25.126.0/23 | transit | 25 |
-
|
2026-01-31 |
| 203.26.138.0/24 | transit | 25 |
-
|
2026-01-31 |
| 203.26.139.0/24 | transit | 25 |
-
|
2026-01-31 |
| 203.28.121.0/24 | transit | 25 |
-
|
2026-01-31 |
| 203.30.164.0/23 | transit | 25 |
-
|
2026-01-31 |
| 203.30.164.0/24 | transit | 25 |
-
|
2026-01-31 |
| 203.30.199.0/24 | transit | 25 |
-
|
2026-01-31 |
| 203.31.116.0/23 | transit | 25 |
-
|
2026-01-31 |
| 203.31.116.0/24 | transit | 25 |
-
|
2026-01-31 |
| 203.32.160.0/20 | transit | 25 |
-
|
2026-01-31 |
| 203.33.150.0/24 | transit | 25 |
-
|
2026-01-31 |
| 203.55.1.0/24 | transit | 25 |
-
|
2026-01-31 |
| 203.56.26.0/24 | transit | 25 |
-
|
2026-01-31 |
| 203.76.0.0/18 | transit | 25 |
-
|
2026-01-31 |
| 203.149.64.0/20 | transit | 25 |
-
|
2026-01-31 |
| 203.149.64.0/22 | transit | 25 |
-
|
2026-01-31 |
| 203.149.68.0/22 | transit | 25 |
-
|
2026-01-31 |
| 203.149.72.0/22 | transit | 25 |
-
|
2026-01-31 |
| 203.149.76.0/22 | transit | 25 |
-
|
2026-01-31 |
| 203.149.80.0/21 | transit | 25 |
-
|
2026-01-31 |
| 203.149.80.0/22 | transit | 25 |
-
|
2026-01-31 |
| 203.149.84.0/22 | transit | 25 |
-
|
2026-01-31 |
| 204.154.60.0/24 | transit | 25 |
-
|
2026-01-31 |
| 210.215.0.0/16 | transit | 25 |
-
|
2026-01-31 |
| 210.215.5.0/24 | transit | 25 |
-
|
2026-01-31 |
| 210.215.6.0/24 | transit | 25 |
-
|
2026-01-31 |
| 210.215.8.0/24 | transit | 25 |
-
|
2026-01-31 |
| 210.215.48.0/24 | transit | 25 |
-
|
2026-01-31 |
| 210.215.72.0/24 | transit | 25 |
-
|
2026-01-31 |
| 210.215.75.0/24 | transit | 25 |
-
|
2026-01-31 |
| 210.215.77.0/24 | transit | 25 |
-
|
2026-01-31 |
| 210.215.90.0/24 | transit | 25 |
-
|
2026-01-31 |
| 210.215.112.0/24 | transit | 25 |
-
|
2026-01-31 |
| 210.215.113.0/24 | transit | 25 |
-
|
2026-01-31 |
PeeringDB 备注
As we advertise all our prefixes to IX route servers we will generally only do bilateral peering where the other party does not use the route servers for all of their prefixes.
API 调用
# 使用 cURL 查询此 ASN
curl -H "Authorization: Bearer YOUR_API_KEY" \
"https://ipv4.dev/api/v1/asn/17766"