Network · data from 2026-11-12
AS17675 Internap Japan Co.,Ltd.
Registry name: AS-PNAPTOK - PacketFabric (Japan) Co., Ltd., JP · PeeringDB
18IPv4 routes
100.0% RPKI valid · 94.4% with a route object
2IPv6 routes
50.0% RPKI valid · 50.0% with a route object
1RPKI invalid
0 origin · 1 maxLength
0No ROA
2 with no route object for this origin
3Low visibility
seen by under 10% of full-table peers
54Route objects not announced
registered with origin AS17675, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS17675, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 2405:e800:6553::/48 | Invalid: maxLength | Nonecovered by 2405:e800::/32 | 48 8%low visibility |
| 61.211.169.0/24 | Valid | Nonecovered by 61.211.160.0/20 | 673 100% |
| 61.211.160.0/20 | Valid | Other IRR onlyRADB | 673 100% |
| 61.211.160.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 122.200.36.0/22 | Valid | Other IRR onlyRADB | 673 100% |
| 203.169.8.0/21 | Valid | Other IRR onlyRADB | 673 100% |
| 203.169.14.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 219.96.96.0/19 | Valid | Other IRR onlyRADB | 673 100% |
| 219.113.0.0/19 | Valid | Other IRR onlyRADB | 673 100% |
| 210.193.64.0/18 | Valid | Other IRR onlyRADB | 672 100% |
| 210.193.120.0/21 | Valid | Other IRR onlyRADB | 672 100% |
| 210.193.123.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 210.193.124.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 218.40.144.0/20 | Valid | Other IRR onlyRADB | 672 100% |
| 218.216.96.0/20 | Valid | Other IRR onlyRADB | 672 100% |
| 2405:e800::/32 | Valid | Other IRR onlyRADB | 634 100% |
| 210.193.122.0/24 | Valid | Other IRR onlyRADB | 2 0%low visibility |
| 218.216.103.0/24 | Valid | Other IRR onlyRADB | 1 0%low visibility |
| 103.38.154.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.38.154.0/24 | Valid | RIR databaseAPNIC | 672 100% |
AS-SET
AS17675's PeeringDB record names no AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 73 are in fix.csv.
- ROA: maxLength1
- Route object: none2
- Route object: RIR16
- Route object: not announced54
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 2405:e800:6553::/48 | ROA 2405:e800::/32 AS17675 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2405:e800:6553::/48. |
| Route object: none | 2405:e800:6553::/48 | No route object for it. A route object for 2405:e800::/32 with origin AS17675 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17675 in the RIR database for the space. |
| Route object: none | 61.211.169.0/24 | No route object for it. A route object for 61.211.160.0/20 with origin AS17675 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17675 in the RIR database for the space. |
| Route object: RIR | 61.211.160.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 61.211.160.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 122.200.36.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.169.8.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.169.14.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.96.96.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 219.113.0.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.193.64.0/18 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.193.120.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.193.123.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.193.124.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 218.40.144.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 218.216.96.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2405:e800::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.193.122.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 218.216.103.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS17675 whose prefix no peer sees AS17675 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 50.20.224.0/21 | RADB | Valid |
| 61.211.164.0/24 | RADB | Valid |
| 61.211.165.0/24 | RADB | Valid |
| 61.211.168.0/24 | RADB | Valid |
| 63.251.8.0/24 | RADB | Valid |
| 69.52.134.0/24 | RADB | No ROA |
| 72.5.82.0/24 | RADB | No ROA |
| 103.28.24.0/24 | RADB | Valid |
| 103.38.155.0/24 | APNIC | Valid |
| 122.200.32.0/21 | RADB | No ROA |
| 149.234.185.0/24 | APNIC, RADB | Valid |
| 149.234.190.0/24 | APNIC, RADB | Valid |
| 192.150.24.0/24 | RADB | No ROA |
| 198.155.101.0/24 | RADB | No ROA |
| 198.155.178.0/24 | RADB | No ROA |
| 198.178.42.0/24 | RADB | No ROA |
| 202.208.1.0/24 | RADB | No ROA |
| 203.169.15.0/24 | RADB | Valid |
| 210.193.97.0/24 | RADB | Valid |
| 210.193.113.0/24 | RADB | Valid |
| 210.193.120.0/24 | RADB | Valid |
| 210.193.125.0/24 | RADB | Valid |
| 216.65.240.0/24 | RADB | No ROA |
| 216.65.241.0/24 | RADB | No ROA |
| 216.65.242.0/24 | RADB | No ROA |
| 216.65.243.0/24 | RADB | No ROA |
| 216.65.244.0/24 | RADB | No ROA |
| 216.65.245.0/24 | RADB | No ROA |
| 216.65.246.0/24 | RADB | No ROA |
| 216.65.247.0/24 | RADB | No ROA |
| 216.65.248.0/24 | RADB | No ROA |
| 216.65.249.0/24 | RADB | No ROA |
| 216.65.250.0/24 | RADB | No ROA |
| 216.65.251.0/24 | RADB | No ROA |
| 216.65.253.0/24 | RADB | No ROA |
| 216.65.254.0/24 | RADB | No ROA |
| 216.65.255.0/24 | RADB | No ROA |
| 216.241.246.0/24 | RADB | No ROA |
| 218.40.158.0/23 | RADB | Valid |
| 219.96.96.0/24 | RADB | Valid |
| 219.96.104.0/21 | RADB | Valid |
| 219.96.104.0/22 | RADB | Valid |
| 219.96.104.0/24 | RADB | Valid |
| 219.96.105.0/24 | RADB | Valid |
| 219.96.106.0/24 | RADB | Valid |
| 219.96.107.0/24 | RADB | Valid |
| 219.96.108.0/22 | RADB | Valid |
| 219.96.108.0/24 | RADB | Valid |
| 219.96.109.0/24 | RADB | Valid |
| 219.96.110.0/24 | RADB | Valid |
| 219.96.111.0/24 | RADB | Valid |
| 219.113.18.0/24 | RADB | Valid |
| 219.113.22.0/24 | RADB | Valid |
| 219.113.26.0/24 | RADB | Valid |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.