There is a lot that can be done, and a lot that is being done by our Team, the traceroute would just have helped us to find out if it is a localized issue with the routing, or one of the upstream providers.
Were you able to test the performance last night?
Hi Afrigenie,
Here is a local ping test to a DOTA server in Cape Town.
Pinging cpt-1.valve.net [152.111.192.244] with 32 bytes of data:
Reply from 152.111.192.244: bytes=32 time=903ms TTL=50
Reply from 152.111.192.244: bytes=32 time=892ms TTL=50
Reply from 152.111.192.244: bytes=32 time=895ms TTL=50
Reply from 152.111.192.244: bytes=32 time=718ms TTL=50
Ping statistics for 152.111.192.244:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 718ms, Maximum = 903ms, Average = 852ms
This is tracert to one of the active servers we play on:
Tracing route to 196.38.180.18 over a maximum of 30 hops
1 2 ms 1 ms 1 ms 10.0.0.2
2 799 ms 959 ms 971 ms 169-0-19-1-access.afrihost.co.za [169.0.19.1]
3 962 ms 959 ms 818 ms 41.170.79.230
4 901 ms 858 ms 1026 ms 41.170.79.236
5 691 ms 719 ms 734 ms 41.169.26.62
6 383 ms 470 ms 479 ms is.jinx.net.za [196.223.14.10]
7 696 ms 734 ms 679 ms core1a-pkl-te-1-2.ip.isnet.net [168.209.1.139]
8 877 ms 747 ms 715 ms 168.209.0.186
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13
Are you still able to help?