Packet Loss - Please help me

[jonn1]

Hello everyone!
I work online for a company in Taipei hosted by Chief Telecom. Lately, I've been experiencing packet loss between my connection and 2 of their servers (152.101.38.101 - Hong Kong, Quarry Bay) and 203.85.37.35 (Singapore). When I try to do a tracert, for example to the server from Singapore. I get these results:

C:\Users\Dye>tracert 203.85.37.35

Tracing route to 203.85.37.35 over a maximum of 30 hops

  1     1 ms     1 ms     1 ms  dsldevice.lan [192.168.1.254]
  2    11 ms     9 ms     9 ms  10.194.128.1
  3     *        5 ms     4 ms  bl3-76-26.dsl.telepac.pt [213.13.76.26]
  4     5 ms     5 ms     5 ms  bl3-76-25.dsl.telepac.pt [213.13.76.25]
  5     5 ms     5 ms     4 ms  bt-cr1-hu-4-0-0.cprm.net [195.8.10.213]
  6    48 ms    47 ms    45 ms  lon3-cr1-be2.cprm.net [195.8.0.242]
  7    42 ms    41 ms    41 ms  195.66.224.177
  8    41 ms    42 ms    40 ms  202.84.178.5
  9   759 ms   750 ms   700 ms  i-0-0-2-0.skdi-core01.bx.telstraglobal.net [202.
84.144.6]
 10   769 ms   778 ms   709 ms  202.84.244.42
 11   760 ms   754 ms   787 ms  unknown.telstraglobal.net [202.126.128.42]
 12     *      719 ms   688 ms  202-76-85-21.static.hk.net [202.76.85.21]
 13   428 ms   433 ms   423 ms  203.85.37.45
 14   446 ms   438 ms   431 ms  203.85.37.35

Trace complete.
Does the 3rd hop's 1st RTT column cause the problem?

Here are the ping tests
C:\Users\Dye>ping 152.101.38.101 -n 40

Pinging 152.101.38.101 with 32 bytes of data:
Reply from 152.101.38.101: bytes=32 time=298ms TTL=105
Request timed out.
Reply from 152.101.38.101: bytes=32 time=299ms TTL=105
Reply from 152.101.38.101: bytes=32 time=307ms TTL=105
Reply from 152.101.38.101: bytes=32 time=297ms TTL=105
Reply from 152.101.38.101: bytes=32 time=297ms TTL=105
Reply from 152.101.38.101: bytes=32 time=299ms TTL=105
Reply from 152.101.38.101: bytes=32 time=296ms TTL=105
Request timed out.
Reply from 152.101.38.101: bytes=32 time=298ms TTL=105
Reply from 152.101.38.101: bytes=32 time=296ms TTL=105
Reply from 152.101.38.101: bytes=32 time=297ms TTL=105
Reply from 152.101.38.101: bytes=32 time=326ms TTL=105
Reply from 152.101.38.101: bytes=32 time=296ms TTL=105
Reply from 152.101.38.101: bytes=32 time=302ms TTL=105
Reply from 152.101.38.101: bytes=32 time=385ms TTL=105
Reply from 152.101.38.101: bytes=32 time=297ms TTL=105
Reply from 152.101.38.101: bytes=32 time=297ms TTL=105
Reply from 152.101.38.101: bytes=32 time=303ms TTL=105
Reply from 152.101.38.101: bytes=32 time=297ms TTL=105
Reply from 152.101.38.101: bytes=32 time=298ms TTL=105
Reply from 152.101.38.101: bytes=32 time=296ms TTL=105
Reply from 152.101.38.101: bytes=32 time=296ms TTL=105
Reply from 152.101.38.101: bytes=32 time=320ms TTL=105
Reply from 152.101.38.101: bytes=32 time=297ms TTL=105
Reply from 152.101.38.101: bytes=32 time=297ms TTL=105
Reply from 152.101.38.101: bytes=32 time=371ms TTL=105
Reply from 152.101.38.101: bytes=32 time=352ms TTL=105
Reply from 152.101.38.101: bytes=32 time=296ms TTL=105
Reply from 152.101.38.101: bytes=32 time=299ms TTL=105
Reply from 152.101.38.101: bytes=32 time=297ms TTL=105
Reply from 152.101.38.101: bytes=32 time=295ms TTL=105
Reply from 152.101.38.101: bytes=32 time=295ms TTL=105
Reply from 152.101.38.101: bytes=32 time=297ms TTL=105
Reply from 152.101.38.101: bytes=32 time=297ms TTL=105
Reply from 152.101.38.101: bytes=32 time=297ms TTL=105
Reply from 152.101.38.101: bytes=32 time=296ms TTL=105
Reply from 152.101.38.101: bytes=32 time=297ms TTL=105
Reply from 152.101.38.101: bytes=32 time=297ms TTL=105
Reply from 152.101.38.101: bytes=32 time=304ms TTL=105

Ping statistics for 152.101.38.101:
    Packets: Sent = 40, Received = 38, Lost = 2 (5% loss),
Approximate round trip times in milli-seconds:
    Minimum = 295ms, Maximum = 385ms, Average = 304ms

C:\Users\Dye>

C:\Users\Dye>ping 203.85.37.35 -n 40

Pinging 203.85.37.35 with 32 bytes of data:
Reply from 203.85.37.35: bytes=32 time=431ms TTL=110
Reply from 203.85.37.35: bytes=32 time=419ms TTL=110
Reply from 203.85.37.35: bytes=32 time=427ms TTL=110
Reply from 203.85.37.35: bytes=32 time=430ms TTL=110
Reply from 203.85.37.35: bytes=32 time=445ms TTL=110
Reply from 203.85.37.35: bytes=32 time=434ms TTL=110
Reply from 203.85.37.35: bytes=32 time=424ms TTL=110
Reply from 203.85.37.35: bytes=32 time=441ms TTL=110
Reply from 203.85.37.35: bytes=32 time=429ms TTL=110
Reply from 203.85.37.35: bytes=32 time=429ms TTL=110
Reply from 203.85.37.35: bytes=32 time=432ms TTL=110
Reply from 203.85.37.35: bytes=32 time=501ms TTL=110
Reply from 203.85.37.35: bytes=32 time=450ms TTL=110
Reply from 203.85.37.35: bytes=32 time=471ms TTL=110
Reply from 203.85.37.35: bytes=32 time=440ms TTL=110
Reply from 203.85.37.35: bytes=32 time=500ms TTL=110
Reply from 203.85.37.35: bytes=32 time=439ms TTL=110
Reply from 203.85.37.35: bytes=32 time=420ms TTL=110
Reply from 203.85.37.35: bytes=32 time=429ms TTL=110
Reply from 203.85.37.35: bytes=32 time=413ms TTL=110
Reply from 203.85.37.35: bytes=32 time=435ms TTL=110
Reply from 203.85.37.35: bytes=32 time=426ms TTL=110
Reply from 203.85.37.35: bytes=32 time=426ms TTL=110
Reply from 203.85.37.35: bytes=32 time=443ms TTL=110
Reply from 203.85.37.35: bytes=32 time=422ms TTL=110
Reply from 203.85.37.35: bytes=32 time=425ms TTL=110
Reply from 203.85.37.35: bytes=32 time=433ms TTL=110
Reply from 203.85.37.35: bytes=32 time=428ms TTL=110
Reply from 203.85.37.35: bytes=32 time=428ms TTL=110
Reply from 203.85.37.35: bytes=32 time=452ms TTL=110
Request timed out.
Reply from 203.85.37.35: bytes=32 time=480ms TTL=110
Reply from 203.85.37.35: bytes=32 time=433ms TTL=110
Reply from 203.85.37.35: bytes=32 time=448ms TTL=110
Reply from 203.85.37.35: bytes=32 time=428ms TTL=110
Reply from 203.85.37.35: bytes=32 time=433ms TTL=110
Reply from 203.85.37.35: bytes=32 time=428ms TTL=110
Reply from 203.85.37.35: bytes=32 time=429ms TTL=110
Reply from 203.85.37.35: bytes=32 time=428ms TTL=110
Reply from 203.85.37.35: bytes=32 time=429ms TTL=110

Ping statistics for 203.85.37.35:
    Packets: Sent = 40, Received = 39, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
    Minimum = 413ms, Maximum = 501ms, Average = 437ms

In terms of Internet Speed, I use an ethernet cable, have fiber optic, modem's firmware is fully updated and my internet speed when testing to Taipei, Chief Telecom is - 329ms, 6.45 download speed, 4.42 upload speed (their requirements are 800kb d/s and 400kb u/s)

What do I do? Can anyone help me??
I've contacted my ISP but they are playing the quickly dismiss game.
Please help!

[Geek-9pm]

A 2 % lose is not extreme, but it is higher than it should be. Your lose should be  more like about 0.05 % or one  prone part in two thousand.   You can check with other servers and find what is typical in your  area.
A number of providers do not consider packet loss to be a matter of concern.  This kind of thinking is potentially harmful. But it is hard to convince others that it matters.

[jonn1]

Thank you very much for your reply Geek 9-pm.

Do you have any suggestions on how I can find the typical server for my area?
Seeing that this company's ITs always ping for 5 different servers, 2 from Taiwan, 1 from South Africa, 1 from Hong Kong and 1 from Singapore when testing the connection. What should I do to solve this packet loss?

Please excuse me if the answer is quite obvious, I barely know anything about these topics ^^

Thanks again