AS17676 SoftBank Corp.
AS17676 is operated by SoftBank Corp. and registered with APNIC (JP) since 2001-03-26.
It announces 482 IPv4 and 3 IPv6 prefixes, 86% of them RPKI valid.
RIPE RIS sees 40 upstream and peer networks and 308 downstream networks next to it.
PeeringDB lists it as an NSP network at 10 internet exchanges and 12 facilities. Its peering policy is selective.
| Name | SoftBank Corp. |
|---|---|
| Registry handle | GIGAINFRA |
| Registry (RIR) | APNIC |
| Country | Japan (JP) |
| Delegated on | 2001-03-26 |
| Network type | NSP, Global |
| Peering policy | Selective |
| IRR as-set | JPIRR::AS-GIGAINFRA JPIRR::AS-GIGAINFRA-V6 |
| Prefixes (IPv4 / IPv6) | 482 / 3 |
| RPKI valid | 86% (419 / 485) |
| Upstreams and peers | 40 |
| Downstream networks | 308 |
| Website | softbank.jp/en |
Routing health
- AS17676 announces 482 IPv4 and 3 IPv6 prefixes.
- 419 of 485 announced prefixes are RPKI valid.
- 66 announced prefixes are not covered by a ROA of AS17676 (they may have none, or another network’s).
- 40 upstreams and peers, 308 downstream networks seen.
For every check with the fix (IRR route objects, the RPKI state of each route, reverse DNS and the registration), run the full network report.
Announced prefixes 485
- 1.112.0.0/14
- 36.240.0.0/14
- 36.244.0.0/14
- 49.252.0.0/16
- 49.253.0.0/16
- 60.64.0.0/10
- 60.64.0.0/16
- 60.65.0.0/16
- 60.66.0.0/16
- 60.67.0.0/16
- 60.68.0.0/16
- 60.69.0.0/16
- 60.70.0.0/16
- 60.71.0.0/16
- 60.72.0.0/16
- 60.73.0.0/16
- 60.74.0.0/16
- 60.75.0.0/16
- 60.76.0.0/16
- 60.77.0.0/16
- 60.78.0.0/16
- 60.79.0.0/16
- 60.80.0.0/16
- 60.81.0.0/16
- 60.82.0.0/16
- 60.83.0.0/16
- 60.84.0.0/16
- 60.85.0.0/16
- 60.86.0.0/16
- 60.87.0.0/16
- 60.88.0.0/16
- 60.89.0.0/16
- 60.90.0.0/16
- 60.91.0.0/16
- 60.92.0.0/16
- 60.93.0.0/16
- 60.94.0.0/16
- 60.95.0.0/16
- 60.96.0.0/16
- 60.97.0.0/16
- 60.98.0.0/16
- 60.99.0.0/16
- 60.100.0.0/16
- 60.101.0.0/16
- 60.102.0.0/16
- 60.103.0.0/16
- 60.104.0.0/16
- 60.105.0.0/16
- 60.106.0.0/16
- 60.107.0.0/16
- 60.108.0.0/16
- 60.109.0.0/16
- 60.110.0.0/16
- 60.111.0.0/16
- 60.112.0.0/16
- 60.113.0.0/16
- 60.114.0.0/16
- 60.115.0.0/16
- 60.116.0.0/16
- 60.117.0.0/16
- 60.118.0.0/16
- 60.119.0.0/16
- 60.120.0.0/16
- 60.121.0.0/16
- 60.122.0.0/16
- 60.124.0.0/16
- 60.125.0.0/16
- 60.126.0.0/16
- 60.127.0.0/16
- 60.128.0.0/11
- 60.128.0.0/16
- 60.129.0.0/16
- 60.130.0.0/16
- 60.131.0.0/16
- 60.132.0.0/16
- 60.133.0.0/16
- 60.134.0.0/16
- 60.135.0.0/16
- 60.136.0.0/16
- 60.137.0.0/16
- 60.138.0.0/16
- 60.139.0.0/16
- 60.140.0.0/16
- 60.141.0.0/16
- 60.142.0.0/16
- 60.143.0.0/16
- 60.144.0.0/16
- 60.145.0.0/16
- 60.146.0.0/16
- 60.147.0.0/16
- 60.148.0.0/16
- 60.149.0.0/16
- 60.150.0.0/16
- 60.151.0.0/16
- 60.152.0.0/16
- 60.153.0.0/16
- 60.154.0.0/16
- 60.155.0.0/16
- 60.156.0.0/16
- 60.157.0.0/16
Showing the first 100.
Upstreams and peers 40
The networks RIPE RIS sees next to AS17676 in BGP paths, the most visible first.
Peering
Peering policy: Selective. Suggested max-prefix limits: 10,000 IPv4, 1,000 IPv6. PeeringDB record
| Exchange | Ports | Speed | Route server |
|---|---|---|---|
| BBIX Amsterdam | 2 | 200G | No |
| BBIX Hong Kong | 2 | 60G | No |
| BBIX Osaka | 6 | 3.2T | No |
| BBIX Singapore | 2 | 400G | No |
| BBIX Tokyo | 6 | 5.2T | No |
| BBIX US-West | 2 | 400G | No |
| Equinix Singapore | 1 | 10G | No |
| JPNAP Osaka | 2 | 200G | No |
| JPNAP Tokyo: Peering | 2 | 200G | No |
| SIX Seattle: MTU 1500 | 1 | 100G | No |
| Facility | City | Country |
|---|---|---|
| AT TOKYO (CC1/CC2) | Tokyo | JP |
| CoreSite - Los Angeles (LA1) One Wilshire | Los Angeles | US |
| Digital Realty AMS9 - Amsterdam | Amsterdam | NL |
| Digital Realty Seattle SEA10 | Seattle | US |
| Equinix OS1 - Osaka | Osaka | JP |
| Equinix SG1 - Singapore | Singapore | SG |
| Equinix SV1/SV5/SV10 - Silicon Valley, San Jose | San Jose | US |
| MEGA-i (iAdvantage Hong Kong) | Hong Kong | HK |
| NTT DATA Dojima (building #4) | Osaka | JP |
| NTT DATA Otemachi Bldg | Tokyo | JP |
| NTT DOCOMO BUSINESS Tokyo (NW1) | Tokyo | JP |
| NTT Sonezaki Data Center(Dojima Campus) | Osaka-Shi Kita-Ku | JP |
More about AS17676
Sources: RIR delegation data and PeeringDB (updated daily); routing from RIPEstat (RIPE NCC RIS and RPKI), refreshed daily. Routing data from 2026-11-12 18:18 UTC. The country is where the AS number was registered, not necessarily where the network operates.