MWEB Uncapped ADSL Feedback

Status
Not open for further replies.
TmanSA said:
Thank You Mweb Guy...

Recreating the port will not help much i am afraid... there are still big problems on our line on this side towards the exchange... to be honest it is a waste of time (and Money) to phone telkom, its now been 5 Months + and still the are incapable to fix the problems... I am close to giving up with them... they are useless... and their helpdesk is worse... u can phone 3 times a day and all 3 times the will tell u a different story and all 3 times they are lying through their teeth... totally useless...
Click to expand...

Sorry that you have to endure that, wish I could fix it myself...

HOpefully when they start upgrading the exchanges they'll fix all other problems pertaining to those exchanges... (holding thumbs)..
 
Hey Mweb guy, any idea what upload speed I'm supposed to be getting on a 1meg line?? Currently syncing at 384 and pretty sure it used to be at 256. But everything working perfectly so please don't change anything, just curiosity...
 
Update, I got zdnet working it was Firefox HTTPS Everywhere extension causing issues.

Code: 
tracert to [url]www.team-xecuter.com[/url]
1	192.168.0.1		0 ms
2	41.133.244.1	41-133-244-1.dsl.mweb.co.za	8 ms
3	197.82.5.250	197-82-5-250.dbn.mweb.co.za	12 ms
4	197.82.2.3	197-82-2-3.dbn.mweb.co.za	11 ms
5	176.67.177.131		204 ms
6	149.6.98.5	te1-4.ccr01.lon09.atlas.cogentco.com	203 ms
7	154.54.36.169	te0-3-0-4.ccr22.lon01.atlas.cogentco.com	278 ms
8	130.117.0.93	te0-3-0-5.ccr22.lon13.atlas.cogentco.com	276 ms
[B]9	209.59.211.47[/B]		272 ms

hops all time out after 9....
 
mikef said:
Not available using mweb uncapped - can access via telkom
Click to expand...

gregmcc said:
Interesting - does that mean its a mweb routing problem?
Click to expand...

Evening Gents, I was able to access the site on the LAN; however unsuccessful are our test bench. Likely that it is the website itself, I have escalated this to out network team. Our abuse team will probably have to get in contact with the hosts to resolve the issue though.
 
Latency just gone to meh, international only it seems ...... been steady 273 ping for ages, about 30 mins ago it shot to 360 and holding. Other accounts are fine.



C:\Users\Andre>ping ddo.com

Pinging ddo.com [74.201.102.43] with 32 bytes of data:
Reply from 74.201.102.43: bytes=32 time=327ms TTL=233
Reply from 74.201.102.43: bytes=32 time=327ms TTL=233
Reply from 74.201.102.43: bytes=32 time=327ms TTL=233
Reply from 74.201.102.43: bytes=32 time=327ms TTL=233

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

C:\Users\Andre>ping bbc.co.uk

Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=254ms TTL=238
Reply from 212.58.241.131: bytes=32 time=253ms TTL=238
Reply from 212.58.241.131: bytes=32 time=254ms TTL=238
Reply from 212.58.241.131: bytes=32 time=254ms TTL=238

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

C:\Users\Andre>ping mybroadband.co.za

Pinging mybroadband.co.za [41.203.21.137] with 32 bytes of data:
Reply from 41.203.21.137: bytes=32 time=21ms TTL=52
Reply from 41.203.21.137: bytes=32 time=21ms TTL=52
Reply from 41.203.21.137: bytes=32 time=21ms TTL=52
Reply from 41.203.21.137: bytes=32 time=21ms TTL=52

Ping statistics for 41.203.21.137:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 21ms, Average = 21ms
Click to expand...


The international pings are always sub 300 and 200 respectively.
 
Last edited:
Hi MH,

Please could you monitor your connection from your side and let me know if it gets any worse or stabilizes.
 
It got better Mweb Guy, I'd say it was on the up for maybe 90 minutes or so.
 
Mephisto_Helix said:
It got better Mweb Guy, I'd say it was on the up for maybe 90 minutes or so.
Click to expand...

From MWEB Uncapped.

ping www.ananzi.co.za

PING www.ananzi.co.za (213.179.59.212): 56 data bytes
64 bytes from 213.179.59.212: icmp_seq=76 ttl=47 time=228.828 ms
Request timeout for icmp_seq 77
64 bytes from 213.179.59.212: icmp_seq=78 ttl=47 time=256.565 ms
64 bytes from 213.179.59.212: icmp_seq=79 ttl=47 time=235.485 ms
64 bytes from 213.179.59.212: icmp_seq=80 ttl=47 time=242.932 ms
Request timeout for icmp_seq 81
64 bytes from 213.179.59.212: icmp_seq=82 ttl=47 time=253.847 ms
64 bytes from 213.179.59.212: icmp_seq=83 ttl=47 time=236.988 ms
Request timeout for icmp_seq 84
64 bytes from 213.179.59.212: icmp_seq=85 ttl=47 time=228.525 ms
Request timeout for icmp_seq 86
64 bytes from 213.179.59.212: icmp_seq=87 ttl=47 time=237.938 ms

From Abroad

1508 bytes from 213.179.59.212: icmp_req=14 ttl=49 time=34.0 ms
1508 bytes from 213.179.59.212: icmp_req=15 ttl=49 time=34.0 ms
1508 bytes from 213.179.59.212: icmp_req=16 ttl=49 time=36.2 ms
1508 bytes from 213.179.59.212: icmp_req=17 ttl=49 time=34.0 ms
1508 bytes from 213.179.59.212: icmp_req=18 ttl=49 time=33.8 ms
1508 bytes from 213.179.59.212: icmp_req=19 ttl=49 time=33.9 ms
1508 bytes from 213.179.59.212: icmp_req=20 ttl=49 time=33.9 ms

Why is there packet loss from MWEB Uncapped ? :(

Everything very slow here.
 
Hi nutter2000

I will reply to your Pm shortly.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X