Hinet slow ping times

Life Technology
1

In just tested my speed … look at the slow ping times

When is Hinet going to get it right? When it’s not speed than it’s ping (latency) they have problems with …

2

It actually makes surfing slooooow, it’s almost the same as too slow speed … you need to wait loooong for the servers to respond … it’s annoying.

3

Have you tried traceroute (on windows: tracert) to see which ‘hop’ has the big increase in latency? If it’s your first hop then your actual DSL line is busted or you have a trojan on your network spewing out spam. If it’s later down the line then you can blame Hinet.

4

Nothing is spewing here … have excellent security and firewalls, a router too …

5

This is the culprit …

5 kh-c12r2.router.hinet.net (220.128.25.121) 8 msec 4 msec 8 msec
6 pa-c12r12.USA-PAIX.router.hinet.net (211.22.225.145) 136 msec 136 msec 136 msec

6

tracert forumosa.com

Tracing route to forumosa.com [70.86.115.10]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.123.254
2 38 ms 33 ms 33 ms 125-232-96-254.dynamic.hinet.net [125.232.96.254
]
3 33 ms 33 ms 33 ms tp-pc1-c76r1.router.hinet.net [168.95.74.66]
4 * 35 ms 37 ms 220-128-11-54.HINET-IP.hinet.net [220.128.11.54]

5 33 ms 33 ms 33 ms 220-128-1-249.HINET-IP.hinet.net [220.128.1.249]

6 33 ms 33 ms 33 ms tp-s2-c108-85.router.hinet.net [211.72.108.85]
7 164 ms 163 ms 163 ms pa-c12r12.USA-PAIX.router.hinet.net [211.72.108.165]
8 164 ms 163 ms 163 ms POS5-0.IG3.PAO1.ALTER.NET [63.65.130.29]
9 164 ms 164 ms 164 ms 0.so-3-0-0.XL2.PAO1.ALTER.NET [152.63.50.2]
10 165 ms 164 ms 164 ms 0.so-5-0-0.XL2.SCL2.ALTER.NET [152.63.57.42]
11 164 ms 164 ms 164 ms 0.so-7-0-0.BR1.SCL2.ALTER.NET [152.63.57.101]
12 165 ms 165 ms 165 ms 204.255.169.174
13 165 ms 165 ms 166 ms xe-0-2-0.r20.plalca01.us.bb.gin.ntt.net [129.250
.4.230]
14 165 ms 166 ms 166 ms ae-1.r21.snjsca04.us.bb.gin.ntt.net [129.250.4.1
19]
15 205 ms 205 ms 205 ms p64-1-0-0.r21.dllstx09.us.bb.gin.ntt.net [129.25
0.3.153]
16 215 ms 216 ms 215 ms xe-4-1.r03.dllstx09.us.bb.gin.ntt.net [129.250.3
.226]
17 212 ms 211 ms 211 ms xe-4-4.r03.dllstx09.us.ce.gin.ntt.net [157.238.2
25.6]
18 209 ms 208 ms 209 ms te7-1.dsr02.dllstx3.theplanet.com [70.87.253.18]

19 208 ms 208 ms 208 ms po32.dsr02.dllstx5.theplanet.com [70.85.127.110]

20 209 ms 209 ms 225 ms po1.car04.dllstx5.theplanet.com [70.84.160.134]

21 208 ms 208 ms 208 ms a.73.5646.static.theplanet.com [70.86.115.10]

Trace complete.

7

tracert joost.com

Tracing route to joost.com [4.71.105.52]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.123.254
2 34 ms 34 ms 34 ms 125-232-96-254.dynamic.hinet.net [125.232.96.254
]
3 35 ms 46 ms 33 ms tp-pc1-c76r1.router.hinet.net [168.95.74.66]
4 34 ms 35 ms 33 ms 220-128-11-54.HINET-IP.hinet.net [220.128.11.54]

5 39 ms 39 ms 39 ms kh-c12r11.router.hinet.net [220.128.1.5]
6 40 ms 40 ms 40 ms kh-c12r1.router.hinet.net [220.128.24.121]
7 169 ms 169 ms 169 ms pa-c12r12.USA-PAIX.router.hinet.net [211.22.225.
145]
8 169 ms 169 ms 169 ms SO2-0-0.IG4.PAO1.ALTER.NET [63.65.130.117]
9 169 ms 169 ms 169 ms 0.so-1-1-0.XL2.PAO1.ALTER.NET [152.63.144.97]
10 171 ms 170 ms 170 ms 0.so-7-0-0.XL2.SJC7.ALTER.NET [152.63.48.2]
11 170 ms 170 ms 169 ms 0.so-7-0-0.BR1.SJC7.ALTER.NET [152.63.48.253]
12 172 ms 170 ms 171 ms OC-48-6-1-0-edge5.SanJose1.Level3.net [4.68.63.4
9]
13 170 ms 176 ms 179 ms ae-31-51.ebr1.SanJose1.Level3.net [4.68.123.30]

14 174 ms 179 ms * ae-1-100.ebr1.SanJose1.Level3.net [4.69.132.1]
15 181 ms 180 ms 179 ms ae-3-3.car1.Tustin1.Level3.net [4.69.132.217]
16 179 ms 180 ms 179 ms ae-3-3.car1.Tustin1.Level3.net [4.69.132.217]
17 179 ms 180 ms 179 ms JOOST-OPERA.car1.Tustin1.Level3.net [4.71.104.15
4]
18 179 ms 179 ms 179 ms sna-www-fe-2-bond0.joost.net [4.71.105.52]

Trace complete.

ping joost.com

Pinging joost.com [4.71.105.52] with 32 bytes of data:

Reply from 4.71.105.52: bytes=32 time=179ms TTL=48
Reply from 4.71.105.52: bytes=32 time=179ms TTL=48
Reply from 4.71.105.52: bytes=32 time=179ms TTL=48
Reply from 4.71.105.52: bytes=32 time=179ms TTL=48

Ping statistics for 4.71.105.52:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 179ms, Maximum = 179ms, Average = 179ms

ping forumosa.com

Pinging forumosa.com [70.86.115.10] with 32 bytes of data:

Reply from 70.86.115.10: bytes=32 time=208ms TTL=43
Reply from 70.86.115.10: bytes=32 time=208ms TTL=43
Reply from 70.86.115.10: bytes=32 time=209ms TTL=43
Reply from 70.86.115.10: bytes=32 time=209ms TTL=43

Ping statistics for 70.86.115.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 208ms, Maximum = 209ms, Average = 208ms

ping dyxum.com

Pinging dyxum.com [213.202.100.44] with 32 bytes of data:

Reply from 213.202.100.44: bytes=32 time=557ms TTL=113
Reply from 213.202.100.44: bytes=32 time=560ms TTL=113
Request timed out.
Reply from 213.202.100.44: bytes=32 time=560ms TTL=113

Ping statistics for 213.202.100.44:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 557ms, Maximum = 560ms, Average = 559ms

8

All those traceroutes are quite reasonable, and only the ping to 213.202.100.44 is really out of line. Pings to US should reasonably be 180-220ms from Taiwan. To Europe 350-400ms is typical since most network links here take the long way around through the US. For 213.202.100.44 the traceroute I tried bogs down between hops 18 and 19 in telia.net somewhere in Europe, so I don’t think that’s hinet’s fault.

9

Yesterday I had 500+ to HK and 600+ to Europe …