MWEB Uncapped ADSL Feedback

Status
Not open for further replies.
XperiAnce said:
Yikes, looks like International Bandwidth is down:

C:\Users\Michael>tracert www.rackspace.com

Tracing route to www.wip.rackspace.com [207.97.209.147]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms xxx
2 <1 ms <1 ms <1 ms xxx
3 14 ms 14 ms 13 ms xxx.dsl.mweb.co.za [xxx]
4 14 ms 13 ms 14 ms 197-80-4-94.jhb.mweb.co.za [197.80.4.94]
5 14 ms 13 ms 14 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
6 * 378 ms * tengig0-7-0-2.12.vic-p-2.mweb.co.za [196.22.169.242]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * 286 ms * xe-10-1-3.edge4.London1.Level3.net [212.113.14.121]
11 285 ms 283 ms * ae-52-52.csw2.London1.Level3.net [4.69.139.120]
12 287 ms 280 ms 280 ms ae-56-221.ebr2.London1.Level3.net [4.69.153.129]
13 353 ms 349 ms 348 ms ae-42-42.ebr1.NewYork1.Level3.net [4.69.137.70]
14 354 ms * 359 ms ae-4-4.ebr1.NewYork2.Level3.net [4.69.141.18]
15 411 ms 643 ms 641 ms ae-3-3.ebr2.Washington1.Level3.net [4.69.132.89]
16 653 ms * 634 ms ae-72-72.csw2.Washington1.Level3.net [4.69.134.150]
17 644 ms 630 ms * ae-2-70.edge1.Washington4.Level3.net [4.69.149.79]
18 362 ms 355 ms 355 ms RACKSPACE-M.edge1.Washington4.Level3.net [4.53.112.46]
19 * 360 ms 356 ms vlan903.core3.iad1.rackspace.com [69.20.1.40]
20 360 ms 355 ms 355 ms intra-core1-core3.iad1.rackspace.com [69.20.1.82]
21 * * 355 ms core5-iad2-iad1-distro1.iad2.rackspace.net [72.4.122.103]
22 362 ms 355 ms 356 ms aggr301a-1-core5.iad2.rackspace.net [72.4.122.121]
23 356 ms 356 ms 356 ms www.rackspace.com [207.97.209.147]

Trace complete.
Click to expand...

Good Morning XperiAnce, your tracer completes and I cannot see any problem with regards international traffic within the tracer you have provided. There are no international links down at the moment either.
 
MWEB Guy said:
Good Morning XperiAnce, your tracer completes and I cannot see any problem with regards international traffic within the tracer you have provided. There are no international links down at the moment either.
Click to expand...

Though traceroutes are completing that's merely for ICMP packets,there seems to be a severe slowdown,and Gordon's explanation seems likely. There's no way these many people would post at the same time if it was fine ;)
 
MWEB Guy said:
Good Morning XperiAnce, your tracer completes and I cannot see any problem with regards international traffic within the tracer you have provided. There are no international links down at the moment either.
Click to expand...

You're joking right? About 8 people have all just commented saying international is down. Surely that's not a coincedence?
 
Good morning, thanks for all the feedback guys; we are looking into it and will provide feedback shortly.
 
ping -t www.twitter.com

Pinging twitter.com [199.59.149.198] with 32 bytes of data:
Reply from 199.59.149.198: bytes=32 time=516ms TTL=235
Reply from 199.59.149.198: bytes=32 time=510ms TTL=235
Reply from 199.59.149.198: bytes=32 time=506ms TTL=235
Reply from 199.59.149.198: bytes=32 time=501ms TTL=235
Reply from 199.59.149.198: bytes=32 time=456ms TTL=235
Reply from 199.59.149.198: bytes=32 time=417ms TTL=235
Reply from 199.59.149.198: bytes=32 time=417ms TTL=235
Reply from 199.59.149.198: bytes=32 time=417ms TTL=235
Click to expand...

tracert www.twitter.com

Tracing route to twitter.com [199.59.149.198]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms 10.0.0.250
2 7 ms 7 ms 8 ms xxx.dsl.mweb.co.za [xxx]
3 7 ms 7 ms 8 ms 197-80-4-70.jhb.mweb.co.za [197.80.4.70]
4 8 ms 8 ms 8 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 192 ms * * tengig0-7-0-2.12.vic-p-2.mweb.co.za [196.22.169.242]
6 188 ms * 194 ms tengig0-1-0-0.cpt-up-1.mweb.co.za [197.84.4.34]
7 * * * Request timed out.
8 * 187 ms * 176.67.177.131
9 436 ms 458 ms * xe-8-1-0.edge3.London1.Level3.net [195.50.124.133]
10 377 ms * 287 ms ae-52-52.csw2.London1.Level3.net [4.69.139.120]
11 283 ms 276 ms 273 ms ae-56-221.ebr2.London1.Level3.net [4.69.153.129]
12 349 ms 342 ms 342 ms ae-43-43.ebr1.NewYork1.Level3.net [4.69.137.74]
13 496 ms 447 ms 415 ms ae-4-4.ebr1.NewYork2.Level3.net [4.69.141.18]
14 352 ms 347 ms 347 ms ae-3-3.ebr2.Washington1.Level3.net [4.69.132.89]
15 351 ms 348 ms 348 ms ae-72-72.csw2.Washington1.Level3.net [4.69.134.150]
16 * * * Request timed out.
17 352 ms 348 ms * TWITTER-INC.edge2.Washington4.Level3.net [4.53.114.102]
18 * 412 ms * xe-0-0-0.pao1-cr1.twttr.com [199.16.159.102]
19 420 ms 433 ms 427 ms xe-0-0-0.smf1-er2.twttr.com [199.16.159.33]
20 * 418 ms 484 ms www2.twitter.com [199.59.149.198]
Click to expand...
Being routed via cape town
 
Strangely Im still connected to someone on skype internationally though, and local works fine but everything else seems dead, or horribly slow.
 
Bellville in the dumps too...
Local ping 7ms 100%, then 77% - 100% packet loss from 192.28.178.113 tengige0-3-0-0.12.cpt-up-1.mweb.co.za and onwards....

Mortiiy
 
Last edited:
I've moved to my Telkom capped and all seems fine - so its MWEB side
 
Really slow my side too - local is fine.. international terrible - major packet loss

traceroute to www.microsoft.com (207.46.131.43), 64 hops max, 52 byte packets
1 dd-wrt.localdomain (192.168.0.199) 1.353 ms 1.835 ms 2.472 ms
2 sitecom.localdomain (192.168.0.1) 2.521 ms 1.929 ms 1.298 ms
3 41-133-138-1.dsl.mweb.co.za (41.133.138.1) 9.086 ms 9.508 ms 11.206 ms
4 te1-1-0.508.cpt-ipc-1.mweb.co.za (196.28.178.190) 10.176 ms 22.455 ms 10.229 ms
5 197-84-2-2.cpt.mweb.co.za (197.84.2.2) 11.888 ms
197-84-3-2.cpt.mweb.co.za (197.84.3.2) 11.606 ms 10.424 ms
6 * * *
7 * * *
8 176.67.177.131 (176.67.177.131) 173.342 ms * *
9 * * *
10 igbtmdistc7503.msft.net (195.66.226.140) 308.959 ms 264.814 ms 259.985 ms
11 * ge-5-1-0-0.lts-64cb-1a.ntwk.msn.net (207.46.42.227) 260.457 ms *
12 * so-7-1-0-0.ash-64cb-1b.ntwk.msn.net (213.199.144.158) 340.631 ms *
13 xe-10-3-1-0.ch1-96c-1a.ntwk.msn.net (207.46.45.15) 357.381 ms 354.244 ms *
14 ge-5-3-0-0.co2-64c-1a.ntwk.msn.net (207.46.45.37) 404.265 ms 399.833 ms 403.149 ms
15 ge-0-1-0-0.wst-64cb-1a.ntwk.msn.net (207.46.43.195) 405.729 ms 413.159 ms *
....


traceroute to rackspace.com (173.203.44.122), 64 hops max, 52 byte packets
1 dd-wrt (192.168.0.199) 1.260 ms 1.570 ms 0.975 ms
2 dsl-gw (192.168.0.1) 3.528 ms 1.443 ms 1.131 ms
3 41-133-138-1.dsl.mweb.co.za (41.133.138.1) 9.876 ms 11.428 ms 9.857 ms
4 te1-1-0.508.cpt-ipc-1.mweb.co.za (196.28.178.190) 11.943 ms 10.754 ms 11.444 ms
5 197-84-3-2.cpt.mweb.co.za (197.84.3.2) 12.414 ms
197-84-2-2.cpt.mweb.co.za (197.84.2.2) 11.961 ms 11.862 ms
6 * * *
7 * * *
8 * * 176.67.177.131 (176.67.177.131) 175.090 ms
9 xe-8-1-0.edge3.london1.level3.net (195.50.124.133) 291.649 ms 259.366 ms 258.455 ms
10 ae-52-52.csw2.london1.level3.net (4.69.139.120) 278.612 ms * 262.453 ms
11 ae-57-222.ebr2.london1.level3.net (4.69.153.133) 267.297 ms 257.515 ms
ae-59-224.ebr2.london1.level3.net (4.69.153.141) 261.792 ms
12 ae-42-42.ebr1.newyork1.level3.net (4.69.137.70) 335.682 ms 330.812 ms
ae-41-41.ebr1.newyork1.level3.net (4.69.137.66) 335.884 ms
13 ae-4-4.ebr1.newyork2.level3.net (4.69.141.18) 336.358 ms * *
14 * * *
15 * * *
16 ae-6-6.ebr1.chicago2.level3.net (4.69.140.190) 366.974 ms * *
17 ae-1-51.edge1.chicago2.level3.net (4.69.138.130) 349.270 ms 352.915 ms 351.094 ms
18 * 4.71.248.54 (4.71.248.54) 354.419 ms *
19 coreb.ord1.rackspace.net (184.106.126.134) 357.434 ms 361.097 ms 356.274 ms
20 * core1-coreb.ord1.rackspace.net (184.106.126.129) 356.082 ms *
21 core1-aggr401a-1.ord1.rackspace.net (173.203.0.233) 352.104 ms 352.222 ms 353.327 ms
22 * * *
...
 
MR V said:
Chill guys MWEBGuy is sorting this out
Click to expand...

I have to disagree with this - when it was just me reporting it, we got a 'everything is fine'. More people reporting it gives Mwebguy more information (such as impact, location, ect) and allows him to diagnose quicker by getting a clear picture.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X