MWEB Uncapped Subscribers Feedback

[Rosaudio]

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

  1     1 ms     1 ms     1 ms  . [192.168.2.1]
  2     *        *        *     Request timed out.
  3   117 ms   117 ms   119 ms  tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.16
9.170]
  4   118 ms   129 ms   193 ms  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
  5   154 ms   136 ms   136 ms  tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
  6   116 ms   120 ms   118 ms  tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]

  7   343 ms   340 ms   354 ms  pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]

...Trace complete.

Surely thats still quite high, at hop 3 and 4? Am I being pedantic?

Also getting very high hops like that

 

[MWEB]

Surely thats still quite high, at hop 3 and 4? Am I being pedantic?

Hi hambone,

Possibly Telkom are having some long-haul issues on their access network from your area. Same traceroute from JHB area ...

Tracing route to fg-in-f104.1e100.net [72.14.221.104]
over a maximum of 30 hops:

1 <1 ms <1 ms 12 ms home.gateway [192.168.1.254]
2 8 ms 8 ms 8 ms 41-133-78-1.dsl.mweb.co.za [41.133.78.1]
3 9 ms 9 ms 8 ms tengig-0-0-0-107.vic-ipc-1.mweb.co.za [196.22.169.158]
4 10 ms 9 ms 9 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 54 ms 41 ms 52 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
6 11 ms 13 ms 13 ms tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219]
7 235 ms 236 ms 237 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
... etc.

MWB.

 

[hambone]

Okay, so what would one do about it?

EDIT: And I really don't mind if you tell me to talk to telkom, as that may be a legitimate solution that wouldn't leave me chasing a snake that's already left.

 

[MWEB]

Okay, so what would one do about it?

Hi hambone,

PM MWEB Operations (direct link in my sig), they can enquire with Telkom if there are any issues in your area.

MWB.

 

[hambone]

Hi hambone,

PM MWEB Operations (direct link in my sig), they can enquire with Telkom if there are any issues in your area.

MWB.

Thanks, I shall do exactly that. This is why I stick up for you guys when things happen, I get answers.

 

[FrEaKo]

Sigh, today I connected to Quakelive server and I am pinging 120ms. WTF????

 

[Gordon_R]

Hi hambone,

Possibly Telkom are having some long-haul issues on their access network from your area. Same traceroute from JHB area ...

Tracing route to fg-in-f104.1e100.net [72.14.221.104]
over a maximum of 30 hops:

1 <1 ms <1 ms 12 ms home.gateway [192.168.1.254]
2 8 ms 8 ms 8 ms 41-133-78-1.dsl.mweb.co.za [41.133.78.1]
3 9 ms 9 ms 8 ms tengig-0-0-0-107.vic-ipc-1.mweb.co.za [196.22.169.158]
... etc.

MWB.

Several users on this thread have complained today, and for a while I had good local ping times, so its not just one person, or one area. This is between various DSLAMs and MWeb Victory Park. If MWeb is shifting responsibility for this hop onto Telkom, then we really are screwed...

 

[Chris_H]

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

  1     1 ms     1 ms     1 ms  . [192.168.2.1]
  2     *        *        *     Request timed out.
  3   117 ms   117 ms   119 ms  tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.16
9.170]
  4   118 ms   129 ms   193 ms  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
  5   154 ms   136 ms   136 ms  tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
  6   116 ms   120 ms   118 ms  tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]

  7   343 ms   340 ms   354 ms  pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]

...Trace complete.

Surely thats still quite high, at hop 3 and 4? Am I being pedantic?

My hop into the mweb network varies between 7ms and 600ms atm and a ping to the IGame server 41.213.87.22 is between 400 and 800ms

Oh, And I am in Cape Town

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

  4     *      489 ms   498 ms  41-132-48-1.dsl.mweb.co.za [41.132.48.1]
  5     *        *      532 ms  tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.169.146]
  6   549 ms   495 ms   461 ms  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
  7   474 ms   457 ms   550 ms  tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
  8   561 ms   530 ms   564 ms  tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]
  9   571 ms   494 ms   594 ms  pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
 10   801 ms   616 ms   620 ms  130.117.136.1
 11   721 ms   813 ms   808 ms  te1-2.ccr01.lon02.atlas.cogentco.com [130.117.50.138]

Trace complete.

 

[Gordon_R]

Several users on this thread have complained today, and for a while I had good local ping times, so its not just one person, or one area. This is between various DSLAMs and MWeb Victory Park.

Half an hour later my ping times have dropped from 90ms to 30ms, which seems weird. Either there is something going on that we haven't been told, or the lines are very congested during certain times. The ping times always seems to be in multiples of 30ms (never 40ms or 80ms),

Anyone else in CT down to 30ms (MWeb local) ping times?

 

[TonyA]

Just checked down to 32ms

 

[Chris_H]

ah, strange - down to 30ms as well

 

[medicnick83]

The shaping is up to crap! Enough said on that.

MWEB says they want to get someone 'senior' to contact me regarding my HORRIBLE line speeds.

To tell me what? Sorry that we shaping the shyte outta you?!?!

 

[schumi]

From their facebook page, This just in from the MWEB technical team: Good news! We are pleased to announce that we have just completed a sizeable upgrade to our IPC bandwidth. Enjoy! - PLEASE NOTE: This is not the announcement due tomorrow

 

[Gordon_R]

From their facebook page, This just in from the MWEB technical team: Good news! We are pleased to announce that we have just completed a sizeable upgrade to our IPC bandwidth. Enjoy! - PLEASE NOTE: This is not the announcement due tomorrow

Well, the MWeb rep said they were getting more bandwidth, so this is it - local bandwidth!?

I don't know why it takes them so long to announce something that we can all see is busy happeing in front of our eyes...

 

[TonyA]

Gordon R, I just ran speedtest again and guess what! I'm back in Cape Town, not Kinberly

 

[Rosaudio]

Well my speedtests are back to normal - http://www.speedtest.net/result/803772019.png

And it now indicates that I am in Cape Town instead of Kimberley

Torrents going at 100kB/s so right now im happy

 

[Gordon_R]

Gordon R, I just ran speedtest again and guess what! I'm back in Cape Town, not Kinberly

Hah-ha! The test is obviously confused by the 90ms delay, and interprets this as you living very, very far away from the Telkom exchange. LOL ;-)

I'm glad it all back to normal. Seems that grow in demand continually outstrips capacity...

 

[TonyA]

With the rain at present perhaps Kimberleys a better call

 

[ToxicBunny]

Is anyone else having issues getting to certain international sites?

Over the last few days I've been trying to get to sites like www.ifixit.com and my pc just choons me nooit....

 

[D34M0n7]

Is anyone else having issues getting to certain international sites?

Over the last few days I've been trying to get to sites like www.ifixit.com and my pc just choons me nooit....

Happens to me sometimes, all I do is unplug my router and give it 10min, connect it up again and I got full access... for a while, then I repeat the procedure.

Its strange, I know.