MWEB Uncapped ADSL Feedback - Part 2

Status
Not open for further replies.
YouTube is completely unusable. My speed test results are good, 1.49Mbps down, yet I cannot even stream 240p youtube. Mweb's network is badly broken. Time to sign up with a non broken ISP
 
YouTube is completely unusable. My speed test results are good, 1.49Mbps down, yet I cannot even stream 240p youtube. Mweb's network is badly broken. Time to sign up with a non broken ISP

AH is also broken at the moment. MWEB is actually faster.
 
YouTube is completely unusable. My speed test results are good, 1.49Mbps down, yet I cannot even stream 240p youtube. Mweb's network is badly broken. Time to sign up with a non broken ISP
Try again. Seems like today after 9:00PM youtube doesn't buffer anymore.
 
I am really tired of this **** tonight. I think the camel's back is broken. I have had no to limited internet connectivity tonight.

I actually miss dial up! That was more reliable and less costly than this. And at present, also faster.
 
C:\>tracert google.com

Tracing route to google.com [173.194.34.167]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.254
2 933 ms 1043 ms * 41-133-102-1.dsl.mweb.co.za [41.133.102.1]
3 785 ms 754 ms 754 ms 197-84-8-58.cpt.mweb.co.za [197.84.8.58]
4 541 ms 390 ms 370 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 713 ms 761 ms 845 ms tengige0-0-0-2.11.cpt-p-1.mweb.co.za [196.28.178
.97]
6 875 ms 769 ms * 197-84-4-193.cpt.mweb.co.za [197.84.4.193]
7 1052 ms * 839 ms 176.67.177.131
8 * 1029 ms 934 ms 176.67.177.133
9 1135 ms 1225 ms 1147 ms 176.67.177.255
10 1054 ms 940 ms 858 ms 209.85.240.63
11 835 ms 811 ms 738 ms 209.85.253.175
12 959 ms * * lhr14s22-in-f7.1e100.net [173.194.34.167]
13 * 849 ms 951 ms lhr14s22-in-f7.1e100.net [173.194.34.167]

Trace complete.
 
C:\>tracert google.com

Tracing route to google.com [173.194.34.167]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.254
2 933 ms 1043 ms * 41-133-102-1.dsl.mweb.co.za [41.133.102.1]
3 785 ms 754 ms 754 ms 197-84-8-58.cpt.mweb.co.za [197.84.8.58]
4 541 ms 390 ms 370 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 713 ms 761 ms 845 ms tengige0-0-0-2.11.cpt-p-1.mweb.co.za [196.28.178
.97]
6 875 ms 769 ms * 197-84-4-193.cpt.mweb.co.za [197.84.4.193]
7 1052 ms * 839 ms 176.67.177.131
8 * 1029 ms 934 ms 176.67.177.133
9 1135 ms 1225 ms 1147 ms 176.67.177.255
10 1054 ms 940 ms 858 ms 209.85.240.63
11 835 ms 811 ms 738 ms 209.85.253.175
12 959 ms * * lhr14s22-in-f7.1e100.net [173.194.34.167]
13 * 849 ms 951 ms lhr14s22-in-f7.1e100.net [173.194.34.167]

Trace complete.


C:\>tracert google.com

Tracing route to google.com [173.194.34.167]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.254
2 933 ms 1043 ms * 41-133-102-1.dsl.mweb.co.za [41.133.102.1]
3 785 ms 754 ms 754 ms 197-84-8-58.cpt.mweb.co.za [197.84.8.58]
4 541 ms 390 ms 370 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 713 ms 761 ms 845 ms tengige0-0-0-2.11.cpt-p-1.mweb.co.za [196.28.178
.97]
6 875 ms 769 ms * 197-84-4-193.cpt.mweb.co.za [197.84.4.193]
7 1052 ms * 839 ms 176.67.177.131
8 * 1029 ms 934 ms 176.67.177.133
9 1135 ms 1225 ms 1147 ms 176.67.177.255
10 1054 ms 940 ms 858 ms 209.85.240.63
11 835 ms 811 ms 738 ms 209.85.253.175
12 959 ms * * lhr14s22-in-f7.1e100.net [173.194.34.167]
13 * 849 ms 951 ms lhr14s22-in-f7.1e100.net [173.194.34.167]

Trace complete.
 
Cape Town area as well, first hop in tracert is also crazy.

A lot of people will tell you that it's overcongested exchange but everyone is complaining of lag in GW2 tonight across multiple ISPs.
 
C:\>tracert google.com

Tracing route to google.com [173.194.34.167]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.254
2 933 ms 1043 ms * 41-133-102-1.dsl.mweb.co.za [41.133.102.1]
3 785 ms 754 ms 754 ms 197-84-8-58.cpt.mweb.co.za [197.84.8.58]
4 541 ms 390 ms 370 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 713 ms 761 ms 845 ms tengige0-0-0-2.11.cpt-p-1.mweb.co.za [196.28.178
.97]
6 875 ms 769 ms * 197-84-4-193.cpt.mweb.co.za [197.84.4.193]
7 1052 ms * 839 ms 176.67.177.131
8 * 1029 ms 934 ms 176.67.177.133
9 1135 ms 1225 ms 1147 ms 176.67.177.255
10 1054 ms 940 ms 858 ms 209.85.240.63
11 835 ms 811 ms 738 ms 209.85.253.175
12 959 ms * * lhr14s22-in-f7.1e100.net [173.194.34.167]
13 * 849 ms 951 ms lhr14s22-in-f7.1e100.net [173.194.34.167]

Trace complete.

C:\>tracert google.com

Tracing route to google.com [173.194.34.167]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.254
2 933 ms 1043 ms * 41-133-102-1.dsl.mweb.co.za [41.133.102.1]
3 785 ms 754 ms 754 ms 197-84-8-58.cpt.mweb.co.za [197.84.8.58]
4 541 ms 390 ms 370 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 713 ms 761 ms 845 ms tengige0-0-0-2.11.cpt-p-1.mweb.co.za [196.28.178
.97]
6 875 ms 769 ms * 197-84-4-193.cpt.mweb.co.za [197.84.4.193]
7 1052 ms * 839 ms 176.67.177.131
8 * 1029 ms 934 ms 176.67.177.133
9 1135 ms 1225 ms 1147 ms 176.67.177.255
10 1054 ms 940 ms 858 ms 209.85.240.63
11 835 ms 811 ms 738 ms 209.85.253.175
12 959 ms * * lhr14s22-in-f7.1e100.net [173.194.34.167]
13 * 849 ms 951 ms lhr14s22-in-f7.1e100.net [173.194.34.167]

Trace complete.


C:\>tracert google.com

Tracing route to google.com [173.194.34.167]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.254
2 933 ms 1043 ms * 41-133-102-1.dsl.mweb.co.za [41.133.102.1]
3 785 ms 754 ms 754 ms 197-84-8-58.cpt.mweb.co.za [197.84.8.58]
4 541 ms 390 ms 370 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 713 ms 761 ms 845 ms tengige0-0-0-2.11.cpt-p-1.mweb.co.za [196.28.178
.97]
6 875 ms 769 ms * 197-84-4-193.cpt.mweb.co.za [197.84.4.193]
7 1052 ms * 839 ms 176.67.177.131
8 * 1029 ms 934 ms 176.67.177.133
9 1135 ms 1225 ms 1147 ms 176.67.177.255
10 1054 ms 940 ms 858 ms 209.85.240.63
11 835 ms 811 ms 738 ms 209.85.253.175
12 959 ms * * lhr14s22-in-f7.1e100.net [173.194.34.167]
13 * 849 ms 951 ms lhr14s22-in-f7.1e100.net [173.194.34.167]

Trace complete.

Morning straatkat

From these results it is clear that things spike from from the 2nd hop. That points to a congested exchange you are connecting too.

I suggest contacting Telkom, provide them these results as well so that they can look into why the exchange is congested.
 
Cape Town area as well, first hop in tracert is also crazy.

A lot of people will tell you that it's overcongested exchange but everyone is complaining of lag in GW2 tonight across multiple ISPs.

Morning StevenC

Can you please do a traceroute to a local and international site so that I can see the results you are getting.
 
Egypt's coastguard caught three divers cutting through an undersea Internet cable on Wednesday, the army said, the first suggestion criminals might be involved in days of severed connections and disruptions online.
 
I actually miss dial up! That was more reliable and less costly than this. And at present, also faster.
You're speaking the biggest load of horse **** ever. You're mad, I'll let it slide and assume you're actually a smarter-than-average person just venting
 
Egypt's coastguard caught three divers cutting through an undersea Internet cable on Wednesday, the army said, the first suggestion criminals might be involved in days of severed connections and disruptions online.

They should be shot on sight
 
According to Afrihost, Telkom did some work on an IPC in Cape Town recently and, this morning, 'were moving over to (the) upgraded IPC'.
Maybe that's responsible for those of us connecting via Cape Town having such latency issues this morning...
 
You're speaking the biggest load of horse **** ever. You're mad, I'll let it slide and assume you're actually a smarter-than-average person just venting


Actually, if you look at the speed test, you will have noticed that a dial up was faster last night. As for the total costs, a 4 meg line and uncap internet = R1149, which is almost twice as much as I used to pay for my dial up connection.

I am just really tired of this, that is all. I had Telkom looked at the line, I have had Mweb looked at it. I have bought two new routers, replaced cables and I cant even open a freaken webpage this morning before I left home.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X