MWEB Gaming Feedback

Megamuffin said:
Same here even in an unpopulated area in WoW i get 600 ms, guess im gonna have to get a WA acc to raid with on WoW
Click to expand...

Could you provide me with some comparative traces between the MWEB and WA accounts to an international site. not Battlenet please as Blizzard firewalls out most responses so it's not all that useful.
 
Mweb and WoW was again horrible for me last night 3k world ping in Firelands on MWeb, Thank god I have an FNB Connect account, I changed to that and enjoyed raiding Firelands with a 250 world and home ping with no spikes. So tired of these issues with MWeb.... BTW in the Northern suburbs in JHB. Time it was failing was around 20:00.
 
Same problem here. I also use a 4Mb mweb uncapped account and two weeks ago I started getting huge lag spikes, high latency and constant disconnections from wow.

I switched to my WA account and everything was running fine. This problem started only a few weeks ago and it seems like it's only on mweb accounts (a friend of mine also on mweb uncapped alo can't play wow because of this)

I'm in Vanderbijlpark so it seems like it's not isolated to just one area.
 
Well, something just happened.... something NOT very pretty....

C:\Users\Astro>tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.244.70]
over a maximum of 30 hops:

1 <1 ms <1 ms 5 ms
2 12 ms 9 ms 8 ms 41-133-74-1.dsl.mweb.co.za [41.133.74.1]
3 324 ms 309 ms * tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.169.170]
4 * 323 ms 321 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 * 594 ms * TenGigE0-1-0-0.12.vic-up-1.mweb.co.za [196.22.169.241]
6 * * 586 ms tengige0-3-1-0.mid-up-1.mweb.co.za [196.22.169.210]
7 * * * Request timed out.
8 * * * Request timed out.
9 835 ms 832 ms 829 ms te3-4.ccr02.lon02.atlas.cogentco.com [154.54.36.169]
10 * * * Request timed out.
11 * 842 ms 840 ms ldn-b4-link.telia.net [213.248.70.237]
12 * * 814 ms ldn-bb2-link.telia.net [80.91.249.181]
13 * * * Request timed out.
14 * * * Request timed out.
15 * 804 ms 799 ms 212.58.238.137
16 * * * Request timed out.
17 * * * Request timed out.
18 * 845 ms * bbc-vip115.telhc.bbc.co.uk [212.58.244.70]
19 842 ms 836 ms 837 ms bbc-vip115.telhc.bbc.co.uk [212.58.244.70]

Will give my modem the "recommended" 10 min rest now, and check after that....
 
had bad latency in firelands as well..had to switch to WA account :(
 
Well, courtesy of Eskom/Ekurhuleni I lost power shortly after my post, so I don't know if the lag improved.
 
@Blustorm that type of latency indicates a more low level issue which i would generally relate to a congestion issue, please let me know if you experience this again, or on any sort of regular cycle and we can try and raise this with Telkom for you.

I have several cases pending at the moment where we have had acknowledgement of DSLAM congestion from their side and we are pushing as much as possible to get them to upgrade the relevant infrastructure.
 
Again having high latency on MWeb, and don't tell me it's congestion ALL my other accounts work. This is really starting to pi$$ me off. I think the next month will be my last with MWeb, I can't handle this incompetence. If I was this useless at my job I would've been fired long ago...
 
After last night's bad latency....well, tonight its not better. 1500ms! I have a raid starting at 8...so, its WA again. Its very erratic with MWeb, have not had issues for +/- 3 weeks, and now its like that again.
 
Tom242 said:
After last night's bad latency....well, tonight its not better. 1500ms! I have a raid starting at 8...so, its WA again. Its very erratic with MWeb, have not had issues for +/- 3 weeks, and now its like that again.
Click to expand...


update: switched to WA....solid 197ms!!!! I am just glad to have an account for raiding...but that makes me think if the money that I pay to MWeb is not wasted?


after raid update: 200ms all the time, on WA...MWeb not possible,1k+ ms
 
Last edited:
Will@MWEB said:
@Blustorm that type of latency indicates a more low level issue which i would generally relate to a congestion issue, please let me know if you experience this again, or on any sort of regular cycle and we can try and raise this with Telkom for you.

I have several cases pending at the moment where we have had acknowledgement of DSLAM congestion from their side and we are pushing as much as possible to get them to upgrade the relevant infrastructure.
Click to expand...
Hi Will,

It happened again last night, but at the exact same time my friend in Edenvale had the same issue. Now I could possibly understand that my DSLAM could have congestion, but how could two DSLAMs 25kms apart have congestion at the same time?]

Incidentally, it took about 10 mins, then resolved itself without me switching off my modem.
 
Last edited:
BluStorm said:
Hi Will,

It happened again last night, but at the exact same time my friend in Edenvale had the same issue. Now I could possibly understand that my DSLAM could have congestion, but how could two DSLAMs 25kms apart have congestion at the same time?]

Incidentally, it took about 10 mins, then resolved itself without me switching off my modem.
Click to expand...

Do you happen to recall the time that you had this problem last night?

I'm asking as I did pick up from last night that our graphing showed two very short dips in the traffic on Seacom, lasting about 5 minutes each between 20h00 and 22h00. These weren't outages per say as they were only slight dips and there's no indication of any equipment failure anywhere on our monitoring. it does however indicate that there may have been a slight drop in the capacity on the link at those times, which would explain a latency spike on your side.

Our engineers are doing root cause analysis on this with Seacom to see if they can establish what happened. I'd just like to stress that this would account for what you're describing last night if it fit's into the right time window, but it's not a general explanation for any other latency problems you may be having.
 
It was probably between 20:30 and 20:50 last night.

But my trace routes showed high pings (>100ms / timeouts) for the pings to Victory park as well. Coincidence?
 
FYI to 'non business users' - SEACOM has started maintenance already - Business clients where informed that the 10th it started - so might explain this trend.
 
WTFast is now offering South African servers for you to try out!

To test this out:

1. Make sure you have the latest build of WTFast: https://secure.wtfast.com/download.aspx
2. On the WTFast game/server selection screen, select “show server locations”
3. On the server location list, we now have 3 server locations listed for South Africa:
a. South Africa – this is a direct connection to our ZA server. You will connect to your game directly from this ZA server.
b. South Africa to EU – connect to our ZA server, then our server in Germany. (then your game)
c. South Africa to US – connect to our ZA server, then our server in Washington, DC (east coast US, then your game)
4. To try this out, you should either choose South Africa, or EU if you are connecting to EU game severs, or US for US servers.

We are anxious for your feedback to let us know how these new ZA servers work out from South Africa compared to our other servers. Leave feedback here, or send it to [email protected] and I can give you some free WTFast time.
 
nelis said:
I can't connect to steam.
Click to expand...

No problems this end nelis. Also just to clarify the steam servers that sit on our network do not handle authentication, they only provide content caching.
 
So I have been using the SA servers WTFast for WoW, they seem solid although my latency is not any lower than when using a international server.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X