I have a 1MB Dedicated PPPoA line which is suffering as well.

From what I can tell, the routing has been changed for all international traffic. The new route is severely overloaded, so we are experiencing extra hops, and huge amounts of packet loss.

I do not think this is caused by a break in a cable, as the issue first appeared a few days ago, went away, and returned. The cable would have had to break, get fixed, and break again for this story to be true.

It seems to me that TM is currently undergoing changes in infrastructure and, therefore, re-routing all users to an unaffected path. Not only does this unaffected path have extra hops, but it's also overloaded. Hence, we see higher pings, packet loss, and HEC Errors.

from my gaming machine;

C:\Documents and Settings\Gaming>ping guk.everquest2.com -n 10

Pinging sdkeq2-01-01.everquest2.com [199.108.12.33] with 32 bytes of data:

Request timed out.
Reply from 199.108.12.33: bytes=32 time=461ms TTL=47
Reply from 199.108.12.33: bytes=32 time=464ms TTL=47
Reply from 199.108.12.33: bytes=32 time=464ms TTL=47
Request timed out.
Reply from 199.108.12.33: bytes=32 time=471ms TTL=47
Reply from 199.108.12.33: bytes=32 time=460ms TTL=47
Request timed out.
Reply from 199.108.12.33: bytes=32 time=462ms TTL=47
Reply from 199.108.12.33: bytes=32 time=458ms TTL=47

Ping statistics for 199.108.12.33:
Packets: Sent = 10, Received = 7, Lost = 3 (30% loss),
Approximate round trip times in milli-seconds:
Minimum = 458ms, Maximum = 471ms, Average = 462ms

---

Added on August 4, 2009, 10:59 pmSimulate a small load (like loading a US web site based in Los Angeles), and notice 50% packet loss, and very high pings. International exchange is ultra congested. A scary thought at 11pm


C:\Documents and Settings\Gaming>ping guk.everquest2.com -n 10 -l 5000

Pinging sdkeq2-01-01.everquest2.com [199.108.12.33] with 5000 bytes of data:

Request timed out.
Reply from 199.108.12.33: bytes=5000 time=601ms TTL=47
Reply from 199.108.12.33: bytes=5000 time=599ms TTL=47
Request timed out.
Request timed out.
Request timed out.
Reply from 199.108.12.33: bytes=5000 time=602ms TTL=47
Reply from 199.108.12.33: bytes=5000 time=602ms TTL=47
Reply from 199.108.12.33: bytes=5000 time=599ms TTL=47
Request timed out.

Ping statistics for 199.108.12.33:
Packets: Sent = 10, Received = 5, Lost = 5 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 599ms, Maximum = 602ms, Average = 600ms

This post has been edited by mhaneline: Aug 4 2009, 10:59 PM

Every day between 2am-7am it goes back to "normal" speeds. Pings are 150-200ms lower to US and there is 0% packet loss. As soon as business hours start, the issues begin. I think TM is doing some kind of reset at around 2am every day (probably for you Torrent/P2P users) to reset connections, because it goes back to "normal" at roughly the same time every morning.

Packet loss is extreme bad, and pings 150 higher than Jaring. TM = fail


Ping statistics for 199.108.12.33:
Packets: Sent = 10, Received = 8, Lost = 2 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 364ms, Maximum = 372ms, Average = 366ms

mine, and TM in general is failing. Last few days extreme Packet Loss.

I would not say that it was fine all day. From 6AM on extreme Packet Loss again!

getting 12% packet loss to DNS 202.188.0.133
getting 8% packet loss to DNS 202.188.1.5



This indicates severe local issue. Even small local issue = huge international issue.

Test this and see if ok. This is not individual user problem. It is whole TM problem.



Should be 1.5M+ and ping should be under 300

Something has been very wrong for the past 3 days or so. I keep a close eye on Packet Loss as it affects me internationally. Packet loss was around 2% before this week, but now it is 10-20% with pings much higher than usual. This is the best ping / Packet Loss I could get right now:

Ping statistics for 199.108.12.33:
Packets: Sent = 100, Received = 90, Lost = 10 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 401ms, Maximum = 734ms, Average = 449ms


This is usually min 280 max 300 with 0% loss

TM = fail

Pinging 112.137.162.166 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 112.137.162.166:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),