Nothing at this point, I'll enquire with the team and revert ASAP.Random aside- any news on if / when you’ll pick up FF in Gauteng again or is it a lower priority thing?
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Nothing at this point, I'll enquire with the team and revert ASAP.Random aside- any news on if / when you’ll pick up FF in Gauteng again or is it a lower priority thing?
Nothing at this point, I'll enquire with the team and revert ASAP.
I doubt anyone wants to touch FF at this point in time IMO... better up times on openserveNo stress, it’s not impacting anything at the moment so whenever you get a chance
I doubt anyone wants to touch FF at this point in time IMO... better up times on openserve

Playing D4 latency is so crap.
In the old day we have latency of 198ms, now even worse. This was on Telkom dial up modem.
See attached pic on this. I can't except this.
Why do we have fiber? To be in a better position.
View attachment 1750396
I'm not a person that complains a lot here.
I'm on 200/200 connection, wtf is happening. This is like pissing money in the water.
I'm on Vumatel, East rand Springs.
I play only Diablo 4.Is latency bad just to D4 servers or for all/most internet use? Is it just you or are other players / users in your area having similar issues? Is this all the time or at a point in time?
That will go a long way to helping in figuring out where the issue is
Playing D4 latency is so crap.
In the old day we have latency of 198ms, now even worse. This was on Telkom dial up modem.
See attached pic on this. I can't except this.
Why do we have fiber? To be in a better position.
View attachment 1750396
I'm not a person that complains a lot here.
I'm on 200/200 connection, wtf is happening. This is like pissing money in the water.
I'm on Vumatel, East rand Springs.
I play only Diablo 4.
Under normal play, get 200ms latency.
Have seen occasionally be up in the +300ms range. But comes down and settles at 200ms
Seen this also on my old laptop happening. My new laptop lost its pin, can't login.
WebSquadZA can you explain how you are involved with fiber.
I just want to get a picture.
I'm with Vuma, signed up with you.
How is the path to England
Speaking under correction here but i believe D4 is hosted on Google servers so would be picked up locally by Google in JHB.A reminder here that latency is the RTT between 2 spots on the internet. In this case your home (point a) and the D4 servers (point b). Latency will vary for every single connection you make, though when rounded up to ms, we can approximate the following:
1. within a region (eg. your home to other networks in JHB): +- 1-3ms
2. between regions: eg. JHB-CPT is +- 20ms and JHB-DBN is +- 8ms
3. between countries: eg. CPT-LON is +- 150ms, JHB - SINGAPORE is +- 130ms and so on. As you can see, it goes up the further your connection goes.
To use the plumbing analogy, Vuma provide the pipe between your home and a POP in JHB, we provide the internet (water) over this pipe. Now when it comes to issues on a game like this, it's more likely some sort of routing or upstream issue.
I don't play D4, so I have little idea how it works and what server endpoints are involved. The first thing is to figure out why you're having this issue. Is it:
- An issue between your home and the POP? IE are there elevated latencies on the last mile Vuma portion? You can run an MTR here. If you're unsure how to, please reach out to our support team so they can help you troubleshoot your line and make sure it's 100%.
- Is there a general issue reaching Blizzard? From my tests this morning, to known destinations, we're reaching their EU servers at +- 170ms from JHB, so it doesn't seem so. Remember I don't know the intricacies of their setup, so we need to work together to figure this portion out.
- Are you being pushed over to a very remote server? Can you choose a region in D4, or is this automatically allocated to you? We could also be looking at some very weird asymmetric routing as we saw with Vultr servers hosting Dota in Singapore these past few weeks (which should be resolved now)
Looking forward to getting you sorted out. Step 1 is to log a ticket so our team can eliminate any last mile issues. Also, if you can help the team figure out what IPs you're connecting to, this will speed up the process considerably.
I haven't seen the specs myself but most likey a mirror server, same happens with Warzone servers, Absolute rubbish game... imoSpeaking under correction here but i believe D4 is hosted on Google servers so would be picked up locally by Google in JHB.
When it launched they were on Google servers but that could have changed...
Taking a look at Resource Monitor during a play session they have Game Content hosted on Google,but their actual Gameplay servers are on a Blizzard IP range which wouldn't go through the Google peeringSpeaking under correction here but i believe D4 is hosted on Google servers so would be picked up locally by Google in JHB.
When it launched they were on Google servers but that could have changed...
I connect to EU server which basically England London.A reminder here that latency is the RTT between 2 spots on the internet. In this case your home (point a) and the D4 servers (point b). Latency will vary for every single connection you make, though when rounded up to ms, we can approximate the following:
1. within a region (eg. your home to other networks in JHB): +- 1-3ms
2. between regions: eg. JHB-CPT is +- 20ms and JHB-DBN is +- 8ms
3. between countries: eg. CPT-LON is +- 150ms, JHB - SINGAPORE is +- 130ms and so on. As you can see, it goes up the further your connection goes.
To use the plumbing analogy, Vuma provide the pipe between your home and a POP in JHB, we provide the internet (water) over this pipe. Now when it comes to issues on a game like this, it's more likely some sort of routing or upstream issue.
I don't play D4, so I have little idea how it works and what server endpoints are involved. The first thing is to figure out why you're having this issue. Is it:
- An issue between your home and the POP? IE are there elevated latencies on the last mile Vuma portion? You can run an MTR here. If you're unsure how to, please reach out to our support team so they can help you troubleshoot your line and make sure it's 100%.
- Is there a general issue reaching Blizzard? From my tests this morning, to known destinations, we're reaching their EU servers at +- 170ms from JHB, so it doesn't seem so. Remember I don't know the intricacies of their setup, so we need to work together to figure this portion out.
- Are you being pushed over to a very remote server? Can you choose a region in D4, or is this automatically allocated to you? We could also be looking at some very weird asymmetric routing as we saw with Vultr servers hosting Dota in Singapore these past few weeks (which should be resolved now)
Looking forward to getting you sorted out. Step 1 is to log a ticket so our team can eliminate any last mile issues. Also, if you can help the team figure out what IPs you're connecting to, this will speed up the process considerably.

It looks like you've created duplicate profiles on our system and your second profile isn't linked to any accounts.Good day
View attachment 1750695
I logged in, then I click on "Open Ticket".
Then a window pops up telling me "No accounts found."
You can see I logged in, Hello Jochen.
Want to log a ticket but I can't.
Latency is still an issue to Diablo server. Early morning getting +300ms.
it should be under 200ms as you explained the other day.
These are all Google IPs, handed over locally via peering and entirely dependent on Google's transit. These would all be the same for all local ISPs that peer with Google (so all ISPs). Testing EU-WEST, I see about 170ms from JHB. So unlikely this is where you're connecting to for gameplay, as this seems correctI connect to EU server which basically England London.
I don't have option were to connect, all EU.
If I connect to Singapore, I lose all my char. Like a clean begin.
Same with America.
This what I picked up: Not me somebody else.
here you go
the locations i mined from the server slam (they are production)
serverpool: us-central | address: 34.134.81.253 | port: 54546
serverpool: us-west | address: 34.145.56.198 | port: 54545
serverpool: eu-west | address: 34.159.2.39 | port: 54546
serverpool: asia-northeast | address: 34.84.12.125 | port: 54546
serverpool: southamerica-east | address: 34.95.165.101 | port: 54546
serverpool: australia-southeast | address: 34.151.97.211 | port: 54545
and you automatically get assigned to the closest one to your ip
also its all cloud based servers (kubernetes) so they can scale up/down as needed live without the need of closing the servers
Hope this will help?
This seems to be an IP somewhere In the US, judging by the trace route. What is more interesting is that blizzard peer in the EU, but none of our upstreams are learning this IP there. Rather via a Blizzard upstream, Telia. There's an odd 50ms jump somewhere past Chicago, seemingly Las Vegas. I've checked our upstreams, as well as a number of other networks locally with looking glasses, this issue seems to be Blizzard side to this specific IP. It pegs it at 300ms, which is what @HowTo is complaining about. So I do think there's something odd going on D4 side here. But we're happy to keep investigating.Taking a look at Resource Monitor during a play session they have Game Content hosted on Google,but their actual Gameplay servers are on a Blizzard IP range which wouldn't go through the Google peering
(I got 137.221.106.121 on my test Run)
Blizzard (and Telia) have a coloured history with South African latency for more than a decade unfortunately because of this strange US based hosting of certain services,they do quite a bit of their own custom routing that doesn't always play well. I've found in the past doing a VPN connection to the US and then playing cuts the latency significantly when those times do happenThis seems to be an IP somewhere In the US, judging by the trace route. What is more interesting is that blizzard peer in the EU, but none of our upstreams are learning this IP there. Rather via a Blizzard upstream, Telia. There's an odd 50ms jump somewhere past Chicago, seemingly Las Vegas. I've checked our upstreams, as well as a number of other networks locally with looking glasses, this issue seems to be Blizzard side to this specific IP. It pegs it at 300ms, which is what @HowTo is complaining about. So I do think there's something odd going on D4 side here. But we're happy to keep investigating.
I’ve responded here. Your email is not the email on file, you will need to reach out to our team to confirm your identity and have your new email linked. Otherwise please use the email address you initially used to sign up.
Have you managed to track down D4 IPs? Also do you know anyone else locally who has lower latency to these servers? As I said in my last response, the IP that @PsyWulf kindly provided is in Las Vegas, which explains 300ms. The IPs you picked up seem to be more frontend IPs and are all hosted by Google with little ability to route around. The first thing to establish is whether a better IP exists.Just a quick question.
Will IPv6 not improve the situation.
I have not set it up for the new router.