Anyone else experiencing high ping to Dota SA server lately?

[8BitLife]

I mentioned this in a fibre ISP thread too, but apparently not a lot of Dota players there. I am with Seacom through Vumatel. My Dota ping has always been 1 to SA servers. This week suddenly it shot up to 300 and the last 2 days it has been at 170. Seacom said they reset my IP or something but it didn't do anything. Was on the phone with them now where we pinged, through Powershell, the 3 SA Dota server IP addresses and each time it was fine(ie 1ms to 2ms). But when I go back in game it still pings at 177. And it is only to SA servers. Literally giving me the same pings as always to foreign servers.

Any idea what the problem can be?

Edit: When I unplug the LAN cable and play through my phone's Vodacom connection instead, my ping is fine.

 

[DarkSt0rm]

Nope. I play with 2 to 6ms... Sounds like a bad route, I'd suggest you contact your ISP with traceroutes and get them to fix it also try play with a VPN with local servers.

 

[Fulcrum29]

A lot off people are having a bad connection with official Valve servers in South Africa and from asking around it seems those affected are from everywhere but Johannesburg.

 

[8BitLife]

A lot off people are having a bad connection with official Valve servers in South Africa and from asking around it seems those affected are from everywhere but Johannesburg.

I did. Their response:

Good morning

As discussed, and shown in the screenshot, we observe no latency concerns to the IP's provided.

We also note no latency or service issues on any other general services and destinations.

Your netstat shows IP's 184.87.168.9:80 (akamai) to which we pick up no latency, and 52.156.204.185:443 (Microsoft) where we pick up latency of 200ms from 104.44.20.207 (Microsoft outside our network we have no control over)

As such, at this point we can not assist further without the definite IP address you are connecting to in-game, and even then we can only control up to the point where this leaves our network as we have no control over peering and/or routing outside our network as this will be up to the destination IP to resolve.

IAW: Tough. Your problem. Deal with it. It is definitely an issue on Seacom's side since I don't have this issue through a Vodacom connection and I don't hear other people on other ISPs complaining about this.

 

[Fulcrum29]

I did. Their response:

Good morning

As discussed, and shown in the screenshot, we observe no latency concerns to the IP's provided.

We also note no latency or service issues on any other general services and destinations.

Your netstat shows IP's 184.87.168.9:80 (akamai) to which we pick up no latency, and 52.156.204.185:443 (Microsoft) where we pick up latency of 200ms from 104.44.20.207 (Microsoft outside our network we have no control over)

As such, at this point we can not assist further without the definite IP address you are connecting to in-game, and even then we can only control up to the point where this leaves our network as we have no control over peering and/or routing outside our network as this will be up to the destination IP to resolve.

IAW: Tough. Your problem. Deal with it. It is definitely an issue on Seacom's side since I don't have this issue through a Vodacom connection and I don't hear other people on other ISPs complaining about this.

I received a similar response when asking about the loss many of the people outside of Johannesburg is experiencing with CSGO. In summary they said I should take it up with my ISP, which I did before contacting them, and the loss does seem to be at their point of origin when doing MTR, but it is very hard to establish the source of the issue. I believe it may be due to some firewall or rerouting config, but who am I to say.

Oddly enough, though this is a 'local' issue it started with the submarine cable breaks from my experience. There may have been a few changes made to compensate as their local servers still need to communicate with the core servers for full functionality.

 

[8BitLife]

I received a similar response when asking about the loss many of the people outside of Johannesburg is experiencing with CSGO. In summary they said I should take it up with my ISP, which I did before contacting them, and the loss does seem to be at their point of origin when doing MTR, but it is very hard to establish the source of the issue. I believe it may be due to some firewall or rerouting config, but who am I to say.

Oddly enough, though this is a 'local' issue it started with the submarine cable breaks from my experience. There may have been a few changes made to compensate as their local servers still need to communicate with the core servers for full functionality.

Might be, but for me it only started halfway through last week which was weeks after the break in cables happened. And like I said, not having this issue on Vodacom connection. Someone else mentioned it is Seacom's peering policies that is causing it.

 

[Nibiru]

Perhaps the internet cable(s) along Africa being damaged in the ocean? Crayfish nibbling it or some anchor being dragged over it.

It has not been fixed 100% yet.

 

[Mypro-D]

I have the same problem. Seems like a peering issue as other accounts work fine. Just Seacom.

 

[8BitLife]

Perhaps the internet cable(s) along Africa being damaged in the ocean? Crayfish nibbling it or some anchor being dragged over it.

It has not been fixed 100% yet.

Would explain it if I was connecting to a foreign server. But I am connecting to a local server so should not be affected by the cable breaks. Plus it only started a week ago which is a month after the cable breaks happened.

 

[8BitLife]

I received a similar response when asking about the loss many of the people outside of Johannesburg is experiencing with CSGO. In summary they said I should take it up with my ISP, which I did before contacting them, and the loss does seem to be at their point of origin when doing MTR, but it is very hard to establish the source of the issue. I believe it may be due to some firewall or rerouting config, but who am I to say.

Oddly enough, though this is a 'local' issue it started with the submarine cable breaks from my experience. There may have been a few changes made to compensate as their local servers still need to communicate with the core servers for full functionality.

BTW I am from JHB...but finally got this repsonse from Seacom today:

We require 1-month calendar notice, and an official request being sent to [email protected].

Having said the above and with valid reason, please understand that we have now had a few reports on the same issue (RE: Valve/Steam issues) which we are busy addressing with the provider directly.

No ETA for resolution, but this is being dealt with as a matter of urgency.

 

[HerZeLeiD]

And that cable break is taking ages to fix as well. When ZA sleeps I turn to BF4 and R6S on EU. Usually I would get 160 - 180ms, instead I get 220 - 240ms which is enough to feel the difference.

 

[8BitLife]

Seems to have been fixed for Seacom clients at least:

Good morning

We have received confirmation from Valve that routing has been restored.

Please test your end and advise soonest?

 

[danny Bo_0M]

I mentioned this in a fibre ISP thread too, but apparently not a lot of Dota players there. I am with Seacom through Vumatel. My Dota ping has always been 1 to SA servers. This week suddenly it shot up to 300 and the last 2 days it has been at 170. Seacom said they reset my IP or something but it didn't do anything. Was on the phone with them now where we pinged, through Powershell, the 3 SA Dota server IP addresses and each time it was fine(ie 1ms to 2ms). But when I go back in game it still pings at 177. And it is only to SA servers. Literally giving me the same pings as always to foreign servers.

Any idea what the problem can be?

Edit: When I unplug the LAN cable and play through my phone's Vodacom connection instead, my ping is fine.

Hi.
I know a few people having the same problems.
You can try switching from ethernet cable connection to wireless connection or e-cable to wi-fi
hope that helps you too

shap