Just to add to this, when doing Speedtests it normally picks me up in Durban. However the last few days it shows Cape Town as my closest server, and then the Speedtest doesn't complete. Nothing changed on my side, using the Afrihost issued DNS and everything.
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: Will you be watching the FIFA World Cup Final?
Afrihost Business Uncapped Feedback
- Thread starter Lino
- Start date
- Status
F
Fudzy
Guest
Sheesh! Is it bundled?
Yup, bundled. It used to be rock solid, but getting worse week by week unfortunately. Just wish there was an alternative.
Hey Man, that was just for him to ping his exchange
It seems like you have very bad ping - which could be related to intermittent exchange congestion. If it doesnt clear up - contact Live Chat, theyll help you out.Unfortunately you have bad exchange congestion there :/ Try contacting Afrihost and Telkom to report a line fault. Also try connecting over ethernet instead of wifi, and make sure your router is not getting too hot
Bursty-dude
Expert Member
If it was the routher, the connection would suck permanently, right?
And I am not going to buy a router just to check, and I do not know anyone with the same model router which I could borrow to test.
Firstly, Could you please type this into cmd.
ping 105.236.11.193 -t
Let it run for +-5 minutes and post a summary here.
Secondly - could you post a screenshot of your routers status page please
Thirdly - regarding the line speeds. Telkom dont offer 6MB sync's so you have to pay for a 10meg line. This means that you have more line capacity than your account speed - which is a good thing
1:
Pinging 105.236.11.193 with 32 bytes of data:
Reply from 105.236.11.193: bytes=32 time=15ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=14ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=18ms TTL=254
Reply from 105.236.11.193: bytes=32 time=14ms TTL=254
Reply from 105.236.11.193: bytes=32 time=16ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=15ms TTL=254
Reply from 105.236.11.193: bytes=32 time=23ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=21ms TTL=254
Reply from 105.236.11.193: bytes=32 time=18ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=16ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=14ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=17ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=16ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=16ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=14ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=18ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=21ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=16ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=21ms TTL=254
Reply from 105.236.11.193: bytes=32 time=15ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=14ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=20ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=17ms TTL=254
Reply from 105.236.11.193: bytes=32 time=15ms TTL=254
Reply from 105.236.11.193: bytes=32 time=14ms TTL=254
Reply from 105.236.11.193: bytes=32 time=15ms TTL=254
Reply from 105.236.11.193: bytes=32 time=20ms TTL=254
Reply from 105.236.11.193: bytes=32 time=15ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=22ms TTL=254
Reply from 105.236.11.193: bytes=32 time=15ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=14ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=29ms TTL=254
Reply from 105.236.11.193: bytes=32 time=14ms TTL=254
Reply from 105.236.11.193: bytes=32 time=20ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=14ms TTL=254
Reply from 105.236.11.193: bytes=32 time=30ms TTL=254
Reply from 105.236.11.193: bytes=32 time=17ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=23ms TTL=254
Reply from 105.236.11.193: bytes=32 time=14ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Request timed out.
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Request timed out.
Reply from 105.236.11.193: bytes=32 time=16ms TTL=254
Request timed out.
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Request timed out.
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=19ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=26ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=23ms TTL=254
Reply from 105.236.11.193: bytes=32 time=14ms TTL=254
Reply from 105.236.11.193: bytes=32 time=25ms TTL=254
Reply from 105.236.11.193: bytes=32 time=14ms TTL=254
Reply from 105.236.11.193: bytes=32 time=26ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=26ms TTL=254
Reply from 105.236.11.193: bytes=32 time=14ms TTL=254
Reply from 105.236.11.193: bytes=32 time=20ms TTL=254
Reply from 105.236.11.193: bytes=32 time=19ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=25ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=16ms TTL=254
Reply from 105.236.11.193: bytes=32 time=17ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Reply from 105.236.11.193: bytes=32 time=11ms TTL=254
Ping statistics for 105.236.11.193:
Packets: Sent = 149, Received = 139, Lost = 10 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 30ms, Average = 14ms
Control-C
2:
3:
Like I have told Afrihost many times before, when we first got ADSL a year ago, we had a perfectly stable 10Mb line and never had issues with anything like Youtube buffering, dropping connections, intermittent service, etc. Since March 2013, it has slowly degraded into the crap we sit with today. In short, it used to be a stable 10Mb line, now it is all over the place.
Bursty-dude
Expert Member
Exactly. But trying to get Hellscum to fix a single line problem in this area will test the patience of every single Saint in history.
None of our neighbors I speak to regularly have ADSL. They all use various cell networks.
Business next door closed down about 3 months ago and house is standing empty, but they did have ADSL.
Line went belly up for about 20 minutes just now, now it's back again, but slower than it was earlier today.
If I was Gian, I will walk into Telkom and go bitchslap whoever is in charge of the Techs. I honestly would.
None of our neighbors I speak to regularly have ADSL. They all use various cell networks.
Business next door closed down about 3 months ago and house is standing empty, but they did have ADSL.
Line went belly up for about 20 minutes just now, now it's back again, but slower than it was earlier today.
If I was Gian, I will walk into Telkom and go bitchslap whoever is in charge of the Techs. I honestly would.
Haha. Okay - so, the reason I say it could be a router issue is that there is a high latency for the first hop, which indicated the router is having issues.
Try swopping out the Ethernet cable. Also - would you please run a speedtest over wifi from one of your cell phones, and post the results here. Do you have a laptop to run a tracert over wifi with?
Z
GarethY
Well-Known Member
Unfortunately you have bad exchange congestion there :/ Try contacting Afrihost and Telkom to report a line fault. Also try connecting over ethernet instead of wifi, and make sure your router is not getting too hot
It's not the exchange congestion I'm looking at - I know about that. Check out hop 8 and onward, it just keeps going back and forth between two IP addresses and never gets to the destination...
EDIT: I can access that website on my Openweb accounts, but not on my Afrihost accounts
Check post 3111
1 2 ms 4 ms 1 ms 192.168.0.1
That's not too bad, there could be a QoS or or silly things running at the time since ping/tracert don't get priority.
Good point.
Bursty-dude
Expert Member
This is an email I sent at 2:51AM this morning after trying to do some work on my website, but the connection kept giving me the finger, and after checking on Telkom's fault tracking (which showed the fault was closed
):
"To: [email protected], [email protected]
I have just checked on Telkom's fault tracking and the fault has been closed.
No, the problem still remains with a very badly erratic connection at times.
10 months later and Telkom STILL has not done anything about the problem.
I have not heard from a single person at Telkom, nor has any Telkom tech set foot in our property to check the line and connections since I first opened a support ticket way back in March 2013.
10 months have passed, and the problem remains. This is not what "pure internet joy" should be like. I was very very impressed with Afrihost back in January 2013, when we had a stable 10Mb connection and no connection problems. But now....
6BTK221213 fault must be reopened and fixed.
I work from home and am almost always here, so Telkom cannot lie and say they have been here or tried to contact me.
Please get them to come to our house and physically check what the problem is.
Regards."
I now do not care anymore, if this issue is not resolved by the end of January 2014, I will cancel my AH ADSL, the Mifi, and my web hosting, and go elsewhere.
I am now officially done complaining, doing traceroutes, doing speed tests, etc. It is now in Afrihost's hands. Either they get Hellscum to fix the line, or they lose 1600 bucks per month from a customer.
):"To: [email protected], [email protected]
I have just checked on Telkom's fault tracking and the fault has been closed.
No, the problem still remains with a very badly erratic connection at times.
10 months later and Telkom STILL has not done anything about the problem.
I have not heard from a single person at Telkom, nor has any Telkom tech set foot in our property to check the line and connections since I first opened a support ticket way back in March 2013.
10 months have passed, and the problem remains. This is not what "pure internet joy" should be like. I was very very impressed with Afrihost back in January 2013, when we had a stable 10Mb connection and no connection problems. But now....
6BTK221213 fault must be reopened and fixed.
I work from home and am almost always here, so Telkom cannot lie and say they have been here or tried to contact me.
Please get them to come to our house and physically check what the problem is.
Regards."
I now do not care anymore, if this issue is not resolved by the end of January 2014, I will cancel my AH ADSL, the Mifi, and my web hosting, and go elsewhere.
I am now officially done complaining, doing traceroutes, doing speed tests, etc. It is now in Afrihost's hands. Either they get Hellscum to fix the line, or they lose 1600 bucks per month from a customer.
GarethY
Well-Known Member
Oh whoops
Google DNS on Afrihost line:
Code:
C:\Windows\system32>ping themorningpint.com
Pinging themorningpint.com [66.147.244.155] with 32 bytes of data:
Reply from 196.44.18.89: TTL expired in transit.
Reply from 196.44.18.89: TTL expired in transit.
Reply from 196.44.18.89: TTL expired in transit.
Reply from 196.44.18.89: TTL expired in transit.
Ping statistics for 66.147.244.155:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
C:\Windows\system32>tracert themorningpint.com
Tracing route to themorningpint.com [66.147.244.155]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 10.1.1.10
2 23 ms 35 ms 22 ms 105-236-7-65-esr-lo.mtnbusiness.co.za [105.236.7.65]
3 81 ms 39 ms 39 ms 41.181.51.182
4 38 ms 35 ms 35 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 42 ms 51 ms 39 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 42 ms 45 ms 45 ms 196.44.31.106
7 37 ms 41 ms 37 ms ct-nas-1--ct-ad-1-a.mtnns.net [196.44.18.86]
8 * 35 ms 50 ms 196.44.18.89
9 219 ms 42 ms 251 ms 196.44.18.90
10 * 38 ms 36 ms 196.44.18.89
11 71 ms 43 ms 38 ms 196.44.18.90
12 42 ms 37 ms 40 ms 196.44.18.89
13 42 ms 40 ms 36 ms 196.44.18.90
14 36 ms * * 196.44.18.89
15 41 ms 55 ms 39 ms 196.44.18.90
16 * * * Request timed out.
17 157 ms 60 ms 42 ms 196.44.18.90
18 * 37 ms * 196.44.18.89
19 39 ms 36 ms 41 ms 196.44.18.90
20 * 37 ms 240 ms 196.44.18.89
21 60 ms 56 ms 42 ms 196.44.18.90
22 * 51 ms 60 ms 196.44.18.89
23 41 ms 59 ms * 196.44.18.90
24 46 ms 46 ms 52 ms 196.44.18.89
25 48 ms 43 ms 51 ms 196.44.18.90
26 54 ms 38 ms 37 ms 196.44.18.89
27 41 ms 41 ms 37 ms 196.44.18.90
28 * * * Request timed out.
29 45 ms 39 ms 41 ms 196.44.18.90
30 * * ms 220 ms 196.44.18.89
Trace complete.Afrihost DNS on Afrihost line:
Code:
C:\Windows\system32>ping themorningpint.com
Pinging themorningpint.com [66.147.244.155] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 66.147.244.155:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Windows\system32>tracert themorningpint.com
Tracing route to themorningpint.com [66.147.244.155]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.1.1.10
2 23 ms 21 ms 21 ms 105-236-7-65-esr-lo.mtnbusiness.co.za [105.236.7.65]
3 41 ms 36 ms 38 ms 41.181.51.182
4 81 ms 34 ms 53 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 51 ms 42 ms 40 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 38 ms * 42 ms 196.44.31.106
7 83 ms 40 ms 38 ms ct-nas-1--ct-ad-1-a.mtnns.net [196.44.18.86]
8 * * * Request timed out.
9 39 ms 38 ms 49 ms 196.44.18.90
10 * * * Request timed out.
11 48 ms 41 ms 51 ms 196.44.18.90
12 46 ms 68 ms * 196.44.18.89
13 41 ms 36 ms 40 ms 196.44.18.90
14 44 ms * 37 ms 196.44.18.89
15 41 ms 43 ms 41 ms 196.44.18.90
16 39 ms 40 ms 37 ms 196.44.18.89
17 51 ms 40 ms 36 ms 196.44.18.90
18 53 ms * * 196.44.18.89
19 45 ms 45 ms 54 ms 196.44.18.90
20 43 ms 49 ms 49 ms 196.44.18.89
21 41 ms 36 ms 39 ms 196.44.18.90
22 36 ms 45 ms 58 ms 196.44.18.89
23 38 ms * 36 ms 196.44.18.90
24 * * * Request timed out.
25 40 ms 39 ms 37 ms 196.44.18.90
26 * 42 ms 39 ms 196.44.18.89
27 37 ms 47 ms 40 ms 196.44.18.90
28 * 39 ms 36 ms 196.44.18.89
29 42 ms 46 ms 41 ms 196.44.18.90
30 37 ms 40 ms 36 ms 196.44.18.89
Trace complete.Openweb DNS on Openweb line:
Code:
C:\Windows\system32>ping themorningpint.com
Pinging themorningpint.com [66.147.244.155] with 32 bytes of data:
Reply from 66.147.244.155: bytes=32 time=316ms TTL=43
Reply from 66.147.244.155: bytes=32 time=315ms TTL=44
Reply from 66.147.244.155: bytes=32 time=311ms TTL=44
Reply from 66.147.244.155: bytes=32 time=313ms TTL=44
Ping statistics for 66.147.244.155:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 311ms, Maximum = 316ms, Average = 313ms
C:\Windows\system32>tracert themorningpint.com
Tracing route to themorningpint.com [66.147.244.155]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.1.1.10
2 20 ms 19 ms 19 ms 196-210-155-129.dynamic.isadsl.co.za [196.210.155.129]
3 39 ms 35 ms 37 ms vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
4 38 ms 38 ms 35 ms 196.35.115.136
5 49 ms 37 ms 59 ms 168.209.2.12
6 36 ms 45 ms 38 ms core1b-ctn-gi0-2.ip.isnet.net [168.209.6.4]
7 188 ms 187 ms 187 ms core1b-dock-ten-0-4-0-0-119.ip.isnet.net [168.209.0.10]
8 185 ms 186 ms 186 ms 40gigabitethernet1-1.core1.lon1.he.net [195.66.224.21]
9 * 257 ms 273 ms 10ge10-4.core1.nyc4.he.net [72.52.92.241]
10 277 ms 271 ms * 100ge7-2.core1.chi1.he.net [184.105.223.161]
11 295 ms 294 ms 299 ms 10ge3-2.core1.den1.he.net [184.105.213.86]
12 305 ms 305 ms 320 ms 10ge4-2.core1.slc1.he.net [184.105.222.154]
13 315 ms 321 ms 325 ms ace-data-centers-inc.10gigabitethernet1-4.core1.slc1.he.net [66.160.133.118]
14 314 ms 317 ms 314 ms rtr-b.unifiedlayer.com [199.58.199.118]
15 315 ms 313 ms 323 ms box655.bluehost.com [66.147.244.155]
Trace complete.
C:\Windows\system32>Okay - something VERY weird is going on here!
Okay, I've just done a tracert - and it does the same thing. This means that there might be a server error? Please would you try a tracert to google.co.za and bbc.co.uk.
1 <1 ms <1 ms <1 ms 10.0.0.1
2 8 ms 7 ms 7 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 9 ms 9 ms 10 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
4 10 ms 9 ms 10 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 10 ms 10 ms 10 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 9 ms 10 ms 10 ms 196.44.31.106
7 9 ms 9 ms 9 ms ct-nas-1--ct-ad-1-a.mtnns.net [196.44.18.86]
8 * 10 ms 10 ms 196.44.18.89
9 9 ms 9 ms 10 ms 196.44.18.90
10 10 ms 10 ms 10 ms 196.44.18.89
11 10 ms 18 ms 9 ms 196.44.18.90
12 9 ms 9 ms 9 ms 196.44.18.89
13 9 ms 9 ms 10 ms 196.44.18.90
14 9 ms 10 ms 11 ms 196.44.18.89
15 10 ms 9 ms 9 ms 196.44.18.90
16 10 ms 10 ms * 196.44.18.89
17 10 ms 10 ms 10 ms 196.44.18.90
18 * * * Request timed out.
19 10 ms 10 ms 10 ms 196.44.18.90
20 * * * Request timed out.
21 10 ms 10 ms 10 ms 196.44.18.90
22 * * * Request timed out.
23 10 ms 10 ms 10 ms 196.44.18.90
24 10 ms * 9 ms 196.44.18.89
25 10 ms 10 ms 10 ms 196.44.18.90
26 10 ms 9 ms 10 ms ^C
If this is you - ill remove the images ASAP. I thought it would just be helpful
GarethY
Well-Known Member
Code:
C:\Windows\system32>tracert www.google.co.za
Tracing route to www.google.co.za [173.194.34.151]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.1.1.10
2 52 ms 20 ms 19 ms 105-236-7-65-esr-lo.mtnbusiness.co.za [105.236.7.65]
3 62 ms 36 ms 50 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
4 58 ms 55 ms 39 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 40 ms 51 ms 47 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 187 ms 187 ms 231 ms ls-cr-2.uk--tb-cr-1.za.mtnns.net [196.44.31.113]
7 258 ms 214 ms 204 ms am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.183]
8 286 ms 195 ms 272 ms am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.141]
9 234 ms 235 ms 351 ms core2.ams.net.google.com [195.69.145.100]
10 483 ms 491 ms 565 ms 209.85.254.90
11 253 ms * 231 ms 72.14.238.153
12 197 ms 204 ms 203 ms 209.85.243.32
13 205 ms 196 ms 196 ms 209.85.253.197
14 194 ms 199 ms 199 ms 209.85.253.115
15 * 196 ms 189 ms lhr14s21-in-f23.1e100.net [173.194.34.151]
Trace complete.
C:\Windows\system32>tracert www.bbc.co.uk
Tracing route to www.bbc.net.uk [212.58.246.94]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.1.1.10
2 24 ms 34 ms 28 ms 105-236-7-65-esr-lo.mtnbusiness.co.za [105.236.7.65]
3 48 ms 37 ms 49 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
4 57 ms 40 ms 61 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 48 ms 50 ms 40 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 41 ms 82 ms 48 ms 196.44.31.106
7 216 ms 222 ms 218 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.221]
8 204 ms 190 ms 239 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
9 199 ms 180 ms 200 ms bbc-linx.pr01.thdow.bbc.co.uk [195.66.224.103]
10 * * * Request timed out.
11 204 ms 189 ms 193 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
12 231 ms 189 ms 194 ms 132.185.255.165
13 188 ms 190 ms 188 ms bbc-vip015.cwwtf.bbc.co.uk [212.58.246.94]
Trace complete.
C:\Windows\system32>Okay, so its only that site which is not resolving?
- Status