MWEB Uncapped ADSL Feedback - Part 2

Status
Not open for further replies.
Hey MwebGuy, any update on this problem in Durban (not sure if this is happening elsewhere) literally nothing is loading.
Pinging www.mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=479ms TTL=119
Reply from 196.2.63.110: bytes=32 time=485ms TTL=119
Reply from 196.2.63.110: bytes=32 time=462ms TTL=119
Reply from 196.2.63.110: bytes=32 time=474ms 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 = 462ms, Maximum = 485ms, Average = 475ms

C:\Users\*>tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.244.69]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms 192.168.0.1
2 9 ms 8 ms 7 ms 41-133-66-1.dsl.mweb.co.za [41.133.66.1]
3 473 ms 471 ms 473 ms 197.82.5.250
4 484 ms 461 ms 471 ms 197.82.2.3
5 653 ms 675 ms 663 ms 176.67.177.227
6 653 ms 660 ms 657 ms ldn-b5-link.telia.net [62.115.13.13]
7 622 ms 619 ms 618 ms atos-ic-151907-ldn-b5.c.telia.net [80.239.132.14
2]
8 * * * Request timed out.
9 680 ms 658 ms 659 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
10 640 ms 660 ms 648 ms 132.185.255.149
11 664 ms 659 ms 666 ms bbc-vip114.telhc.bbc.co.uk [212.58.244.69]

Trace complete.

C:\Users\*>tracert www.mybroadband.co.za

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

1 <1 ms 1 ms 1 ms 192.168.0.1
2 9 ms 8 ms 8 ms 41-133-66-1.dsl.mweb.co.za [41.133.66.1]
3 458 ms 469 ms 475 ms 197.82.5.250
4 478 ms 483 ms 488 ms 197.82.2.3
5 471 ms 485 ms 470 ms tengig0-0-0.vic-pr-1.mweb.co.za [197.80.4.141]
6 486 ms 475 ms 487 ms static161-134.netactive.co.za [196.22.161.134]
7 475 ms 489 ms 490 ms jh-cr-2.za--jh-pr-1.za.mtnns.net [196.44.0.223]

8 486 ms 492 ms 474 ms 196.44.31.99
9 477 ms 475 ms 466 ms 196.31.220.6
10 481 ms 480 ms 468 ms tengigabitethernet1-1.gw20.jnb6.za.mtnbusiness.n
et [196.31.220.23]
11 479 ms 471 ms 480 ms tengigabitethernet5-1.hr9.jnb6.za.mtnbusiness.ne
t [196.31.63.146]
12 460 ms 470 ms 441 ms core-router1.jnb2.host-h.net [196.30.213.108]
13 469 ms 447 ms 461 ms core-access-switch1-vlan1001.jnb.host-h.net [41.
72.136.53]
14 444 ms 444 ms 429 ms mybroadband.co.za [41.203.21.137]

Trace complete.

Pinging www.google.co.za [74.125.233.63] with 32 bytes of data:
Reply from 74.125.233.63: bytes=32 time=247ms TTL=54
Reply from 74.125.233.63: bytes=32 time=239ms TTL=54
Reply from 74.125.233.63: bytes=32 time=255ms TTL=53
Reply from 74.125.233.63: bytes=32 time=237ms TTL=54

Ping statistics for 74.125.233.63:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 237ms, Maximum = 255ms, Average = 244ms
 
mweb issues somewhere:

C:\Users\reactor>tracert www.steampowered.com

Tracing route to steampowered.com [208.64.202.68]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 43 ms 12 ms 12 ms 197-87-57-1.cpt.mweb.co.za [197.87.57.1]
3 18 ms 8 ms 9 ms 197-80-132-142.jhb.mweb.co.za [197.80.132.142]
4 79 ms * 12 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 191 ms 208 ms 220 ms tengig0-7-0-2.12.vic-p-1.mweb.co.za [196.22.169.
241]
6 191 ms 195 ms 208 ms pos0-3-2-0.lon-up-1.mweb.co.za [197.80.5.7]
7 191 ms 245 ms 226 ms 176.67.177.131
8 208 ms 189 ms 263 ms xe-8-1-0.edge3.London1.Level3.net [195.50.124.13
3]
9 325 ms 327 ms 325 ms vl-3601-ve-225.csw2.London1.Level3.net [4.69.166
.145]
10 353 ms 341 ms 331 ms ae-56-221.ebr2.London1.Level3.net [4.69.153.129]

11 335 ms 360 ms 336 ms ae-42-42.ebr1.NewYork1.Level3.net [4.69.137.70]

12 346 ms 356 ms 340 ms ae-48-48.ebr2.NewYork2.Level3.net [4.69.201.50]

13 329 ms 329 ms 330 ms ae-1-100.ebr2.NewYork2.Level3.net [4.69.135.254]

14 333 ms 351 ms 340 ms ae-2-2.ebr1.Chicago1.Level3.net [4.69.132.65]
15 339 ms 328 ms 328 ms ae-6-6.ebr1.Chicago2.Level3.net [4.69.140.190]
16 328 ms 327 ms 334 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
17 332 ms 422 ms 364 ms ae-2-2.ebr2.Seattle1.Level3.net [4.69.132.53]
18 338 ms 324 ms 351 ms ae-2-52.edge1.Seattle3.Level3.net [4.69.147.170]

19 350 ms 329 ms 331 ms CENTURYTEL.edge1.Seattle3.Level3.net [4.59.232.7
4]
20 346 ms 350 ms 359 ms 205.196.6.34
21 373 ms 328 ms 370 ms fw01-core.tuk.valve.net [208.64.202.21]
22 346 ms 340 ms 337 ms 208-64-202-68.valve.net [208.64.202.68]

Trace complete.

C:\Users\reactor>

C:\Users\reactor>tracert www.amazon.com

Tracing route to www.amazon.com [72.21.215.232]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 19 ms 21 ms 15 ms 197-87-57-1.cpt.mweb.co.za [197.87.57.1]
3 9 ms 9 ms 8 ms 41-86-107-6.mweb.co.za [41.86.107.6]
4 9 ms 9 ms 20 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 254 ms 241 ms 205 ms tengig0-0-0-2.11.vic-p-2.mweb.co.za [196.22.169.
226]
6 196 ms 200 ms 193 ms pos0-3-0-0.lon-up-1.mweb.co.za [197.80.5.9]
7 205 ms 260 ms 195 ms 176.67.177.131
8 210 ms 194 ms * ldn-b5-link.telia.net [62.115.13.13]
9 193 ms 229 ms 194 ms ldn-bb1-link.telia.net [80.91.247.91]
10 264 ms 274 ms 264 ms ash-bb3-link.telia.net [80.91.251.207]
11 338 ms 268 ms 268 ms ash-b1-link.telia.net [80.91.248.159]
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.

C:\Users\reactor>
 
This is becoming extremely inconvenient now. Few more episodes like this and I'll be jumping.
 
Problem is south as well, Margate!

C:\Users\BeoTeK>tracert www.steampowered.com

Tracing route to steampowered.com [208.64.202.68]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 12 ms 12 ms 15 ms 41-133-124-1.dsl.mweb.co.za [41.133.124.1]
3 14 ms 13 ms 13 ms 197.82.5.250
4 14 ms 13 ms 14 ms 197.82.2.3
5 204 ms 207 ms 207 ms 176.67.177.227
6 201 ms 209 ms 202 ms xe-8-1-0.edge3.London1.Level3.net [195.50.124.13
3]
7 344 ms 344 ms 344 ms vl-3601-ve-225.csw2.London1.Level3.net [4.69.166
.145]
8 342 ms 343 ms 342 ms ae-57-222.ebr2.London1.Level3.net [4.69.153.133]

9 344 ms 344 ms 344 ms ae-42-42.ebr1.NewYork1.Level3.net [4.69.137.70]

10 341 ms 341 ms 341 ms 4.69.201.46
11 345 ms 345 ms 345 ms ae-1-100.ebr2.NewYork2.Level3.net [4.69.135.254]

12 345 ms 343 ms 343 ms ae-2-2.ebr1.Chicago1.Level3.net [4.69.132.65]
13 343 ms 344 ms 343 ms ae-6-6.ebr1.Chicago2.Level3.net [4.69.140.190]
14 342 ms 342 ms 342 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
15 345 ms 345 ms 344 ms ae-2-2.ebr2.Seattle1.Level3.net [4.69.132.53]
16 344 ms 344 ms 344 ms ae-2-52.edge1.Seattle3.Level3.net [4.69.147.170]

17 344 ms 344 ms 344 ms CENTURYTEL.edge1.Seattle3.Level3.net [4.59.232.7
4]
18 345 ms 344 ms 344 ms 205.196.6.34
19 342 ms 343 ms 342 ms fw01-core.tuk.valve.net [208.64.202.21]
20 343 ms 342 ms 342 ms 208-64-202-68.valve.net [208.64.202.68]

Trace complete.
 
Hi Guys

Thanks for the information.

Has things improved since you guys posted? There are no confirmed issues in the Durban area.
 
Nope still no sites loading

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 8 ms 8 ms 41-133-66-1.dsl.mweb.co.za [41.133.66.1]
3 427 ms 413 ms 445 ms 197.82.5.250
4 461 ms 457 ms 471 ms 197.82.2.3
5 451 ms 453 ms 464 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
6 458 ms 437 ms 452 ms 196.28.178.66
7 412 ms 407 ms 406 ms cte-core-sw2.vwol.net [196.41.144.35]
8 402 ms 430 ms 408 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
Still borked for me too...

Tracing route to myadsl.co.za [41.203.21.137] over a maximum of 30 hops:

1 1 ms 1 ms <1 ms 192.168.144.254
2 12 ms 11 ms 12 ms 41-132-8-1.dsl.mweb.co.za [41.132.8.1]
3 376 ms 363 ms 362 ms 197.82.5.250
4 480 ms 413 ms 412 ms 197.82.2.3
 
Went Dead, came back up, then it went dead again. Just came back up now.

Im also in Durban.
 
MWEB dead in the water, KZN area.
Switched to my fallback business account (which has reduncancy) and it's okay ^
Check it out.. !
 
Hi guys

Thanks for the information.

We received similar queries. There are no confirmed issues in the Durban area. Our technician are looking into this as we speak.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X