Beri
Expert Member
- Joined
- Sep 26, 2006
- Messages
- 4,347
- Reaction score
- 68
No. Ah reset my port and it worked great for 1 day. Now it is slow again
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: Do you think you could pass a driver's licence test without any preparation?
Afrihost CAPPED ADSL Feedback (MTN)
- Thread starter eddief1
- Start date
- Status
No. Ah reset my port and it worked great for 1 day. Now it is slow again
DrJohnZoidberg
Honorary Master
Well at least we improved your latency :/
Beri
Expert Member
- Joined
- Sep 26, 2006
- Messages
- 4,347
- Reaction score
- 68
Thanks for that...".
roadcat
Expert Member
Well that's nice 
My upload is more than my download...
My upload is more than my download...
This isn't pure internet joy
4 meg line
Looks like a line fault to me
That ping is a bit high :/Please would you run my second tool in my sig - and post the results here
Z
P.S: I'm in CPT, and mine's flying tonight
Looks like a line fault to me
Please would you run my second tool in my sig - and post the results here
Z
Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 488ms
Your maximum ping was 571ms
Looking at your average ping, there is definitely something wrong with your line-( Please post the results (at the end of the program) into the forum for advice
Detailed Report
Code:
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)
Pinging 105.236.5.193 with 32 bytes of data:
Reply from 105.236.5.193: bytes=32 time=492ms TTL=254
Reply from 105.236.5.193: bytes=32 time=569ms TTL=254
Reply from 105.236.5.193: bytes=32 time=478ms TTL=254
Reply from 105.236.5.193: bytes=32 time=408ms TTL=254
Reply from 105.236.5.193: bytes=32 time=483ms TTL=254
Reply from 105.236.5.193: bytes=32 time=567ms TTL=254
Reply from 105.236.5.193: bytes=32 time=491ms TTL=254
Reply from 105.236.5.193: bytes=32 time=370ms TTL=254
Reply from 105.236.5.193: bytes=32 time=484ms TTL=254
Reply from 105.236.5.193: bytes=32 time=532ms TTL=254
Reply from 105.236.5.193: bytes=32 time=571ms TTL=254
Reply from 105.236.5.193: bytes=32 time=457ms TTL=254
Reply from 105.236.5.193: bytes=32 time=349ms TTL=254
Reply from 105.236.5.193: bytes=32 time=483ms TTL=254
Reply from 105.236.5.193: bytes=32 time=447ms TTL=254
Reply from 105.236.5.193: bytes=32 time=481ms TTL=254
Reply from 105.236.5.193: bytes=32 time=518ms TTL=254
Reply from 105.236.5.193: bytes=32 time=571ms TTL=254
Reply from 105.236.5.193: bytes=32 time=445ms TTL=254
Reply from 105.236.5.193: bytes=32 time=352ms TTL=254
Reply from 105.236.5.193: bytes=32 time=440ms TTL=254
Reply from 105.236.5.193: bytes=32 time=518ms TTL=254
Request timed out.
Reply from 105.236.5.193: bytes=32 time=564ms TTL=254
Reply from 105.236.5.193: bytes=32 time=505ms TTL=254
Reply from 105.236.5.193: bytes=32 time=475ms TTL=254
Reply from 105.236.5.193: bytes=32 time=547ms TTL=254
Reply from 105.236.5.193: bytes=32 time=565ms TTL=254
Reply from 105.236.5.193: bytes=32 time=522ms TTL=254
Reply from 105.236.5.193: bytes=32 time=496ms TTL=254
Ping statistics for 105.236.5.193:
Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 349ms, Maximum = 571ms, Average = 488ms
2014/06/16 23:41:22.92
Hey Everyone
Saw a few posts about throughput being poor and latency. I think it seems to be the same few people having this routing issue. I can't see from the posts whether they are still getting the same results. Timeout on second hop suggests it might be. Please drop me a PM so I can continue trying to get this figured out.
Otherwise we haven't been seeing much different on the network in general. Changes were made in the North over the last day or so, so I am hoping the packet loss being reported should now have disappeared. If not, please let me know ASAP.
Saw a few posts about throughput being poor and latency. I think it seems to be the same few people having this routing issue. I can't see from the posts whether they are still getting the same results. Timeout on second hop suggests it might be. Please drop me a PM so I can continue trying to get this figured out.
Otherwise we haven't been seeing much different on the network in general. Changes were made in the North over the last day or so, so I am hoping the packet loss being reported should now have disappeared. If not, please let me know ASAP.
The pro-rata billing looks correct, not too sure about the allocation though as it's an Uncapped account.
Could you drop me a PM with your DSL username that you're looking to upgrade so I can have our team check this out?
OMB
Mountain Man
6.93TB for R52.93 sounds like a bargain to me, what are you complaining about?
You can actually have the internet if you use that much data
Just don't wanna get charged more if it's a mistake.
Also would like to let them know if it's a potential issue on the website.
R52 just seems very low.
Also would like to let them know if it's a potential issue on the website.
R52 just seems very low.
6.93TB for R52.93 sounds like a bargain to me, what are you complaining about?
DrJohnZoidberg
Honorary Master
You can actually have the internet if you use that much data
Hehe, I'm almost there... after a year!
Hehe, I'm almost there... after a year!
That's impressive dude! Many high fives
Beri
Expert Member
- Joined
- Sep 26, 2006
- Messages
- 4,347
- Reaction score
- 68
this morning I still had the time out.
Seems like roadcat is still having the same routing issue, with the timeout on the second hop, so we'll have to keep looking into this until we can figure out why this is happening
I'm hoping it will be delivered ASAP, but I don't have a confirmed date that I can commit to just yet. Hoping it won't be longer than a week or so, but nothing concrete to share right now
- Status