MWEB Uncapped ADSL Feedback - Part 3

Is the Mweb news server operational?

Code:
Tracing route to news.mweb.co.za [168.209.98.66]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     7 ms     7 ms     7 ms  41-133-134-1.dsl.mweb.co.za [41.133.134.1
  3     8 ms     8 ms     7 ms  197-84-96-138.cpt.mweb.co.za [197.84.96.1
  4     9 ms     8 ms     9 ms  197-84-2-2.cpt.mweb.co.za [197.84.2.2]
  5    10 ms    11 ms    11 ms  197-84-5-226.cpt.mweb.co.za [197.84.5.226
  6     8 ms     7 ms     8 ms  197-84-7-5.cpt.mweb.co.za [197.84.7.5]
  7     9 ms     9 ms     8 ms  is.cinx.net.za [196.223.22.10]
  8     9 ms    10 ms    10 ms  168.209.6.12
  9    34 ms    34 ms    35 ms  168.209.100.13
 10    32 ms    31 ms    30 ms  168.209.1.134
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

Good morning

I have tested the news server and I am able t make use of it with no trouble.

@Mwebguy I had the same problem today and this is a dns issue. Reason it worked for you is cause you use the mweb dns servers. I had same problem tonight and was pinging news.mweb.co.za on 168.209.98.66 instead of 196.28.78.229 it should be

Just so anyone using google dns (8.8.8.8) or some other public dns may know if they experience the same issue in future - use the direct ip or change your dns.....
 
Last edited:
Now that you mention the Range Extenders...
Never received ours with the FON Router..

Hi

could you please send me your account info and I will follow up on this for you.
 
Hey is anyone else having issues with latency and throughput to youtube etc?
I started noticing it on my phone when I was watching something and it started buffering even at 240p.
I then logged on my computer to check latency and pinging local pages like mweb.co.za and google.co.za were 120ms+.
Also I seem to be getting some loss on the line so I have to assume something has gone belly up in DBN?
Pings as follows:
Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms xxx.xxx.xxx.xxx
2 11 ms 18 ms 11 ms 41-135-97-1.dsl.mweb.co.za [41.135.97.1]
3 121 ms * * 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
4 123 ms * 136 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
5 155 ms 170 ms 158 ms vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
6 188 ms * * 196.28.178.66
7 * * 157 ms cte-core-sw2.vwol.net [196.41.144.35]
8 187 ms 160 ms 155 ms www.mweb.co.za [196.2.63.110]

Anybody else?

Regards
Hellhound
 
Hey is anyone else having issues with latency and throughput to youtube etc?
I started noticing it on my phone when I was watching something and it started buffering even at 240p.
I then logged on my computer to check latency and pinging local pages like mweb.co.za and google.co.za were 120ms+.
Also I seem to be getting some loss on the line so I have to assume something has gone belly up in DBN?
Pings as follows:
Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms xxx.xxx.xxx.xxx
2 11 ms 18 ms 11 ms 41-135-97-1.dsl.mweb.co.za [41.135.97.1]
3 121 ms * * 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
4 123 ms * 136 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
5 155 ms 170 ms 158 ms vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
6 188 ms * * 196.28.178.66
7 * * 157 ms cte-core-sw2.vwol.net [196.41.144.35]
8 187 ms 160 ms 155 ms www.mweb.co.za [196.2.63.110]

Anybody else?

Regards
Hellhound

Hi Hellhound

Please provide me with your MWEb email address.
 
Hey is anyone else having issues with latency and throughput to youtube etc?
I started noticing it on my phone when I was watching something and it started buffering even at 240p.
I then logged on my computer to check latency and pinging local pages like mweb.co.za and google.co.za were 120ms+.
Also I seem to be getting some loss on the line so I have to assume something has gone belly up in DBN?
Pings as follows:
Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms xxx.xxx.xxx.xxx
2 11 ms 18 ms 11 ms 41-135-97-1.dsl.mweb.co.za [41.135.97.1]
3 121 ms * * 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
4 123 ms * 136 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
5 155 ms 170 ms 158 ms vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
6 188 ms * * 196.28.178.66
7 * * 157 ms cte-core-sw2.vwol.net [196.41.144.35]
8 187 ms 160 ms 155 ms www.mweb.co.za [196.2.63.110]

Anybody else?

Regards
Hellhound

Lotsa Int latency, Durban shyte again methinks .......

Hi Mephisto_Helix

Please provide me with tracert results.

I am aware of others also mentioning a Durban issue. We are in the process of trying to find out if it is form our Network or not.
 
Just my input. Im not on mweb but am having issues with both my other ISPs. My friend on Mweb has the same issues so i think it may just be a KZN telkom fault.
 
Just my input. Im not on mweb but am having issues with both my other ISPs. My friend on Mweb has the same issues so i think it may just be a KZN telkom fault.

Hi Bar_Rat

Any input is appreciated.

It helps with understanding a bigger possible picture ;-)
 
Pings on int servers double what they are usually both MWeb and Telkom isp accounts.

Always Dirtbin it seems :sick:

Tracing route to d-216-52-148-29.ded-machine.internap-chicago.nfoservers.com [21
6.52.148.29]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 10 ms 10 ms 41-133-72-1.dsl.mweb.co.za [41.133.72.1]
3 74 ms 74 ms 75 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
4 74 ms 74 ms 76 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
5 273 ms 274 ms 274 ms be-3-779-thd-up-1.mweb.co.za [176.67.177.227]
6 273 ms 272 ms 272 ms ldn-b5-link.telia.net [62.115.13.13]
7 272 ms 273 ms 271 ms ldn-bb1-link.telia.net [80.91.246.96]
8 * 414 ms 343 ms nyk-bb1-link.telia.net [213.155.135.69]
9 363 ms 360 ms 362 ms chi-b21-link.telia.net [62.115.137.31]
10 360 ms 362 ms 360 ms internap-ic-150762-chi-b21.c.telia.net [213.248.
81.142]
11 361 ms 360 ms 359 ms border5.po2-bbnet2.chg.pnap.net [64.94.32.74]
12 368 ms 366 ms 366 ms d-216-52-148-29.ded-machine.internap-chicago.nfo
servers.com [216.52.148.29]

Trace complete.

Ingame its 450+ normaly 250-300
 
Last edited:
Switched back to the tar-net to provide a tracert ....... other networks are fine at the moment.


C:\Users\Andre>tracert ddo.com

Tracing route to ddo.com [74.201.103.121]
over a maximum of 30 hops:

1 5 ms 5 ms 5 ms 41-133-124-1.dsl.mweb.co.za [41.133.124.1]
2 70 ms 69 ms 69 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
3 70 ms 68 ms 68 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
4 269 ms 268 ms 272 ms be-3-779-thd-up-1.mweb.co.za [176.67.177.227]
5 265 ms 267 ms 267 ms ldn-b5-link.telia.net [62.115.13.13]
6 260 ms 262 ms 261 ms cogent-ic-125507-ldn-b4.c.telia.net [213.248.70.
238]
7 268 ms 268 ms 268 ms be2398.ccr22.lon01.atlas.cogentco.com [130.117.5
1.210]
8 267 ms 266 ms 266 ms be2494.ccr42.lon13.atlas.cogentco.com [154.54.39
.130]
9 345 ms 345 ms 345 ms be2493.ccr22.bos01.atlas.cogentco.com [154.54.42
.97]
10 342 ms 343 ms 342 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
11 342 ms 344 ms 347 ms 38.122.52.50
12 342 ms 343 ms 344 ms border1.te7-1-bbnet1.bsn003.pnap.net [63.251.128
.43]
13 338 ms * 337 ms turbine-7.border1.bsn003.pnap.net [64.95.76.202]

14 338 ms 337 ms 348 ms 74.201.102.154
15 342 ms 343 ms 343 ms 74.201.103.121

Trace complete.

Ingame to DDO is usually 270-300, tonight it's 400+ with packet loss thrown in.
 
Why are Steam downloads being throttled? If we're downloading from the MWeb server it should be local bandwidth.

I'm on a premium uncapped account


Hi TheLaggingShaman

You are not currently being speed limited.

All download usage is calculated against the threshold regardless of the type of usage.
 
Is Durban ever going to go a few nights without some bloody BS, seriously :mad:



C:\Users\Andre>tracert mweb.co.za

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

1 5 ms 5 ms 5 ms 41-133-124-1.dsl.mweb.co.za [41.133.124.1]
2 7 ms 6 ms 7 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
3 8 ms 6 ms 7 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
4 45 ms 43 ms 43 ms vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
5 51 ms 63 ms 48 ms 196.28.178.66
6 46 ms 45 ms 45 ms cte-core-sw2.vwol.net [196.41.144.35]
7 45 ms 45 ms 46 ms www.mweb.co.za [196.2.63.110]

Trace complete.

C:\Users\Andre>ping 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=325ms TTL=119
Reply from 196.2.63.110: bytes=32 time=352ms TTL=119
Reply from 196.2.63.110: bytes=32 time=379ms TTL=119
Reply from 196.2.63.110: bytes=32 time=389ms TTL=119

Ping statistics for 196.2.63.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 325ms, Maximum = 389ms, Average = 361ms

C:\Users\Andre>tracert ddo.com

Tracing route to ddo.com [74.201.103.121]
over a maximum of 30 hops:

1 5 ms 5 ms 5 ms 41-133-124-1.dsl.mweb.co.za [41.133.124.1]
2 443 ms 442 ms 444 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
3 451 ms 440 ms 428 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
4 629 ms 633 ms 641 ms be-3-777-thd-up-1.mweb.co.za [176.67.177.131]
5 640 ms 634 ms 632 ms ldn-b5-link.telia.net [62.115.13.13]
6 635 ms 626 ms 622 ms cogent-ic-125507-ldn-b4.c.telia.net [213.248.70.
238]
7 635 ms 629 ms 635 ms be2350.ccr41.lon13.atlas.cogentco.com [154.54.39
.185]
8 644 ms 641 ms 627 ms be2286.ccr42.lon13.atlas.cogentco.com [130.117.5
0.246]
9 706 ms 713 ms 716 ms be2493.ccr22.bos01.atlas.cogentco.com [154.54.42
.97]
10 713 ms 718 ms 715 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
11 709 ms 704 ms 712 ms 38.122.52.50
12 706 ms 708 ms 710 ms border1.te8-1-bbnet2.bsn003.pnap.net [63.251.128
.107]
13 713 ms 706 ms 714 ms turbine-7.border1.bsn003.pnap.net [64.95.76.202]

14 622 ms 616 ms 614 ms 74.201.102.154
15 704 ms 700 ms 708 ms 74.201.103.121

Trace complete.
 
Is Durban ever going to go a few nights without some bloody BS, seriously :mad:

Evening Mephisto_Helix, the 2nd hop on the trace to ddo is quite high.

If you do a trace to bbc.co.uk is the result similar?
 
I have been experience sluggish internet last few days. Can you do a reset or something please.

(Sluggish as in websites not loading sometimes, or really slow. Disconnections from games)
 
Evening Mephisto_Helix, the 2nd hop on the trace to ddo is quite high.

If you do a trace to bbc.co.uk is the result similar?

yep, it's all messed up until I switch to another provider and the hops are fine :(
 
Top
Sign up to the MyBroadband newsletter
X