MWEB Uncapped Subscribers Feedback

[MWEBHelp]

Has not happened so far. How do i do a pathping test thou? Like what command do I use?

Evening Sillicur, please refer to the following link for more information.

http://eu.blizzard.com/support/article.xml?locale=en_GB&articleId=36692

 

[hambone]

I'm pleased to report that my NNTP issues from last month have been resolved this month. Sickbeard backlog is cleared, yay!

 

[Sillicur]

I'm pleased to report that my NNTP issues from last month have been resolved this month. Sickbeard backlog is cleared, yay!

Same, NNTP has been flying for a few weeks now.

 

[fbman]

mine too.,. I am getting nice speeds on NNTP

 

[Synaesthesia]

Anyone else's downloads / streaming crawling this evening?

My torrents aren't as fast as usual tonight.

edit: scratch that, they're going fast now

 

[Sillicur]

Dear Mweb, at exactly 12 each night ping jumps up and there are timeouts. This is with Mweb.

Ping statistics for 84.234.17.86:
Packets: Sent = 56, Received = 46, Lost = 10 (17% loss),
Approximate round trip times in milli-seconds:
Minimum = 239ms, Maximum = 493ms, Average = 293ms


This is with afrihost:

Ping statistics for 84.234.17.86:
Packets: Sent = 37, Received = 37, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 227ms, Maximum = 251ms, Average = 230ms

This is a tracert with Mweb to Jolt.co.uk.

Tracing route to jolt.co.uk [84.234.17.86]
over a maximum of 30 hops:

1 25 ms 21 ms 23 ms 41-133-132-1.dsl.mweb.co.za [41.133.132.1]
2 298 ms 295 ms * Te1-1-0.505.cpt-ipc-1.mweb.co.za [196.28.178.178
]
3 302 ms 300 ms 301 ms Vlan92.cpt-hscore-1.mweb.co.za [196.28.179.11]
4 297 ms * 307 ms TenGigE0-2-0-0.11.cpt-up-1.mweb.co.za [196.28.17
8.97]
5 458 ms 461 ms 460 ms pos0-0-3-0.lon-up-1.mweb.co.za [196.22.164.2]
6 592 ms 636 ms 502 ms linx-extreme1.netrino.co.uk [195.66.227.18]
7 451 ms 453 ms * thn-edge.netrino.co.uk [84.234.19.142]
8 464 ms * 468 ms hex-edge.netrino.co.uk [84.234.19.146]
9 467 ms 467 ms 462 ms bs1-core.netrino.co.uk [84.234.19.5]
10 465 ms * * bruce.ferrago.net [84.234.17.86]
11 458 ms 461 ms 460 ms bruce.ferrago.net [84.234.17.86]

Trace complete.

Now, for a tracert with afrihost to jolt.co.uk.

Tracing route to jolt.co.uk [84.234.17.86]
over a maximum of 30 hops:

1 22 ms 22 ms 23 ms 196-210-145-129.dynamic.isadsl.co.za [196.210.14
5.129]
2 56 ms 56 ms 55 ms cdsl1-rba-vl2253.ip.isnet.net [196.38.73.181]
3 56 ms 54 ms 57 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
4 57 ms 58 ms 88 ms core1b-pkl-te0-0-0-0.ip.isnet.net [196.26.0.62]

5 230 ms 237 ms 244 ms core1b-dock-really-big-l1.ip.isnet.net [168.209.
201.61]
6 226 ms 228 ms 228 ms linx-brocade1.netrino.co.uk [195.66.225.18]
7 346 ms 397 ms 399 ms h67-edge.netrino.co.uk [84.234.19.153]
8 226 ms 223 ms 246 ms hex-edge.netrino.co.uk [84.234.19.218]
9 226 ms 225 ms 225 ms bs1-core.netrino.co.uk [84.234.19.5]
10 230 ms 228 ms 227 ms bruce.ferrago.net [84.234.17.86]

Trace complete.

As you can see, Afrihost is fine, so its not my line, pc, router, telkom or some downloads running. Its Mweb. Massive timeouts as soon as 12pm hits 2 nights in a row now.

I am confused about the pathing thing, cant get it right. (its your job not mine to troubleshoot just fyi) But KEEP IN MIND that it is ping to all international sites, not just wow. Seems you keep linking me WoW stuff, while i have clearly stated multiple times that its not just wow, its ping in the cmd. I might be playing wow yes, but that isnt causing anything and its not just to the wow server, its to everything international.

So, how can I expect you to fix this? Clearly its not my line. Clearly Mweb is at fault. Only question is, will you be doing anything about this? Something happens on your network and to international at exactly 12 each night and lasts for a few hours. This is obviously unacceptable. I am awaiting your response.

Mweb Guy, still think my bandwidth profile is the issue because these were taken when i was out of WoW.

Edit: I use jolt.co.uk as a benchmark to ping in the cmd. It might not be perfect but every international site i ping shows the same result, just wanted to say this before you blame the jolt website or street lamps for your network fault.

 

[Pada]

Sillicur, I'm experiencing EXACTLY the same with my Mweb 1Mbps uncapped.
It's as if Mweb disconnects me to get their stats in order or something like that.

I'm running IS and WebAfrica accounts too, and they didn't have any issues during the same time.

My ADSL has an uptime of almost 1000 hours now, and strangely the Mweb PPPoE connection doesn't disconnect, but I can't to jack on it for a few minutes after midnight.

 

[nelis]

I'm getting timeouts right now. Can they please check it ASAP. Really annoying and I see it's only with basic accounts as our business 4mb account works fine.

I see now not even the newsserver is not working

 

[Sillicur]

I'm getting timeouts right now. Can they please check it ASAP. Really annoying and I see it's only with basic accounts as our business 4mb account works fine.

I see now not even the newsserver is not working

Seems its not just me Mweb Guy. Sad thing is guys, when i first brought this up, u know what their answer was?

"your bandwidth profile does not meet the minimum requirements for WoW"

Even thou i specifically told them its out of wow cmd ping too. Then i got ignored for a day or 2 after calling Mweb Guy out on the BS.

Hope they fix this soon and not blame it on some individual line error.

 

[nelis]

Seems its not just me Mweb Guy. Sad thing is guys, when i first brought this up, u know what their answer was?

"your bandwidth profile does not meet the minimum requirements for WoW"

Even thou i specifically told them its out of wow cmd ping too. Then i got ignored for a day or 2 after calling Mweb Guy out on the BS.

Hope they fix this soon and not blame it on some individual line error.

I agree with you. I'm getting tired with the blame game. When will they wake up. I wish they can have proper support. Right now I'm asking them and no response. I mean they must have 24/7 support via facebook, Myadsl and telephonic. I Never getting a response and this is making me so mad. I'm thinking of taking the matter further.

I think this is bs I can ping www.google.com but not www.mweb.co.za

 

[Necuno]

Type in "pathping <address>" in cmd, Ex

C:\>pathping www.google.com

Tracing route to www.l.google.com [209.85.229.99]
over a maximum of 30 hops:

I'll try to slap in a test myself sometime

Dear Mweb, at exactly 12 each night ping jumps up and there are timeouts. This is with Mweb.

Ping statistics for 84.234.17.86:
Packets: Sent = 56, Received = 46, Lost = 10 (17% loss),
Approximate round trip times in milli-seconds:
Minimum = 239ms, Maximum = 493ms, Average = 293ms


This is with afrihost:

Ping statistics for 84.234.17.86:
Packets: Sent = 37, Received = 37, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 227ms, Maximum = 251ms, Average = 230ms

This is a tracert with Mweb to Jolt.co.uk.

Tracing route to jolt.co.uk [84.234.17.86]
over a maximum of 30 hops:

1 25 ms 21 ms 23 ms 41-133-132-1.dsl.mweb.co.za [41.133.132.1]
2 298 ms 295 ms * Te1-1-0.505.cpt-ipc-1.mweb.co.za [196.28.178.178
]
3 302 ms 300 ms 301 ms Vlan92.cpt-hscore-1.mweb.co.za [196.28.179.11]
4 297 ms * 307 ms TenGigE0-2-0-0.11.cpt-up-1.mweb.co.za [196.28.17
8.97]
5 458 ms 461 ms 460 ms pos0-0-3-0.lon-up-1.mweb.co.za [196.22.164.2]
6 592 ms 636 ms 502 ms linx-extreme1.netrino.co.uk [195.66.227.18]
7 451 ms 453 ms * thn-edge.netrino.co.uk [84.234.19.142]
8 464 ms * 468 ms hex-edge.netrino.co.uk [84.234.19.146]
9 467 ms 467 ms 462 ms bs1-core.netrino.co.uk [84.234.19.5]
10 465 ms * * bruce.ferrago.net [84.234.17.86]
11 458 ms 461 ms 460 ms bruce.ferrago.net [84.234.17.86]

Trace complete.

Now, for a tracert with afrihost to jolt.co.uk.

Tracing route to jolt.co.uk [84.234.17.86]
over a maximum of 30 hops:

1 22 ms 22 ms 23 ms 196-210-145-129.dynamic.isadsl.co.za [196.210.14
5.129]
2 56 ms 56 ms 55 ms cdsl1-rba-vl2253.ip.isnet.net [196.38.73.181]
3 56 ms 54 ms 57 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
4 57 ms 58 ms 88 ms core1b-pkl-te0-0-0-0.ip.isnet.net [196.26.0.62]

5 230 ms 237 ms 244 ms core1b-dock-really-big-l1.ip.isnet.net [168.209.
201.61]
6 226 ms 228 ms 228 ms linx-brocade1.netrino.co.uk [195.66.225.18]
7 346 ms 397 ms 399 ms h67-edge.netrino.co.uk [84.234.19.153]
8 226 ms 223 ms 246 ms hex-edge.netrino.co.uk [84.234.19.218]
9 226 ms 225 ms 225 ms bs1-core.netrino.co.uk [84.234.19.5]
10 230 ms 228 ms 227 ms bruce.ferrago.net [84.234.17.86]

Trace complete.

As you can see, Afrihost is fine, so its not my line, pc, router, telkom or some downloads running. Its Mweb. Massive timeouts as soon as 12pm hits 2 nights in a row now.

I am confused about the pathing thing, cant get it right. (its your job not mine to troubleshoot just fyi) But KEEP IN MIND that it is ping to all international sites, not just wow. Seems you keep linking me WoW stuff, while i have clearly stated multiple times that its not just wow, its ping in the cmd. I might be playing wow yes, but that isnt causing anything and its not just to the wow server, its to everything international.

So, how can I expect you to fix this? Clearly its not my line. Clearly Mweb is at fault. Only question is, will you be doing anything about this? Something happens on your network and to international at exactly 12 each night and lasts for a few hours. This is obviously unacceptable. I am awaiting your response.

Mweb Guy, still think my bandwidth profile is the issue because these were taken when i was out of WoW.

Edit: I use jolt.co.uk as a benchmark to ping in the cmd. It might not be perfect but every international site i ping shows the same result, just wanted to say this before you blame the jolt website or street lamps for your network fault.

 

[nelis]

So can MWEb please tell us what was wrong last night?

 

[Sillicur]

So can MWEb please tell us what was wrong last night?

When you show them the proof and a few users complain its normally silence from them for awhile. Almost always like that. Even thou Mweb Guy is online and have read all this.

 

[MWEBHelp]

Sillicur, I'm experiencing EXACTLY the same with my Mweb 1Mbps uncapped.
It's as if Mweb disconnects me to get their stats in order or something like that.

I'm running IS and WebAfrica accounts too, and they didn't have any issues during the same time.

My ADSL has an uptime of almost 1000 hours now, and strangely the Mweb PPPoE connection doesn't disconnect, but I can't to jack on it for a few minutes after midnight.

So can MWEb please tell us what was wrong last night?

When you show them the proof and a few users complain its normally silence from them for awhile. Almost always like that. Even thou Mweb Guy is online and have read all this.

Hi guys,

@Sillicur, thank you for the traceroute and ping results, this will assist as I will be sending it off to the relevant department to look into.

@Nelis and @Pada, if it happens again, please do a traceroute and ping test and provide me the results so I can add it to the information provide by Sillicur.

Regards,
MWEB Guy

 

[Gargmel]

Skype messages (text) not going through....

 

[sand_man]

Skype messages (text) not going through....

Intermittent issue not just today but forever... Most likely related to Skype...

 

[Pada]

Thanks MWEB Guy.

I'll post traceroute (mtr) and ping results the next time this happens.

My Mweb Internet connection had absolutely no access, and not just very high latencies around 00:20.

What I do know was that when I did a traceroute to www.mweb.co.za, just after my Mweb Internet access came back online again, that the latency on the third hop was like 100ms, instead of just 11.
Here's how it looks now, which is perfect:

                                       Packets               Pings
 Host                                Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 192.168.11.1                      0.0%    14    0.9   0.9   0.8   1.1   0.1
 2. 41.132.44.1                       0.0%    14   10.3  10.6   9.6  11.2   0.5
 3. 196.28.178.202                    0.0%    14   11.5  12.2  11.4  15.2   1.0
 4. 196.28.179.11                     0.0%    13   11.4  13.2  11.4  25.0   3.6
 5. 196.28.178.66                     0.0%    13   13.4  13.9  13.1  15.0   0.5
 6. 196.41.144.35                     0.0%    13   12.7  12.8  11.6  14.8   0.9
 7. 196.2.63.110                      0.0%    13   15.8  13.8  12.4  21.8   2.5

 

[Sillicur]

FFS MWEB, now it happens during the day too.

Reply from 84.234.17.86: bytes=32 time=189ms TTL=119
Request timed out.
Reply from 84.234.17.86: bytes=32 time=188ms TTL=119
Reply from 84.234.17.86: bytes=32 time=186ms TTL=119
Reply from 84.234.17.86: bytes=32 time=190ms TTL=119
Reply from 84.234.17.86: bytes=32 time=197ms TTL=119
Request timed out.
Reply from 84.234.17.86: bytes=32 time=192ms TTL=119
Reply from 84.234.17.86: bytes=32 time=188ms TTL=119
Reply from 84.234.17.86: bytes=32 time=189ms TTL=119
Reply from 84.234.17.86: bytes=32 time=197ms TTL=119
Reply from 84.234.17.86: bytes=32 time=191ms TTL=119
Reply from 84.234.17.86: bytes=32 time=187ms TTL=119
Reply from 84.234.17.86: bytes=32 time=186ms TTL=119
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 84.234.17.86: bytes=32 time=188ms TTL=119

Mweb Guy, how long before this gets sorted out? Or is this going to take weeks again? Huh? You guys should be working on this right now.

 

[MWEBHelp]

FFS MWEB, now it happens during the day too.

Reply from 84.234.17.86: bytes=32 time=189ms TTL=119
Request timed out.
Reply from 84.234.17.86: bytes=32 time=188ms TTL=119
Reply from 84.234.17.86: bytes=32 time=186ms TTL=119
Reply from 84.234.17.86: bytes=32 time=190ms TTL=119
Reply from 84.234.17.86: bytes=32 time=197ms TTL=119
Request timed out.
Reply from 84.234.17.86: bytes=32 time=192ms TTL=119
Reply from 84.234.17.86: bytes=32 time=188ms TTL=119
Reply from 84.234.17.86: bytes=32 time=189ms TTL=119
Reply from 84.234.17.86: bytes=32 time=197ms TTL=119
Reply from 84.234.17.86: bytes=32 time=191ms TTL=119
Reply from 84.234.17.86: bytes=32 time=187ms TTL=119
Reply from 84.234.17.86: bytes=32 time=186ms TTL=119
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 84.234.17.86: bytes=32 time=188ms TTL=119

Mweb Guy, how long before this gets sorted out? Or is this going to take weeks again? Huh? You guys should be working on this right now.

Hi Sillicur,

Pelase note that I have replicated your pings and tracert results on our test bench. I have sent them to our network team for some assistance.

Kind regards, MWEB Guy

 

[Spartaniz]

is there some sort of network maintenance going on? I cant connect to the mweb news server or news demon servers.