Mr Scratch
Expert Member
- Joined
- May 15, 2013
- Messages
- 4,872
- Reaction score
- 1,040
Based.
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
With which games are you seeing the latency spike in?
What sort of account do you have with us?
Pinging speedtest.lon02.softlayer.com [5.10.97.132] with 32 bytes of data:
Reply from 5.10.97.132: bytes=32 time=181ms TTL=45
Reply from 5.10.97.132: bytes=32 time=1195ms TTL=45
Reply from 5.10.97.132: bytes=32 time=181ms TTL=45
Reply from 5.10.97.132: bytes=32 time=179ms TTL=45
Ping statistics for 5.10.97.132:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 179ms, Maximum = 1195ms, Average = 434ms
C:\Users\jemsc>ping speedtest.lon02.softlayer.com
Pinging speedtest.lon02.softlayer.com [5.10.97.132] with 32 bytes of data:
Reply from 5.10.97.132: bytes=32 time=188ms TTL=45
Reply from 5.10.97.132: bytes=32 time=179ms TTL=45
Reply from 5.10.97.132: bytes=32 time=178ms TTL=45
Reply from 5.10.97.132: bytes=32 time=1036ms TTL=45
Ping statistics for 5.10.97.132:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 178ms, Maximum = 1036ms, Average = 395ms
C:\Users\jemsc>ping 185.60.112.158
Pinging 185.60.112.158 with 32 bytes of data:
Reply from 185.60.112.158: bytes=32 time=1660ms TTL=238
Reply from 185.60.112.158: bytes=32 time=235ms TTL=238
Reply from 185.60.112.158: bytes=32 time=522ms TTL=238
Reply from 185.60.112.158: bytes=32 time=196ms TTL=238
Ping statistics for 185.60.112.158:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 196ms, Maximum = 1660ms, Average = 653ms
C:\Users\jemsc>ping 185.60.112.158
Pinging 185.60.112.158 with 32 bytes of data:
Reply from 185.60.112.158: bytes=32 time=1563ms TTL=238
Reply from 185.60.112.158: bytes=32 time=284ms TTL=238
Reply from 185.60.112.158: bytes=32 time=198ms TTL=238
Reply from 185.60.112.158: bytes=32 time=197ms TTL=238
Ping statistics for 185.60.112.158:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 197ms, Maximum = 1563ms, Average = 560ms
C:\Users\jemsc>
Based.
![]()
Path of Exile (and was also getting the same spikes to Diablo 3 servers).
nice
I spent the past few days talking back and forth with the critical care and networking team to get perfect ping in Path of Exile, Overwatch and Rainbow Six Siege.
I'm in Cape Town and for me, there is now absolutely perfect ping to all three of these games with no packet loss.
Connecting to the London server in Path of Exile gives me a solid 166ms ping both during the day and in the evening.
So if you want to know more just ask.
Path of Exile (and was also getting the same spikes to Diablo 3 servers).
Capped data. I'm not convinced it's an ISP issue, I just need to narrow things down, as Telkom have done their thing for now.
*edit*
To PoE EU Servers:
To Diablo 3 EU servers:
I get these same spikes pinging to any server (local as well). I will also need to eliminate my wireless setup as a causative factor here.
FIIIIBRE!![]()
![]()
He's taking the capacity of ~100 subscribers, any way you can cut him off?![]()
Is AH aware of the issue with AH DNS and Steam downloads?
Our Team did look into the Steam issue this morning, and they've implemented a fix for it which should ensure everything is back to normal. You may need to restart your modem to ensure you've got the most up to date DNS settings.![]()
Was the Steam issue not being able to to start game downloads or updates? I had the issue for about 3 days and now it's fixed. Also is this part of the network update you told me about or has that not rolled out yet?
Yeah, when I tried to start a fresh game download it would just sit there and then Steam would throw a connection timeout error. My update that was half way through (started before the issue started) was able to finish but the next queued update was not able to start at all.It was definitely affecting game downloads, I'm not sure if updates to installed games was affected or not. This was a separate change that we made.
Yeah, when I tried to start a fresh game download it would just sit there and then Steam would throw a connection timeout error. My update that was half way through (started before the issue started) was able to finish but the next queued update was not able to start at all.
At least it's fixed now![]()