Icemanbrfc
Honorary Master
Good Morning peeps... Just want to let the JHB guys know, i am off to the beach 
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: What is your non-negotiable item, device, or app for international travel?
- Status
Good Morning peeps... Just want to let the JHB guys know, i am off to the beach
Why you no work?
Icemanbrfc
Honorary Master
I am, but im close to Sea point, so can shoot off lunch time for a quick stroll, then head back
Here we go Rickster
Attachments
- Joined
- Jun 2, 2015
- Messages
- 2,830
- Reaction score
- 82
Good Morning peeps... Just want to let the JHB guys know, i am off to the beach
Watch out for sharks.
- Joined
- Jun 2, 2015
- Messages
- 2,830
- Reaction score
- 82
I am, but im close to Sea point, so can shoot off lunch time for a quick stroll, then head back
Here we go Rickster
That looks terrible.
- Joined
- Jun 2, 2015
- Messages
- 2,830
- Reaction score
- 82
That's odd. We definitely didn't see any general issues in that regard... Are you able to test this morning?
Icemanbrfc
Honorary Master
Internet's really slow this morning :/
Even 360p YouTube videos are buffering on my 8MB line in CT.
I have reset my modem this morning already.
Afripeople, is there anything I can send you or do to have this checked out?
Even 360p YouTube videos are buffering on my 8MB line in CT.
I have reset my modem this morning already.
Afripeople, is there anything I can send you or do to have this checked out?
We can definitely check this out. Can you post a traceroute quickly?
Results from Afrihost network testing tool:
Ping Test:
ping 197.242.144.102
64 bytes from 197.242.144.102: icmp_req=1 ttl=48 time=153 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=48 time=149 ms
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
ping 8.8.8.8
64 bytes from 8.8.8.8: icmp_req=1 ttl=51 time=150 ms
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Trace Test:
traceroute -n 197.242.144.102
1 192.168.0.1 1 ms 1 ms
2 Request timed out * *
3 169.1.5.8 126 ms 125 ms
4 172.18.1.1 141 ms
169.1.5.9 114 ms
5 169.1.5.7 149 ms
41.164.52.4 123 ms
6 169.1.21.5 144 ms
41.169.57.2 142 ms
7 169.1.21.5 145 ms
traceroute -n 8.8.8.8
1 192.168.0.1 1 ms 1 ms
2 Request timed out * *
3 169.1.5.8 125 ms 126 ms
4 169.1.5.1 124 ms 124 ms
5 172.18.1.1 150 ms 145 ms
6 72.14.194.2 145 ms
8.8.8.8 149 ms
7 72.14.239.5 145 ms
8 8.8.8.8 145 ms
DNS Test:
nslookup www.afrihost.com
Name: www.afrihost.com
Address: 104.20.30.244
nslookup www.google.com
Name: www.google.com
Address: 169.1.2.81
nslookup thishouldfail.afrihost.com
** server can't find thisshouldfail.com: NXDOMAIN
HermanTheGerman
Senior Member
Same probs as Bl1zz4rd reports.
[URL=http://www.speedtest.net/my-result/5746371167]
[/URL]
126 ms ping to a local server, and 1.99 mb download on a 10 MB connection? I mean WTF???
Afriguys, this is a huge nono! Some of us depend on flawless connectivity. Not even giving your internet away for free 16 hours/day is enough to make amends for this latest fukup!!! But thx for trying anyway.
[URL=http://www.speedtest.net/my-result/5746371167]
[/URL]
126 ms ping to a local server, and 1.99 mb download on a 10 MB connection? I mean WTF???
Afriguys, this is a huge nono! Some of us depend on flawless connectivity. Not even giving your internet away for free 16 hours/day is enough to make amends for this latest fukup!!! But thx for trying anyway.
Attachments
Yes, I use OpenDNS. But DNS should not be a factor, because it is only needed before setting up the connection, not to maintain throughput on it once established
We did just report a network issue resulting slow speeds and high latency. It should be resolved now and we should see performance normalising. Can you monitor over the next 15-20 minutes?
Yes, I use OpenDNS. But DNS should not be a factor, because it is only needed before setting up the connection, not to maintain throughput on it once established
DNS still plays a role as every lookup or request is routed via DNS. If you are using external DNS, those servers could be performing poorly and this will affect the overall experience. We definitely recommend using our automatically assigned DNS (which are optimised by region) for the best experience.
Sure thing! It seems to be back to normal now. I'll post again if it slows again. Thanks
Sorry, but I dont agree. DNS lookups are cached as well, so that will negate what you said. Also, once a TCP connection has been established DNS is no longer a factor.
DNS being a problem would also show up in the general browsing experience, which it is not.
EDIT: To clarify: I don't agree that DNS is a problem in my instance. DNS however could be a problem if the general browsing experience (not throughput) is bad. This is a throughput problem on youtube, not a general browsing issue.
Last edited:
Sure thing! It seems to be back to normal now. I'll post again if it slows again. Thanks
Awesome
Understand your view here, it should be a quick enough test to change DNS and see if the experience is still problematic.
I see you are also in Cape Town, could these results also be affected by the brief issue we had earlier this morning?
Very possible, I was not made aware of any issue, the listing on the network status page does not list a start time. My bad experience was around 7am I think?
Hmmm, don't think there was an issue at that time, but perhaps it was starting to manifest or less noticeable due to the low volume of traffic on the network.
- Status