South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
I still get decent speeds on torrents... Though I do have to wonder, why does Mweb not shape uploads?
Can you guys download from your downstorm vault with your Mweb account currently? I can't.
Hi Mweb Operations
I've got an Mweb business uncapped 4mbit line with static IPs.
I've been getting fairly constants speeds just in excess of 220KB/sec since I got the line. I don't think it goes faster than that because of my Telkom line. So far the service has been pretty good... but about two days ago things went a bit odd.
Lately my line has really slowed down. Some HTTP downloads keep failing (in Firefox they'll show as complete, but at a fraction of their size). Wget retries multiple times.
A test on speedtest.net using the JHB option gives me a rating of 0.58mbit download and 0.39mbit upload, with a latency of 95ms.
Downloads from international sites (distfiles.gentoo.org and netbsd tested) don't seem to exceed 40KB/sec.
Is there a failure on Seacom ? has someone flipped the switch on my line ?
The router doesn't lose Carrier Detect/doesn't drop the line.
Thanks
P.S. It's quite progressive for Mweb for have a rep on here.
P.P.S. I've just tried the same download via ssh on my office PCs (they're on a piddly 384k line) and I'm getting around 32KB/sec, the same download was running at 22KB/sec on my 4mbit line. (File : http://distfiles.gentoo.org/distfiles/bash-3.2-patched.tar.gz)
P.P.S. Murphy's law ? Now files are coming in, from the same international servers via http at between 90KB/sec and 220KB/sec. Speedtest now reports a download speed of 1.85mbit/sec, latency of 64ms and upload of 0.41mbit.
@ MWEB operations
Could you please look into my DC++ problem?
@MWEB
nvm, shortly after I sent the pm's I realised I had made a id10T error, murphy in all his glory, all working fine now. :blush:
Hi MWEB,
The site:
http://sms.postoffice.co.za/tracking/Parcel.aspx
Does not seem to load completely (times out).
It however loads perfectly if I use a VPN connection.
Ta,
P.
Tracing route to sms.postoffice.co.za [165.8.60.15]
over a maximum of 30 hops:
1 5 ms <1 ms 3 ms 192.168.0.1
2 * * * Request timed out.
3 33 ms 32 ms 31 ms tengig-0-0-0-101.vic-ipc-1.mweb.co.za [196.22.16
9.134]
4 32 ms 32 ms 32 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 33 ms 34 ms 37 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.16
9.225]
6 32 ms 32 ms 31 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.
249]
7 32 ms 32 ms 32 ms tpr-ip-esr-3-gig-6-0-0.telkom-ipnet.co.za [196.4
3.25.54]
8 230 ms 207 ms 199 ms sapos-gw.telkom-ipnet.co.za [196.25.191.34]
9 37 ms 37 ms 37 ms 165.8.15.17
10 38 ms 37 ms 38 ms 165.8.13.3
11 * 38 ms 37 ms firewall1.sapo.co.za [165.8.13.21]
12 38 ms 37 ms 39 ms 165.8.15.41
13 * * * Request timed out.
14 * * * Request timed out.
15 39 ms 38 ms 39 ms 165.8.60.15
Trace complete.
C:\Documents and Settings\Nagatoyuki>tracert sms.postoffice.co.za
Tracing route to sms.postoffice.co.za [165.8.60.15]
over a maximum of 30 hops:
1 286 ms 286 ms 286 ms 95.211.102.1
2 285 ms 285 ms 285 ms 94.75.222.190
3 286 ms 286 ms 287 ms te0-3-0-6.crs.tc2.leaseweb.net [62.212.80.97]
4 287 ms 290 ms 286 ms ams-ix.ams01.mzima.net [195.69.144.73]
5 286 ms 286 ms 286 ms 92.60.240.138
6 294 ms 294 ms 294 ms lon-ip-dir-telecity-gig-1-0-2.telkom-ipnet.co.za
[196.43.9.217]
7 294 ms 294 ms 295 ms lon-ip-dir-telecity-ge-0-3-0-100.telkom-ipnet.co
.za [196.43.9.42]
8 295 ms 295 ms 295 ms lon-ip-dir-telecity.telkom-ipnet.co.za [196.43.9
.249]
9 467 ms 467 ms 467 ms 196.43.9.137
10 485 ms 484 ms 485 ms tpr-ip-esr-3-gig-6-0-0.telkom-ipnet.co.za [196.4
3.25.54]
11 494 ms 494 ms 494 ms sapos-gw.telkom-ipnet.co.za [196.25.191.34]
12 485 ms 485 ms 486 ms 165.8.15.17
13 485 ms 486 ms 487 ms 165.8.13.3
14 * 492 ms 493 ms firewall1.sapo.co.za [165.8.13.21]
15 487 ms 486 ms 487 ms 165.8.15.45
16 * * * Request timed out.
17 * * * Request timed out.
18 492 ms 492 ms 492 ms 165.8.60.15
Trace complete.
The problem is not at my end, the problem is with MWEB's peering with TELKOM etc.
Hi PeterCH
I've just tested the site on a 384k MWEB connection and could not replicate the problem you are describing, the site is quick and all pages load fully. Looking at the traceroute that you've provided from the MWEB connection I don't see any indication there of a peering problem and traces and pings from my side are all completing successfully.
Please PM your MWEB Account details and I'll have one of our specialists contact you to troubleshoot this further.
Kind Regards
MWEB Operations
It also times out for me.