Estamos muy contentos de anunciar la apertura de nuestro nuevo centro de datos en Singapur. Este es el séptimo centro de datos de Linode, y ha sido construido para servir a los ya enormes y crecientes mercados del sudeste asiático, la India, Australia y las regiones circundantes.
Hemos pasado la mayor parte de los últimos meses trabajando para conseguir una gran conectividad a Internet. Nuestra red de Singapur cuenta con routers Cisco ASR de la serie 9000, y actualmente combina el tránsito de Telstra/Pacnet y PCCW, junto con el peering directo en el Equinix Internet Exchange (EIE), lo que nos proporciona acceso a cientos de oportunidades de peering. Consulte nuestra página de pruebas de velocidad para comprobar la latencia y las velocidades de descarga.
Singapur es compatible con todas las características estándar de Linode disponibles en todos nuestros centros de datos - como la conectividad redundante de 40 Gbps a cada máquina anfitriona de hipervisor, el servicio de copia de seguridad Linode , NodeBalancers, IPv6 nativo, etc - y tiene el mismo precio sencillo que nuestros otros centros de datos. Pruebe Singapur ahora!
También estamos trabajando en otras grandes noticias. Manténgase en contacto con nosotros.
Que lo disfrutes.
Comentarios (67)
Finally! Can’t wait to try. Great job guys.
It`s good jobs,I set 4G for my jobs.
Link to China is too slow…
正在 Ping speedtest.singapore.linode.com [139.162.23.4] 具有 32 字节的数据
请求超时。
请求超时。
来自 139.162.23.4 的回复: 字节=32 时间=484ms TTL=51
来自 139.162.23.4 的回复: 字节=32 时间=490ms TTL=51
请求超时。
来自 139.162.23.4 的回复: 字节=32 时间=476ms TTL=51
来自 139.162.23.4 的回复: 字节=32 时间=484ms TTL=51
来自 139.162.23.4 的回复: 字节=32 时间=483ms TTL=51
来自 139.162.23.4 的回复: 字节=32 时间=483ms TTL=51
great, i love linode
@Jerry, ping from Vietnam is very fast
ping 139.162.9.10
Pinging 139.162.9.10 with 32 bytes of data:
Reply from 139.162.9.10: bytes=32 time=78ms TTL=49
Reply from 139.162.9.10: bytes=32 time=68ms TTL=49
Reply from 139.162.9.10: bytes=32 time=72ms TTL=49
Reply from 139.162.9.10: bytes=32 time=63ms TTL=49
Ping statistics for 139.162.9.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 78ms, Average = 70ms
No direct peer to China Telecom and China Unicom, same as DigitalOcean.
However at this pricing level, it is impossible to get 2TB/mo in SG if linked to CT and CU…
Chinese users might still consider Tokyo instead.
I have tracert ,some time run as-2.r22.tokyjp01.jp.bb.gin.ntt.net,some time run as-0.r22.tkokhk01.hk.bb.gin.ntt.net. run hk r batter.
Thank you Linode 🙂
PING speedtest.singapore.linode.com (139.162.23.4) 56(84) bytes of data.
64 bytes from li865-4.members.linode.com (139.162.23.4): icmp_seq=1 ttl=56 time=38.5 ms
64 bytes from li865-4.members.linode.com (139.162.23.4): icmp_seq=2 ttl=56 time=38.2 ms
64 bytes from li865-4.members.linode.com (139.162.23.4): icmp_seq=3 ttl=56 time=37.9 ms
64 bytes from li865-4.members.linode.com (139.162.23.4): icmp_seq=4 ttl=56 time=38.2 ms
From Hong Kong~ 🙂
Awesome ! Will you launch new promotion to celebrate this event 😀
From Chennai, India: 🙂
Pinging speedtest.singapore.linode.com [139.162.23.4] with 32 bytes of data:
Reply from 139.162.23.4: bytes=32 time=34ms TTL=52
Reply from 139.162.23.4: bytes=32 time=34ms TTL=52
Reply from 139.162.23.4: bytes=32 time=34ms TTL=52
Reply from 139.162.23.4: bytes=32 time=34ms TTL=52
When one could expect Frankfurt launch? It’s comming a bit late for ‘next few months’ mentioned in January 15th post.. Cheers for Singapore!
Hi,
route from Taiwan to SG:
Taiwan -> HK -> Japan -> SG ?
1 1 ms 1 ms 1 ms 192.168.10.10
2 13 ms 12 ms 13 ms h254.s98.ts.hinet.net [168.95.98.254]
3 14 ms 12 ms 12 ms tpe4-3302.hinet.net [168.95.25.46]
4 15 ms 13 ms 15 ms 220-128-11-246.HINET-IP.hinet.net [220.128.11.246]
5 16 ms 14 ms 19 ms TPDT-3011.hinet.net [220.128.3.22]
6 15 ms 14 ms 13 ms r4044-s2.tp.hinet.net [220.128.1.182]
7 42 ms 35 ms 37 ms r11-hk.hinet.net [220.128.3.13]
8 80 ms 82 ms 82 ms jt-jp-gw.hinet.net [211.22.33.53]
9 104 ms 104 ms 123 ms xe-0-1-1.gw1.sin2.pacnet.net [202.147.52.64]
10 104 ms 104 ms 105 ms gw2.sin1.sg.linode.com [61.14.147.179]
11 104 ms 104 ms 106 ms li842-6.members.linode.com [139.162.0.6]
12 105 ms 112 ms 104 ms speedtest.singapore.linode.com [139.162.23.4]
[…] https://www.linode.com/2015/04/27/hello-singapore/ […]
Whooo hooo thanks guys you’re the best!!!
Ping from China with China telecom 100M, looks good!
ping speedtest.singapore.linode.com
PING speedtest.singapore.linode.com (139.162.23.4) 56(84) bytes of data.
64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_req=1 ttl=48 time=256 ms
64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_req=2 ttl=48 time=255 ms
64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_req=3 ttl=48 time=255 ms
64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_req=4 ttl=48 time=255 ms
64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_req=5 ttl=48 time=255 ms
64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_req=6 ttl=48 time=255 ms
good job!i love linode!
from china guangdong
PING 139.162.23.4 (139.162.23.4): 56 data bytes
64 bytes from 139.162.23.4: icmp_seq=0 ttl=47 time=236.369 ms
64 bytes from 139.162.23.4: icmp_seq=1 ttl=47 time=237.414 ms
64 bytes from 139.162.23.4: icmp_seq=2 ttl=47 time=234.328 ms
64 bytes from 139.162.23.4: icmp_seq=3 ttl=47 time=237.832 ms
64 bytes from 139.162.23.4: icmp_seq=4 ttl=47 time=234.156 ms
64 bytes from 139.162.23.4: icmp_seq=5 ttl=47 time=235.866 ms
64 bytes from 139.162.23.4: icmp_seq=6 ttl=47 time=236.943 ms
^C
— 139.162.23.4 ping statistics —
7 packets transmitted, 7 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 234.156/236.130/237.832/1.335 ms
Not so good for Australia …
PING speedtest.singapore.linode.com (139.162.23.4) 56(84) bytes of data.
64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_seq=1 ttl=55 time=300 ms
64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_seq=2 ttl=55 time=300 ms
64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_seq=3 ttl=55 time=299 ms
64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_seq=4 ttl=55 time=299 ms
64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_seq=5 ttl=55 time=299 ms
Thank you. would wait for couple of week before moving to AsiaPacific.
[…] Linode 宣佈新加坡機房開放：「Singapore Linodes are now available!」。 […]
I have purchased Singapore,Can U test speed~
In Taiwan is faster,From ISP CHT.
domain http://www.wr.com.tw/
C:\Users\>ping 139.162.23.4
Pinging 139.162.23.4 with 32 bytes of data:
Reply from 139.162.23.4: bytes=32 time=121ms TTL=50
Reply from 139.162.23.4: bytes=32 time=130ms TTL=50
Reply from 139.162.23.4: bytes=32 time=132ms TTL=50
Reply from 139.162.23.4: bytes=32 time=133ms TTL=50
Ping statistics for 139.162.23.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 121ms, Maximum = 133ms, Average = 129ms
From Malaysia, pretty good:
Pinging speedtest.singapore.linode.com [139.162.23.4] with 32 bytes of data:
Reply from 139.162.23.4: bytes=32 time=16ms TTL=58
Reply from 139.162.23.4: bytes=32 time=14ms TTL=58
Reply from 139.162.23.4: bytes=32 time=15ms TTL=58
Reply from 139.162.23.4: bytes=32 time=13ms TTL=58
Ping statistics for 139.162.23.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 16ms, Average = 14ms
Quick question: Can we expect the opening of the Linode datacenter in Frankfurt in the next weeks as well?
Congrats! Our Asian users will love it!
@ShaolinTiger, what ISP are you using?
Via Telekom Malaysia, I’m getting 350+ms
mtr output:
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. 192.168.1.1 0.0% 259 0.2 0.2 0.2 0.3 0.0
2. 60.52.73.138 0.0% 259 7.8 20.8 6.5 94.3 17.6
60.52.73.150
3. 60.52.73.149 0.0% 258 5.5 8.1 5.1 80.3 10.0
4. 10.55.208.58 0.0% 258 12.7 14.8 12.2 55.0 5.7
10.55.208.108
10.55.208.75
5. 203.192.169.25 3.1% 258 4751. 400.7 300.8 4751. 380.5
6. 61.14.157.164 1.2% 258 4651. 402.1 304.2 4651. 367.6
7. 202.147.52.66 2.3% 258 338.7 383.9 297.8 4288. 247.9
8. 61.14.147.177 1.2% 258 328.7 381.6 290.1 4187. 240.2
9. [redacted] 2.3% 258 323.4 366.5 293.5 390.7 21.5
10. [redacted] 3.1% 258 349.8 366.7 292.0 393.9 21.8
Unfortunately whoever did their homework on this one failed. Choosing this location from Australia (Mel, Syd, SA and Bris) typical traceroute latency is approx 270ms.
Latency to West Coast USA (LA) from Australia is typically 190ms.
Fantastic – back on April 23rd I was getting ~ 250ms pings to speedtest.singapore.linode.com via Telstra in brisbane, but now I am getting a pretty consistent 140ms – nice work!
time=150ms ttl=48
tracert
china heilongjiang
wr1.hkg0.asianetcom.net
wr1.sin0.asianetcom.net
gw1.sin2.pacnet.net
139.162.0.1
linode
Not bad from Indonesia :p
Pinging 139.162.23.4 with 32 bytes of data:
Reply from 139.162.23.4: bytes=32 time=32ms TTL=56
Reply from 139.162.23.4: bytes=32 time=32ms TTL=56
Reply from 139.162.23.4: bytes=32 time=31ms TTL=56
Reply from 139.162.23.4: bytes=32 time=31ms TTL=56
Ping statistics for 139.162.23.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 32ms, Average = 31ms
Pinging speedtest.singapore.linode.com [139.162.23.4] with 32 bytes of data:
Reply from 139.162.23.4: bytes=32 time=101ms TTL=54
Reply from 139.162.23.4: bytes=32 time=101ms TTL=54
Reply from 139.162.23.4: bytes=32 time=100ms TTL=54
Reply from 139.162.23.4: bytes=32 time=101ms TTL=54
Ping statistics for 139.162.23.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 100ms, Maximum = 101ms, Average = 100ms
Not bad. Test it from Taiwan.
Seems Telstra is not using the SMW3 cable for Linode, 190ms ping from Telstra Cable, Where DO Singapore datacenter is 90ms.
Comparing from Hong Kong. SINGAPORE around half the latency of TOKYO from HK on residential PCCW/Netvigator connection.
PING 139.162.23.4 (139.162.23.4): 56 data bytes
64 bytes from 139.162.23.4: icmp_seq=0 ttl=56 time=48.940 ms
64 bytes from 139.162.23.4: icmp_seq=1 ttl=56 time=46.373 ms
64 bytes from 139.162.23.4: icmp_seq=2 ttl=56 time=48.951 ms
64 bytes from 139.162.23.4: icmp_seq=3 ttl=56 time=46.318 ms
64 bytes from 139.162.23.4: icmp_seq=4 ttl=56 time=46.620 ms
64 bytes from 139.162.23.4: icmp_seq=5 ttl=56 time=46.761 ms
64 bytes from 139.162.23.4: icmp_seq=6 ttl=56 time=47.018 ms
From same connection to TOKYO datacentre
PING speedtest.tokyo.linode.com (106.187.96.148): 56 data bytes
64 bytes from 106.187.96.148: icmp_seq=0 ttl=54 time=99.122 ms
64 bytes from 106.187.96.148: icmp_seq=1 ttl=54 time=84.868 ms
64 bytes from 106.187.96.148: icmp_seq=2 ttl=54 time=85.451 ms
64 bytes from 106.187.96.148: icmp_seq=3 ttl=54 time=99.531 ms
64 bytes from 106.187.96.148: icmp_seq=4 ttl=54 time=100.383 ms
From in Japan to Tokyo 10ms. From Japan to Singapore 90ms. Expand Tokyo please or try to relocate some of the accounts that do not need the Tokyo DC to Singapore.
Finally! Signup now 🙂
ping from Middle East to Singapore (expected better)
Pinging speedtest.singapore.linode.com [139.162.23.4] with 32 bytes of data:
Reply from 139.162.23.4: bytes=32 time=349ms TTL=47
Reply from 139.162.23.4: bytes=32 time=351ms TTL=47
Reply from 139.162.23.4: bytes=32 time=349ms TTL=47
Reply from 139.162.23.4: bytes=32 time=352ms TTL=47
ping from Middle East to East ‘Murica
Pinging speedtest.newark.linode.com [50.116.57.237] with 32 bytes of data:
Reply from 50.116.57.237: bytes=32 time=305ms TTL=40
Reply from 50.116.57.237: bytes=32 time=302ms TTL=40
Reply from 50.116.57.237: bytes=32 time=302ms TTL=40
Reply from 50.116.57.237: bytes=32 time=302ms TTL=40
ping from Middle East to FOLK!
Pinging speedtest.fremont.linode.com [50.116.14.9] with 32 bytes of data:
Reply from 50.116.14.9: bytes=32 time=338ms TTL=43
Reply from 50.116.14.9: bytes=32 time=336ms TTL=43
Reply from 50.116.14.9: bytes=32 time=348ms TTL=43
Reply from 50.116.14.9: bytes=32 time=336ms TTL=43
ping from Middle East to UK
Pinging speedtest.london.linode.com [176.58.107.39] with 32 bytes of data:
Reply from 176.58.107.39: bytes=32 time=239ms TTL=45
Reply from 176.58.107.39: bytes=32 time=234ms TTL=45
Reply from 176.58.107.39: bytes=32 time=225ms TTL=45
Reply from 176.58.107.39: bytes=32 time=233ms TTL=45
Traceroute from my phone in HK
1. 10.11.105.174
2. 10.11.200.97
3. 10.11.200.84
4. 10.11.99.18
5. 63.218.56.181 63-218-56-181.static.pccwglobal.net
6. 63.218.228.94 TenGE0-0-0-0.br03.sin02.pccwbtn.net
7. 63.217.59.62 linode.te0-1-0-21.br03.sin02.pccwbtn.net
8. 139.162.0.2
9. 139.162.23.4 speedtest.singapore.linode.com
The speed is pretty good and is expected when using PCCW as your upstream. I see a latency of 35-38ms from Hong Kong using business lines of HGC. However, I noticed traceroute to Linode Singapore mainly goes through Pacnet which is considered congested inside Asia. I recommend tuning your routes to give a better experiences to your customers.
moving from tokyo to singapore
…tokyo is crowded cant even resize when needed
and singapore gives better ping to indian locations then tokyo:)
did few testes….
Pin Statistic from Hong Kong, Lantau, I use I-Cable.
Tokyo
>ping speedtest.tokyo.linode.com
Pinging speedtest.tokyo.linode.com [106.187.96.148] with 32 bytes of data:
Reply from 106.187.96.148: bytes=32 time=68ms TTL=50
Reply from 106.187.96.148: bytes=32 time=70ms TTL=50
Reply from 106.187.96.148: bytes=32 time=76ms TTL=50
Reply from 106.187.96.148: bytes=32 time=70ms TTL=50
Ping statistics for 106.187.96.148:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 68ms, Maximum = 76ms, Average = 71ms
Singapore
C:\Users\Hp>ping speedtest.singapore.linode.com
Pinging speedtest.singapore.linode.com [139.162.23.4] with 32 bytes of data:
Reply from 139.162.23.4: bytes=32 time=50ms TTL=49
Reply from 139.162.23.4: bytes=32 time=49ms TTL=49
Reply from 139.162.23.4: bytes=32 time=47ms TTL=49
Reply from 139.162.23.4: bytes=32 time=43ms TTL=49
Ping statistics for 139.162.23.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 50ms, Average = 47ms
Traceroute to Singapore
tracert speedtest.singapore.linode.com
Tracing route to speedtest.singapore.linode.com [139.162.23.4]
over a maximum of 30 hops:
1 1 ms 1 ms 2 ms XiaoQiang [192.168.31.1]
2 7 ms 10 ms 13 ms 10.91.64.1
3 11 ms 14 ms 8 ms 192.168.113.61
4 12 ms 9 ms 13 ms 192.168.66.89
5 10 ms 14 ms 14 ms 192.168.67.185
6 13 ms 13 ms 14 ms 192.168.64.101
7 14 ms 11 ms 12 ms cm61-10-0-245.hkcable.com.hk [61.10.0.245]
8 15 ms 15 ms 17 ms ix-10-3-1-0.tcore1.HK2-Hong-Kong.as6453.net [180
.87.112.85]
9 12 ms 14 ms 11 ms 180.87.112.94
10 48 ms 48 ms 50 ms TenGE0-0-0-0.br03.sin02.pccwbtn.net [63.218.228.
94]
11 47 ms 48 ms 47 ms linode.te0-1-0-21.br03.sin02.pccwbtn.net [63.217
.59.62]
12 49 ms 45 ms 50 ms 139.162.0.2
13 45 ms 49 ms 49 ms speedtest.singapore.linode.com [139.162.23.4]
Trace complete.
Traceroute to Tokyo
>trecert speedtest.tokyo.linode.com
Tracing route to speedtest.tokyo.linode.com [106.187.96.148]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms XiaoQiang [192.168.31.1]
2 19 ms 29 ms 10 ms 10.91.64.1
3 12 ms 11 ms 12 ms 192.168.113.61
4 11 ms 13 ms 10 ms 192.168.66.89
5 15 ms 13 ms 13 ms 192.168.67.185
6 13 ms 26 ms 32 ms 192.168.64.101
7 13 ms 15 ms 12 ms cm61-10-0-245.hkcable.com.hk [61.10.0.245]
8 11 ms 13 ms 10 ms ix-10-3-1-0.tcore1.HK2-Hong-Kong.as6453.net [180
.87.112.85]
9 28 ms 14 ms 23 ms 180.87.112.162
10 17 ms 14 ms 15 ms hkmjbb002.int-gw.kddi.ne.jp [111.87.5.21]
11 68 ms 69 ms 89 ms obpjbb206.int-gw.kddi.ne.jp [118.155.199.197]
12 66 ms 65 ms 70 ms otejbb206.int-gw.kddi.ne.jp [59.128.4.249]
13 85 ms 70 ms 70 ms cm-fcu204.kddnet.ad.jp [124.215.194.165]
14 71 ms 69 ms 68 ms 124.215.199.126
15 70 ms 69 ms 71 ms speedtest.tokyo.linode.com [106.187.96.148]
Trace complete.
Multiple test shows the same stuff.
As a result, I will move my stuff to Singapore.
$ ping speedtest.singapore.linode.com
PING speedtest.singapore.linode.com (139.162.23.4): 56 data bytes
64 bytes from 139.162.23.4: icmp_seq=0 ttl=47 time=322.174 ms
64 bytes from 139.162.23.4: icmp_seq=1 ttl=47 time=344.201 ms
64 bytes from 139.162.23.4: icmp_seq=2 ttl=47 time=364.725 ms
64 bytes from 139.162.23.4: icmp_seq=3 ttl=47 time=384.182 ms
64 bytes from 139.162.23.4: icmp_seq=4 ttl=47 time=300.344 ms
very bad from Beijing, China via China Telecom
Couple of mtr runs from Brisbane, Australia. Hell of a lot quicker using Tokyo.
From Exetel ISP. Similar results to this from Internode.
[# mtr -r speedtest.singapore.linode.com
Start: Wed Jun 3 02:42:15 2015
HOST: xxxxx Loss% Snt Last Avg Best Wrst StDev
1.|– 192.168.100.254 0.0% 10 0.3 0.2 0.2 0.3 0.0
2.|– 1.155.70.115.static.exete 0.0% 10 0.9 0.9 0.7 1.1 0.0
3.|– 232.220.233.220.static.ex 0.0% 10 2.3 2.2 2.2 2.3 0.0
4.|– 161.3.96.58.static.exetel 0.0% 10 2.3 2.3 2.2 2.4 0.0
5.|– 119.225.26.177 0.0% 10 2.7 2.6 2.6 2.7 0.0
6.|– ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|– ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
8.|– 59.154.18.6 0.0% 10 14.2 14.4 14.1 15.4 0.3
9.|– 203.208.174.49 0.0% 10 172.5 195.1 171.1 337.7 51.7
10.|– 203.208.171.13 0.0% 10 339.0 192.2 171.1 339.0 52.3
11.|– 203.208.166.245 0.0% 10 337.2 318.3 178.2 344.2 49.4
12.|– 203.208.172.1 0.0% 10 319.8 329.7 312.2 348.1 11.2
13.|– 203.208.158.74 10.0% 10 354.8 336.9 312.6 354.9 17.1
14.|– 203.208.173.181 10.0% 10 347.9 308.6 267.2 347.9 37.4
15.|– 203.208.178.5 10.0% 10 339.5 306.5 267.4 340.1 37.0
16.|– 139.162.0.2 10.0% 10 283.4 300.4 269.3 365.1 39.4
17.|– speedtest.singapore.linod 10.0% 10 283.6 277.3 264.4 283.6 6.0
# mtr -r speedtest.tokyo.linode.com
Start: Wed Jun 3 02:42:48 2015
HOST: xxxxx Loss% Snt Last Avg Best Wrst StDev
1.|– 192.168.100.254 0.0% 10 0.2 0.3 0.2 0.4 0.0
2.|– 1.155.70.115.static.exete 0.0% 10 0.8 0.8 0.7 1.0 0.0
3.|– 232.220.233.220.static.ex 0.0% 10 2.2 2.4 2.2 3.6 0.3
4.|– 177.3.96.58.static.exetel 0.0% 10 2.3 2.3 2.2 2.7 0.0
5.|– 119.225.26.177 0.0% 10 2.7 2.7 2.6 2.8 0.0
6.|– ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|– ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
8.|– 59.154.18.8 0.0% 10 14.2 14.3 14.2 14.4 0.0
9.|– ix-0-2-1-806.tcore1.TV2-T 0.0% 10 116.4 118.9 116.2 141.8 8.0
10.|– if-2-2.tcore2.TV2-Tokyo.a 0.0% 10 114.7 115.5 114.5 120.1 1.9
11.|– 116.0.90.66 0.0% 10 127.5 121.6 116.8 129.7 4.6
12.|– otejbb206.int-gw.kddi.ne. 0.0% 10 116.8 119.2 116.7 140.3 7.4
13.|– cm-fcu204.kddnet.ad.jp 0.0% 10 116.3 120.1 116.2 128.1 4.3
14.|– 124.215.199.126 0.0% 10 118.8 118.8 118.7 119.0 0.0
15.|– speedtest.tokyo.linode.co 10.0% 10 116.7 117.2 116.5 118.9 0.6
very well.
C:\Users\Administrator>ping speedtest.singapore.linode.com -t
正在 Ping speedtest.singapore.linode.com [139.162.23.4] 具有 32 字节的数据:
来自 139.162.23.4 的回复: 字节=32 时间=125ms TTL=47
来自 139.162.23.4 的回复: 字节=32 时间=125ms TTL=47
来自 139.162.23.4 的回复: 字节=32 时间=123ms TTL=47
来自 139.162.23.4 的回复: 字节=32 时间=124ms TTL=47
来自 139.162.23.4 的回复: 字节=32 时间=129ms TTL=47
来自 139.162.23.4 的回复: 字节=32 时间=132ms TTL=47
来自 139.162.23.4 的回复: 字节=32 时间=134ms TTL=47
来自 139.162.23.4 的回复: 字节=32 时间=129ms TTL=47
来自 139.162.23.4 的回复: 字节=32 时间=145ms TTL=47
来自 139.162.23.4 的回复: 字节=32 时间=132ms TTL=47
来自 139.162.23.4 的回复: 字节=32 时间=129ms TTL=47
来自 139.162.23.4 的回复: 字节=32 时间=136ms TTL=47
来自 139.162.23.4 的回复: 字节=32 时间=146ms TTL=47
139.162.23.4 的 Ping 统计信息:
数据包: 已发送 = 13，已接收 = 13，丢失 = 0 (0% 丢失)，
往返行程的估计时间(以毫秒为单位):
最短 = 123ms，最长 = 146ms，平均 = 131ms
now use japan, Singapore may be another good choice.
Great, i love it, we will connect from Vietnam faster. Thanks
My site hosted at singapore http://www.Webx99.com with other provider but I am not quite satisfied with them looks like linode is giving good speed in india as i can see in ping results.
From Malaysia via TM UniFi:
C:\Users\toor>ping -4 -n 5 speedtest.singapore.linode.com
Pinging speedtest.singapore.linode.com [139.162.23.4] with 32 bytes of data:
Reply from 139.162.23.4: bytes=32 time=10ms TTL=58
Reply from 139.162.23.4: bytes=32 time=10ms TTL=58
Reply from 139.162.23.4: bytes=32 time=12ms TTL=58
Reply from 139.162.23.4: bytes=32 time=10ms TTL=58
Reply from 139.162.23.4: bytes=32 time=11ms TTL=58
Ping statistics for 139.162.23.4:
Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 12ms, Average = 10ms
C:\Users\toor>ping -6 -n 5 speedtest.singapore.linode.com
Pinging speedtest.singapore.linode.com [2400:8901::4b] with 32 bytes of data:
Reply from 2400:8901::4b: time=12ms
Reply from 2400:8901::4b: time=11ms
Reply from 2400:8901::4b: time=9ms
Reply from 2400:8901::4b: time=11ms
Reply from 2400:8901::4b: time=13ms
Ping statistics for 2400:8901::4b:
Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 13ms, Average = 11ms
Not bad. Will consider signing up..
Ping from Mumbai, India. 67ms excellent. Definitely gonna try it…
ping speedtest.singapore.linode.com
PING speedtest.singapore.linode.com (139.162.23.4) 56(84) bytes of data.
64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_seq=1 ttl=50 time=64.2 ms
64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_seq=2 ttl=50 time=64.5 ms
64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_seq=4 ttl=50 time=70.5 ms
64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_seq=5 ttl=50 time=70.2 ms
64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_seq=6 ttl=50 time=63.0 ms
64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_seq=7 ttl=50 time=70.3 ms
64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_seq=8 ttl=50 time=59.9 ms
64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_seq=9 ttl=50 time=71.5 ms
64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_seq=10 ttl=50 time=70.9 ms
64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_seq=11 ttl=50 time=72.3 ms
64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_seq=12 ttl=50 time=70.5 ms
64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_seq=13 ttl=50 time=65.3 ms
64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_seq=14 ttl=50 time=64.3 ms
64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_seq=15 ttl=50 time=73.0 ms
^C
— speedtest.singapore.linode.com ping statistics —
15 packets transmitted, 14 received, 6% packet loss, time 14140ms
rtt min/avg/max/mdev = 59.932/67.928/73.057/4.033 ms
Pretty sad times from Sydney on a NBN connection:
PING speedtest.singapore.linode.com (139.162.23.4): 56 data bytes
64 bytes from 139.162.23.4: icmp_seq=0 ttl=55 time=487.714 ms
64 bytes from 139.162.23.4: icmp_seq=1 ttl=55 time=288.697 ms
64 bytes from 139.162.23.4: icmp_seq=2 ttl=55 time=316.294 ms
64 bytes from 139.162.23.4: icmp_seq=3 ttl=55 time=570.821 ms
64 bytes from 139.162.23.4: icmp_seq=4 ttl=55 time=458.410 ms
64 bytes from 139.162.23.4: icmp_seq=5 ttl=55 time=376.034 ms
64 bytes from 139.162.23.4: icmp_seq=6 ttl=55 time=601.354 ms
64 bytes from 139.162.23.4: icmp_seq=7 ttl=55 time=545.499 ms
64 bytes from 139.162.23.4: icmp_seq=8 ttl=55 time=443.493 ms
64 bytes from 139.162.23.4: icmp_seq=9 ttl=55 time=358.693 ms
— speedtest.singapore.linode.com ping statistics —
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 288.697/444.701/601.354/102.754 ms
Unfortunately, the RTT to a Singapore linode from Sydney via TPG (fluctuating between 300ms and 400ms with some packet loss) is worse than the RTT to a London linode from Sydney (consistent 320ms).
There’s also a fluctuating 60ms-160ms RTT between the Singapore linode and its default gateway.
Wow, Its Nice to hear, can’t want to move to my local datacenter.
Regards,
Raja.
Great job! You’re the best.
Well done. Still blocked regarding VMs bookings until D/Frankfurt location is missing. We love this service but cannot use yet.
Hi,
I would like to know which is better from India and China, Tokyo or Singapore?
Thanks in advance to anyone replying me.
We are going to give it a try with our website soon, hope to get the good response as been discussed here in the post.
Great Job indeed!
Please direct china telecom please use china telecom CN2 Network
@Garron
I recommend Singapore from India. Following from Kerala
PING speedtest.singapore.linode.com (139.162.23.4) 56(84) bytes of data.
64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_seq=1 ttl=55 time=74.5 ms
64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_seq=2 ttl=55 time=74.8 ms
64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_seq=3 ttl=55 time=74.2 ms
64 bytes from speedtest.singapore.linode.com (139.162.23.4): icmp_seq=4 ttl=55 time=73.8 ms
I also shifted my linode to Singapore datacenter. Thank you linode for starting Singapore datacenter
Hi, I am no expert, just a user and I love using Linode. But look at what I’ve found! You can’t really take the speedtest server at face value….
Besides ping, you have to use tracert to see at which nodes are slowing down your linode server in singapore to the internet.
Here’s what I do:
1. I shifted my linode to Singapore DC.
2. Using the one of fastest broadband subscriptions (500mbps) from singapore isp, i ping from my client machine in Singapore to Linode Singapore DC:
2.1 Pinging speedtest.singapore.linode.com [139.162.23.4] with 32 bytes of data:
Reply from 139.162.23.4: bytes=32 time=5ms TTL=51
Reply from 139.162.23.4: bytes=32 time=4ms TTL=51
Reply from 139.162.23.4: bytes=32 time=4ms TTL=51
Reply from 139.162.23.4: bytes=32 time=4ms TTL=51
2.2 Pinging li863-XX.members.linode.com [139.162.2X.XX] with 32 bytes of data:
Reply from 139.162.2X.XX: bytes=32 time=179ms TTL=46
Reply from 139.162.2X.XX: bytes=32 time=178ms TTL=46
Reply from 139.162.2X.XX: bytes=32 time=179ms TTL=48
Reply from 139.162.2X.XX: bytes=32 time=166ms TTL=48
WHY there is such a huge difference in time between ping the speedtest Singapore linode server and my actual linode server that is now in Linode Singapore DC?
At first I thought it might be my OS causing the delay. But I’ve striped my server to its bare to respond very fast to network request. So, here’s what I did: I just do a simple tracert and viola! the answer is there.
3.1 tracert speedtest.singapore.linode.com
9 4 ms * 4 ms ip-202-147-32-126.asianetcom.net [202.147.32.126]
10 83 ms 6 ms 7 ms te0-0-2-0.wr1.sin0.asianetcom.net [61.14.157.109]
11 9 ms 4 ms * xe-0-1-1.gw1.sin2.pacnet.net [202.147.52.64]
12 9 ms 4 ms * ip-61-14-147-179.asianetcom.net [61.14.147.179]
13 10 ms 4 ms * 139.162.0.6
14 4 ms 4 ms 3 ms speedtest.singapore.linode.com [139.162.23.4]
3.2 tracert li863-XX.members.linode.com
9 4 ms * 3 ms ip-202-147-32-126.asianetcom.net [202.147.32.126]
10 7 ms * 6 ms te0-3-0-3.wr2.sin0.asianetcom.net [61.14.158.42]
11 4 ms * 4 ms xe0-2-0.gw1.sin2.pacnet.net [202.147.52.66]
12 190 ms 189 ms 190 ms ip-61-14-147-177.asianetcom.net [61.14.147.177]
13 4 ms 4 ms * 139.162.0.2
14 166 ms 178 ms 176 ms li863-XX.members.linode.com
4. ANALYSIS.
From the 2 tracert tests, you can see that everything is the same until my 12 hops. ip-61-14-147-179.asianetcom.net to the speedtest server returns a super fast 4ms while ip-61-14-147-177.asianetcom.net to the actual linode returns 190ms. 47 to 48 times slower! Which means even though the Singapore speedtest server and the actual linode server are on Linode Singapore DC, they are placed on different networks (1 fast and the other much slower!). Linode, can you accept that?
As a user, I felt misled and sad. Assuming my test is right, this is a quality issue and Linode should rectify this with it’s Singapore service provider or network team asap. I hope Linode can rectify this issue soon as this is not the kind of quality we’ve bought into.
PS: You can buy me tea some time after you have corrected this. 🙂
Thanks!
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
ping speedtest.singapore.linode.com
Pinging speedtest.singapore.linode.com [139.162.23.4] with 32 bytes of data:
Reply from 139.162.23.4: bytes=32 time=5ms TTL=55
Reply from 139.162.23.4: bytes=32 time=5ms TTL=55
Reply from 139.162.23.4: bytes=32 time=5ms TTL=55
Reply from 139.162.23.4: bytes=32 time=5ms TTL=55
Ping statistics for 139.162.23.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 5ms, Average = 5ms
Result from SG
For me in the US, 279±2 ms from east coast USA.
Need POP in Australia… Singapore link is aweful… ask Azure, Rackspace and AWS all conceded they needed to be actually in AU, especially with new NBN rolling out with 100M down/40M up speeds on the way over next 2 years (20% done)
Oh:
Pinging speedtest.singapore.linode.com [139.162.23.4] with 32 bytes of data:
Reply from 139.162.23.4: bytes=32 time=171ms TTL=46
Reply from 139.162.23.4: bytes=32 time=175ms TTL=46
Reply from 139.162.23.4: bytes=32 time=185ms TTL=46
Reply from 139.162.23.4: bytes=32 time=169ms TTL=46
Ping statistics for 139.162.23.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 169ms, Maximum = 185ms, Average = 175ms
We have had a lot of requests for hosting apps/data in Asia, specifically in Singapore in some cases.
Your dedication to providing international hosting options like this one in Singapore is one of the reasons we built a custom Linode adapter for our web development platform: https://news.nanobox.io/linode-now-supported/
@Richard We always looking for ways to get accessibility to more people, so we’re glad this fulfilled the goal!
@Soh
PLEASE can we have a Sydney POP ?