Can China no longer use Tokyo 2 server in Japan?
Three days ago, my Tokyo server in Japan was completely disconnected. In the past, although the connection speed is slow and there are often data packet dropouts, but I do not require hi gh speed, so I have been using it. But now it's not connected. I rebuilt a server in Tokyo 2, Japan. The display is still IP impassable. A lot of changes, all the same, but my new address is the U. S. server shows that IP is passable, can be used normal ly. I would like to ask, is the server of Tokyo 2 in Japan no longer available in mainland China? If you can use it, please tell me how to operate a new server in Tokyo, Japan.
3 Replies
rdaniels
Linode Staff
@yeyuechuan I'm sorry to hear that you are having trouble accessing your Tokyo server. However, glad to hear that your US server's IP is currently accessible for you! Just to clarify, a few months ago, our Tokyo 1 datacenter was decommissioned. Linodes were migrated to our Tokyo 2 datacenter around that time.
Running some mtrs may better help you understand where the the connection loss is occurring. You can also use ping.pe to check connection from different parts of the world. It is also worth mentioning that your Linode's IP address may be blocked by the GFW. We have an excellent post here that can provide you with some next steps. These options do require more work, but they may help you work around the firewall. Good Luck!
Display IP is not available.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| No response from host - 100 | 55 | 0 | 0 | 0 | 0 | 0 |
| 117.3.175.61.dial.nb.zj.dynamic.163data.com.cn - 0 | 280 | 280 | 1 | 3 | 23 | 4 |
| 61.153.114.29 - 0 | 280 | 280 | 4 | 8 | 22 | 7 |
| 202.97.82.5 - 0 | 280 | 280 | 6 | 8 | 26 | 7 |
| 202.97.50.162 - 1 | 276 | 275 | 6 | 17 | 32 | 6 |
| 202.97.90.33 - 1 | 272 | 270 | 9 | 24 | 40 | 17 |
| 202.97.51.62 - 53 | 89 | 42 | 0 | 221 | 270 | 215 |
| ae-0.r30.tokyjp05.jp.bb.gin.ntt.net - 54 | 88 | 41 | 188 | 213 | 237 | 208 |
| ae-2.r01.tokyjp08.jp.bb.gin.ntt.net - 22 | 152 | 120 | 207 | 225 | 239 | 217 |
| 192.80.17.178 - 55 | 88 | 40 | 0 | 207 | 221 | 196 |
| 139.162.64.31 - 47 | 96 | 51 | 199 | 217 | 237 | 199 |
| No response from host - 100 | 55 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 55 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 55 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 55 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 55 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 55 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 55 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 55 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 55 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 55 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 55 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 55 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 55 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 55 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 55 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 55 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 55 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 55 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 55 | 0 | 0 | 0 | 0 | 0 |
| ____________________________________ | __ | __ | __ | __ | __ | __ |
| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider |
watrick
Linode Staff
Thanks for posting this MTR output.
Based on this output, the biggest packet loss occurs at 202.97.51.62. Looking up that IP, it belongs to Chinanet:
$ whois 202.97.51.62 | grep descr
descr: CHINANET backbone network
descr: Data Communication Division
descr: China Telecom
This would support the suggestion that Regina was mentioning, about your access to the Linode being affected by the GFW. I would recommend reviewing the suggestions made in this Community post for possible work arounds.