MWEB Uncapped ADSL Feedback - Part 2

Status
Not open for further replies.
Kenilworth
021 761
getting 150+ ping in the MWEB BF3 AK server where normally I get less than 10
tracert 152.111.192.230

Tracing route to 152.111.192.230 over a maximum of 30 hops

1 2 ms 1 ms 1 ms unknown [192.168.1.1]
2 7 ms 8 ms 9 ms 41-132-74-1.dsl.mweb.co.za [41.132.74.1]
3 78 ms 80 ms 77 ms te1-1-0.508.cpt-ipc-1.mweb.co.za [196.28.178.190]
4 157 ms 154 ms * 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 175 ms 170 ms 172 ms 196.28.178.70
6 164 ms 162 ms 162 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]
7 162 ms 157 ms 162 ms 152.111.192.230
 
Last edited:
Thanks for all the info guys, I will proivde it to the relevant persons.
As soon as I know anything I will let you know.
 
Sunday night and no gaming for me...

Hope the ping issues get sorted soon "crosses fingers"
 
021 671

Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms login.router [10.0.0.2]
2 8 ms 7 ms 7 ms 41-133-112-1.dsl.mweb.co.za [41.133.112.1]
3 110 ms 109 ms 108 ms 197-84-8-34.cpt.mweb.co.za [197.84.8.34]
4 212 ms 211 ms 213 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 218 ms 214 ms 216 ms 196.28.178.66
6 217 ms 232 ms 220 ms cte-core-sw2.vwol.net [196.41.144.35]
7 212 ms 215 ms 227 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
Location: Plumstead, Cape Town
021
Ping: 400 to 650ms in GW2 (obtained through resource monitor).

Quite a bad experience this evening, luckily not doing WvWvW
 
Cape Town
7441
ping 259 to MWEB Cape Town
download 0.25Mb/sec

I think what I was seeing earlier today was the prelude to this.
 
Hey guys,

Thanks for all the feedback.
I have logged this issue with our engineers. I still have not received any feedback.
I will post an update as soon as I have some feedback.
 
70434015.png


Code: 
ping -n 30 mweb.co.za

Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=268ms TTL=122
Reply from 196.2.63.110: bytes=32 time=263ms TTL=122
Reply from 196.2.63.110: bytes=32 time=266ms TTL=122
Request timed out.
Reply from 196.2.63.110: bytes=32 time=272ms TTL=122
Reply from 196.2.63.110: bytes=32 time=267ms TTL=122
Reply from 196.2.63.110: bytes=32 time=270ms TTL=122
Reply from 196.2.63.110: bytes=32 time=268ms TTL=122
Reply from 196.2.63.110: bytes=32 time=265ms TTL=122
Reply from 196.2.63.110: bytes=32 time=266ms TTL=122
Reply from 196.2.63.110: bytes=32 time=267ms TTL=122
Reply from 196.2.63.110: bytes=32 time=264ms TTL=122
Reply from 196.2.63.110: bytes=32 time=262ms TTL=122
Reply from 196.2.63.110: bytes=32 time=268ms TTL=122
Reply from 196.2.63.110: bytes=32 time=270ms TTL=122
Reply from 196.2.63.110: bytes=32 time=268ms TTL=122
Reply from 196.2.63.110: bytes=32 time=271ms TTL=122
Reply from 196.2.63.110: bytes=32 time=268ms TTL=122
Reply from 196.2.63.110: bytes=32 time=270ms TTL=122
Reply from 196.2.63.110: bytes=32 time=272ms TTL=122
Reply from 196.2.63.110: bytes=32 time=265ms TTL=122
Reply from 196.2.63.110: bytes=32 time=270ms TTL=122
Reply from 196.2.63.110: bytes=32 time=270ms TTL=122
Reply from 196.2.63.110: bytes=32 time=271ms TTL=122
Reply from 196.2.63.110: bytes=32 time=274ms TTL=122
Reply from 196.2.63.110: bytes=32 time=261ms TTL=122
Reply from 196.2.63.110: bytes=32 time=254ms TTL=122
Reply from 196.2.63.110: bytes=32 time=254ms TTL=122
Reply from 196.2.63.110: bytes=32 time=251ms TTL=122
Reply from 196.2.63.110: bytes=32 time=256ms TTL=122

Ping statistics for 196.2.63.110:
    Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
    Minimum = 251ms, Maximum = 274ms, Average = 265ms

Just adding another voice to the cacophony :)
 
Also...

is it my imagination or are the pings getting progressively higher?
 
I'm also experiencing the exact same issues as all the other users in Stellenbosch:

From WebAfrica account to WebAfrica server:
Code: 
Tracing route to vl306.er.gw.cpt.za.wa.co.za [41.185.60.1]
over a maximum of 30 hops:

  1     1 ms    <1 ms     1 ms  mikrotik.tuis.local [192.168.11.1]
  2    10 ms    10 ms    10 ms  wbs-ip-esr-4.ipnet.wa.co.za [41.185.86.1]
  3    12 ms    12 ms    12 ms  wnls-ipc1-vl-105.wa.co.za [196.220.59.250]
  4    13 ms    13 ms    14 ms  vl306.er.gw.cpt.za.wa.co.za [41.185.60.1]

From MWEB account to WebAfrica server:
Code: 
Tracing route to vl306.er.gw.cpt.za.wa.co.za [41.185.60.1]
over a maximum of 30 hops:

  1     1 ms    <1 ms     1 ms  mikrotik.tuis.local [192.168.11.1]
  2    11 ms    10 ms     9 ms  41-132-44-1.dsl.mweb.co.za [41.132.44.1]
  3    83 ms    81 ms    82 ms  196-28-178-234.adsl.mweb.co.za [196.28.178.234]
  4   177 ms   173 ms   172 ms  197-84-3-2.cpt.mweb.co.za [197.84.3.2]
  5   170 ms   173 ms   174 ms  tengige0-7-0-2.12.cpt-p-2.mweb.co.za [196.28.178.114]
  6   169 ms   174 ms   176 ms  tengig0-0-0.cpt-pr-2.mweb.co.za [197.84.4.165]
  7   159 ms   159 ms   155 ms  vl306.er.gw.cpt.za.wa.co.za [41.185.60.1]
... where it is usually around 15-20ms from my MWEB account.
 
Handz said:
Also...

is it my imagination or are the pings getting progressively higher?
Click to expand...
Nope, you were right!

From Stellenbosch to Amazon EC2 (US East): * Click thumbnails for full scale images.


From Stellenbosch to Google CINX:


These graphs indicate that the latency gradually increased from 15:00 - 20:00, and was then restored at around 21:30.

Interestingly enough my 10MB SSH download speed (which I'm scheduling every 30 minutes) from Amazon EC2 to MWEB remained at about 170-180KB/s on my 2Mbps MWEB uncapped account!
 
Macabre25 said:
Mine is fixed, pings back to 10ms to mweb server
Click to expand...

Hi

Thanks for the feedback, appreciate it.

Everything should be back to normal again, I have received word from our engineers :)
 
Hi Guys

Really sorry about the horrid latency for Cape Town over the weekend. :( We had a routine capacity upgrade on the Cape Town IPC link which for obscure reasons that only the Cisco engineers can fully explain caused one of our core routers in Cape Town to run high latency.

It took some back and forth between our engineers and Telkom to isolate the problem, but it was eventually resolved yesterday evening.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X