| Japan |
184.28.95.4 Osaka, Japan [Other] |
0ms |
56 |
View DNS HTTP Route |
| Singapore |
23.207.192.199 Singapore [Other] |
0ms |
57 |
View DNS HTTP Route |
| Hong Kong, China |
23.195.108.166 Hong Kong, China [Other] |
1ms |
57 |
View DNS HTTP Route |
| Hong Kong, China |
23.195.108.166 Hong Kong, China [Other] |
1ms |
57 |
View DNS HTTP Route |
| Hong Kong, China |
23.195.108.166 Hong Kong, China [Other] |
1ms |
58 |
View DNS HTTP Route |
| South Korea |
23.35.220.218 Seoul, South Korea [Other] |
1ms |
51 |
View DNS HTTP Route |
| San Jose, USA |
23.221.76.205 San Francisco, California, USA [Other] |
1ms |
56 |
View DNS HTTP Route |
| Hong Kong, China |
23.195.108.166 Hong Kong, China [Other] |
1ms |
58 |
View DNS HTTP Route |
| Hong Kong, China |
23.195.108.166 Hong Kong, China [Other] |
2ms |
58 |
View DNS HTTP Route |
| Seoul, South Korea |
23.35.220.218 Seoul, South Korea [Other] |
2ms |
51 |
View DNS HTTP Route |
| South Korea |
23.35.220.218 Seoul, South Korea [Other] |
2ms |
50 |
View DNS HTTP Route |
| Hong Kong, China |
23.195.108.166 Hong Kong, China [Other] |
2ms |
58 |
View DNS HTTP Route |
| Hong Kong, China |
23.195.108.166 Hong Kong, China [Other] |
2ms |
54 |
View DNS HTTP Route |
| Hong Kong, China |
23.195.108.166 Hong Kong, China [Other] |
2ms |
58 |
View DNS HTTP Route |
| Hong Kong, China |
23.195.108.166 Hong Kong, China [Other] |
2ms |
58 |
View DNS HTTP Route |
| Hong Kong, China |
23.195.108.166 Hong Kong, China [Other] |
4ms |
52 |
View DNS HTTP Route |
| Hong Kong, China |
23.195.108.166 Hong Kong, China [Other] |
4ms |
52 |
View DNS HTTP Route |
| Wuhan, Hubei [China Telecom] |
23.217.68.232 Tokyo, Japan [Other] |
45ms |
51 |
View DNS HTTP Route |
| Japan |
23.195.108.166 Hong Kong, China [Other] |
46ms |
52 |
View DNS HTTP Route |
| Ningbo, Zhejiang [China Mobile] |
23.195.108.166 Hong Kong, China [Other] |
49ms |
45 |
View DNS HTTP Route |
| Danjiangkou, Hubei [China Telecom] |
23.219.68.153 Tokyo, Japan [Other] |
50ms |
49 |
View DNS HTTP Route |
| Zhenjiang, Jiangsu [China Telecom] |
23.217.68.232 Tokyo, Japan [Other] |
52ms |
51 |
View DNS HTTP Route |
| Beijing [China Telecom] |
23.217.68.232 Tokyo, Japan [Other] |
52ms |
52 |
View DNS HTTP Route |
| Ningbo, Zhejiang [China Telecom] |
23.217.68.232 Tokyo, Japan [Other] |
53ms |
49 |
View DNS HTTP Route |
| Shijiazhuang, Hebei [China Telecom] |
23.217.68.232 Tokyo, Japan [Other] |
53ms |
51 |
View DNS HTTP Route |
| Ningbo, Zhejiang [China Telecom] |
23.217.68.232 Tokyo, Japan [Other] |
55ms |
46 |
View DNS HTTP Route |
| Nanning, Guangxi [China Telecom] |
23.217.68.232 Tokyo, Japan [Other] |
58ms |
51 |
View DNS HTTP Route |
| Wuhan, Hubei [China Telecom] |
23.219.68.153 Tokyo, Japan [Other] |
58ms |
51 |
View DNS HTTP Route |
| Hohhot, Inner Mongolia [China Telecom] |
23.217.68.232 Tokyo, Japan [Other] |
58ms |
50 |
View DNS HTTP Route |
| Changsha, Hunan [China Mobile] |
184.51.96.232 Singapore [Other] |
60ms |
50 |
View DNS HTTP Route |
| Shantou, Guangdong [China Telecom] |
23.217.68.232 Tokyo, Japan [Other] |
62ms |
52 |
View DNS HTTP Route |
| Xiamen, Fujian [China Telecom] |
23.217.68.232 Tokyo, Japan [Other] |
63ms |
46 |
View DNS HTTP Route |
| Xiangyang, Hubei [China Telecom] |
23.217.68.232 Tokyo, Japan [Other] |
65ms |
49 |
View DNS HTTP Route |
| Shiyan, Hubei [China Telecom] |
23.219.68.153 Tokyo, Japan [Other] |
65ms |
47 |
View DNS HTTP Route |
| Xiamen, Fujian [China Telecom] |
23.217.68.232 Tokyo, Japan [Other] |
66ms |
46 |
View DNS HTTP Route |
| Xi’an, Shaanxi [China Telecom] |
23.217.68.232 Tokyo, Japan [Other] |
66ms |
50 |
View DNS HTTP Route |
| Xi’an, Shaanxi [China Telecom] |
23.217.68.232 Tokyo, Japan [Other] |
66ms |
52 |
View DNS HTTP Route |
| Shiyan, Hubei [China Telecom] |
23.217.68.232 Tokyo, Japan [Other] |
66ms |
50 |
View DNS HTTP Route |
| Shiyan, Hubei [Multi-ISP] |
23.219.68.153 Tokyo, Japan [Other] |
67ms |
50 |
View DNS HTTP Route |
| Shiyan, Hubei [China Telecom] |
23.219.68.153 Tokyo, Japan [Other] |
68ms |
50 |
View DNS HTTP Route |
| Xi’an, Shaanxi [China Telecom] |
23.217.68.232 Tokyo, Japan [Other] |
68ms |
50 |
View DNS HTTP Route |
| Los Angeles, USA |
104.76.100.114 Secaucus, New Jersey, USA [Other] |
68ms |
51 |
View DNS HTTP Route |
| Kunming, Yunnan [China Telecom] |
23.217.68.232 Tokyo, Japan [Other] |
69ms |
54 |
View DNS HTTP Route |
| Kunming, Yunnan [China Telecom] |
23.217.68.232 Tokyo, Japan [Other] |
69ms |
53 |
View DNS HTTP Route |
| Shiyan, Hubei [China Mobile] |
23.55.208.234 Tokyo, Japan [Other] |
71ms |
47 |
View DNS HTTP Route |
| Hohhot, Inner Mongolia [China Telecom] |
23.217.68.232 Tokyo, Japan [Other] |
72ms |
52 |
View DNS HTTP Route |
| Kunming, Yunnan [China Telecom] |
23.217.68.232 Tokyo, Japan [Other] |
72ms |
49 |
View DNS HTTP Route |
| Luoyang, Henan [Multi-ISP] |
23.217.68.232 Tokyo, Japan [Other] |
73ms |
51 |
View DNS HTTP Route |
| Xining, Qinghai [China Telecom] |
23.217.68.232 Tokyo, Japan [Other] |
76ms |
48 |
View DNS HTTP Route |
| Hohhot, Inner Mongolia [China Telecom] |
23.217.68.232 Tokyo, Japan [Other] |
77ms |
52 |
View DNS HTTP Route |
| Wuhan, Hubei [China Telecom] |
23.215.160.192 Tokyo, Japan [Other] |
77ms |
51 |
View DNS HTTP Route |
| Chongqing [China Telecom] |
23.217.68.232 Tokyo, Japan [Other] |
77ms |
51 |
View DNS HTTP Route |
| Shiyan, Hubei [China Telecom] |
23.217.68.232 Tokyo, Japan [Other] |
80ms |
47 |
View DNS HTTP Route |
| Xiangyang, Hubei [China Telecom] |
23.217.68.232 Tokyo, Japan [Other] |
81ms |
48 |
View DNS HTTP Route |
| Xiangyang, Hubei [China Telecom] |
23.219.68.153 Tokyo, Japan [Other] |
82ms |
47 |
View DNS HTTP Route |
| Shiyan, Hubei [China Telecom] |
23.219.68.153 Tokyo, Japan [Other] |
82ms |
51 |
View DNS HTTP Route |
| Shiyan, Hubei [China Telecom] |
23.217.68.232 Tokyo, Japan [Other] |
83ms |
48 |
View DNS HTTP Route |
| Meishan, Sichuan [China Unicom] |
23.215.160.192 Tokyo, Japan [Other] |
85ms |
49 |
View DNS HTTP Route |
| Shiyan, Hubei [China Telecom] |
23.219.68.153 Tokyo, Japan [Other] |
85ms |
50 |
View DNS HTTP Route |
| Jinan, Shandong [China Mobile] |
23.36.16.189 Tokyo, Japan [Other] |
88ms |
39 |
View DNS HTTP Route |
| Dalian, Liaoning [China Telecom] |
23.207.192.199 Singapore [Other] |
93ms |
48 |
View DNS HTTP Route |
| Hong Kong, China |
184.27.28.232 Kuala Lumpur, Malaysia [Other] |
98ms |
52 |
View DNS HTTP Route |
| Urumqi, Xinjiang [China Telecom] |
23.217.68.232 Tokyo, Japan [Other] |
101ms |
51 |
View DNS HTTP Route |
| Lhasa, Tibet [China Telecom] |
23.217.68.232 Tokyo, Japan [Other] |
102ms |
49 |
View DNS HTTP Route |
| Jinan, Shandong [China Mobile] |
23.48.116.185 Tokyo, Japan [Other] |
117ms |
39 |
View DNS HTTP Route |
| Shanghai [China Telecom] |
184.27.32.169 Osaka, Japan [Other] |
122ms |
49 |
View DNS HTTP Route |
| Chengdu, Sichuan [China Mobile] |
104.121.228.221 Bangalore, India [Other] |
124ms |
43 |
View DNS HTTP Route |
| Tibet [China Mobile] |
23.49.8.227 Singapore [Other] |
129ms |
45 |
View DNS HTTP Route |
| Chengdu, Sichuan [China Mobile] |
104.121.228.221 Bangalore, India [Other] |
134ms |
44 |
View DNS HTTP Route |
| Nanjing, Jiangsu [China Telecom] |
104.85.244.95 Los Angeles, California, USA [Other] |
158ms |
50 |
View DNS HTTP Route |
| Urumqi, Xinjiang [China Mobile] |
23.2.76.228 San Jose, California, USA [Other] |
159ms |
47 |
View DNS HTTP Route |
| Hong Kong, China |
184.27.28.232 Kuala Lumpur, Malaysia [Other] |
159ms |
52 |
View DNS HTTP Route |
| Shanghai [Multi-ISP] |
23.38.160.223 Los Angeles, California, USA [Other] |
165ms |
49 |
View DNS HTTP Route |
| Jinan, Shandong [China Unicom] |
2.20.168.228 Istanbul, Turkey [Other] |
184ms |
41 |
View DNS HTTP Route |
| Chengdu, Sichuan [China Mobile] |
184.31.253.4 Sydney, New South Wales, Australia [Other] |
185ms |
39 |
View DNS HTTP Route |
| Jiujiang, Jiangxi [China Telecom] |
104.85.244.95 Los Angeles, California, USA [Other] |
186ms |
52 |
View DNS HTTP Route |
| Hong Kong, China |
104.85.244.95 Los Angeles, California, USA [Other] |
191ms |
51 |
View DNS HTTP Route |
| Zhongwei, Ningxia [China Telecom] |
23.38.160.223 Los Angeles, California, USA [Other] |
192ms |
51 |
View DNS HTTP Route |
| Maanshan, Anhui [China Telecom] |
23.208.8.76 El Segundo, California, USA [Other] |
196ms |
46 |
View DNS HTTP Route |
| Lanzhou, Gansu [China Unicom] |
23.212.168.75 Auckland, New Zealand [Other] |
199ms |
46 |
View DNS HTTP Route |
| Shanghai [China Telecom] |
23.38.160.223 Los Angeles, California, USA [Other] |
199ms |
50 |
View DNS HTTP Route |
| Zhengzhou, Henan [China Telecom] |
23.41.100.206 Los Angeles, California, USA [Other] |
202ms |
46 |
View DNS HTTP Route |
| Ningbo, Zhejiang [China Unicom] |
23.209.216.233 Taipei, China [Other] |
219ms |
47 |
View DNS HTTP Route |
| Quanzhou, Fujian [China Telecom] |
23.217.76.233 USA [Other] |
221ms |
46 |
View DNS HTTP Route |
| Shijiazhuang, Hebei [China Unicom] |
2.19.244.88 Düsseldorf, North Rhine-Westphalia, Germany [Other] |
227ms |
52 |
View DNS HTTP Route |
| Gui’an, Guizhou [China Telecom] |
23.212.168.75 Auckland, New Zealand [Other] |
230ms |
50 |
View DNS HTTP Route |
| Changchun, Jilin [China Telecom] |
23.38.72.230 Hamburg |
|
|
|