Afrihost New Network Feedback

Status
Not open for further replies.
Read it and weep...

Tracing route to google.co.za [216.58.223.3]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 1542 ms 1718 ms 1879 ms 169-0-19-1.ip.afrihost.co.za [169.0.19.1]
3 2175 ms 1214 ms 1198 ms cpt-tx2.ip.adsl.co.za [169.1.5.81]
4 1584 ms 1715 ms 1576 ms cpt-rx1.ip.adsl.co.za [169.1.5.94]
5 2118 ms 2067 ms 1976 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 2030 ms 1602 ms 1664 ms 41.164.52.40
7 1763 ms 1617 ms 1748 ms 172.18.1.162
8 1466 ms 1590 ms 1795 ms 72.14.194.206
9 1761 ms 1743 ms 2213 ms 72.14.237.239
10 1570 ms 1897 ms 1841 ms jnb01s07-in-f3.1e100.net [216.58.223.3]

Trace complete.

Yes Yes.....It my exchange, please contact Telkom, blah blah blah
Then I say no its not. I had ADSL for 5 years now and this is the first time. Then I post another trace route a few days later when the problem fixes itself and everyone is happy.
 
Bashley said:
Read it and weep...

Tracing route to google.co.za [216.58.223.3]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 1542 ms 1718 ms 1879 ms 169-0-19-1.ip.afrihost.co.za [169.0.19.1]
3 2175 ms 1214 ms 1198 ms cpt-tx2.ip.adsl.co.za [169.1.5.81]
4 1584 ms 1715 ms 1576 ms cpt-rx1.ip.adsl.co.za [169.1.5.94]
5 2118 ms 2067 ms 1976 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 2030 ms 1602 ms 1664 ms 41.164.52.40
7 1763 ms 1617 ms 1748 ms 172.18.1.162
8 1466 ms 1590 ms 1795 ms 72.14.194.206
9 1761 ms 1743 ms 2213 ms 72.14.237.239
10 1570 ms 1897 ms 1841 ms jnb01s07-in-f3.1e100.net [216.58.223.3]

Trace complete.

Yes Yes.....It my exchange, please contact Telkom, blah blah blah
Then I say no its not. I had ADSL for 5 years now and this is the first time. Then I post another trace route a few days later when the problem fixes itself and everyone is happy.
Click to expand...

0_0

That's pretty horrific. How long as it been like that?!?
 
YouTube still going strong. :)

Capture_1080.JPG


Trace route to google.co.za:
Code: 
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\Lara>tracert google.co.za

Tracing route to google.co.za [216.58.223.35]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    17 ms    16 ms    17 ms  cpt-tx2.ip.adsl.co.za [169.1.5.81]
  4    17 ms    16 ms    17 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82]
  5    19 ms    16 ms    17 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6    16 ms    17 ms    17 ms  41.164.52.40
  7    37 ms    37 ms    39 ms  172.18.1.162
  8    43 ms    48 ms    51 ms  72.14.194.206
  9    39 ms    38 ms    38 ms  72.14.239.129
 10    38 ms    38 ms    39 ms  jnb01s08-in-f35.1e100.net [216.58.223.35]

Trace complete.
 
Are some of you guys still having issues with torrents in the evening? It seems to be effecting me now as well.
 
Icemanbrfc said:
so you read 661 pages, and seen what issues some people are having, and you just assume that its the same issue for you, without giving the Afri Guys any further info.

Most of the guys who are having issues, are at least giving them info they require, as difficult a time as they are having, and as gatvol as they are getting they are giving what is being asked of them.

Most of the other ISP's will ask for at least some info or testing to ascertain where the problem might lie.
Click to expand...

Before assuming I haven't given any info, maybe you should pose that into a question. I have contacted the support desk a couple of times, given what they have asked for, made changes on my router as requested and still nothing. So kindly keep those assumptions to yourself. Unless of course you think you know everything, but MY assumption is you know diddly..

Keep cool though
 
Tracing route to afrihost.co.za [41.86.112.68]
over a maximum of 30 hops:

1 1 ms 1 ms 2 ms 192.168.1.1
2 1025 ms 1137 ms 1165 ms 169-0-19-1.ip.afrihost.co.za [169.0.19.1]
3 2954 ms * 2259 ms cpt-tx2.ip.adsl.co.za [169.1.5.81]
4 1726 ms 1542 ms 1294 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
5 1339 ms 1416 ms 1322 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 1766 ms 1688 ms 3165 ms optinet.ct1.napafrica.net [196.10.140.15]
7 1887 ms 1846 ms 2039 ms te0-0-0-1.cpt-p-2.optinet.net [197.84.7.34]
8 1770 ms 1498 ms 1788 ms tengig-0-7-0-1-vic-p-1.mweb.co.za [197.84.4.47]

9 1949 ms 1459 ms 1585 ms 101.te0-0-2-0.vic-tr-1.optinet.net [197.80.7.4]

10 1249 ms 1273 ms 1421 ms 197-81-226-77.jhb.mweb.co.za [197.81.226.77]
11 1597 ms 1481 ms 1420 ms 197-81-226-53.jhb.mweb.co.za [197.81.226.53]
12 1470 ms 1610 ms 1432 ms 197-81-229-2.jhb.mweb.co.za [197.81.229.2]
13 1407 ms 1519 ms 1609 ms 197-81-229-9.jhb.mweb.co.za [197.81.229.9]
14 1679 ms 1779 ms 2029 ms afrihost.co.za [41.86.112.68]

Trace complete.
 
Unhappy438 said:
Are some of you guys still having issues with torrents in the evening? It seems to be effecting me now as well.
Click to expand...

What sort of Afrihost account are you on at the moment? How is your line looking at the moment?
 
NewBiks said:
I always seem to have issues with Twitch.

I've also just got out of a game of CS where I was getting 5-10% packet loss
Click to expand...

Is Twitch.tv generally bad or is there a particular stream that is worse than the others?
 
Evening folks - Been getting terrible latency with online gaming and web pages taking ages to load.. I have seen people posting on here now so thought I would give it a bash to see if anyone can help.

Not sure if this helps at all below. My concern is all the time outs?

Thanks all

15 194 ms 195 ms 194 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
16 199 ms 199 ms 199 ms 195.219.83.186
17 194 ms 215 ms 231 ms ae-4.r22.londen03.uk.bb.gin.ntt.net [129.250.5.24]
18 266 ms 266 ms 266 ms ae-5.r24.nycmny01.us.bb.gin.ntt.net [129.250.2.18]
19 263 ms 263 ms 262 ms ae-1.r07.nycmny01.us.bb.gin.ntt.net [129.250.3.181]
20 266 ms 266 ms 265 ms ae-8.amazon.nycmny01.us.bb.gin.ntt.net [129.250.201.126]
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 282 ms 291 ms 356 ms 54.239.110.167
27 272 ms 271 ms 271 ms 54.239.111.39
28 270 ms 273 ms 288 ms 205.251.244.205
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
 
OMGWTFLMAO said:
Evening folks - Been getting terrible latency with online gaming and web pages taking ages to load.. I have seen people posting on here now so thought I would give it a bash to see if anyone can help.

Not sure if this helps at all below. My concern is all the time outs?

Thanks all

15 194 ms 195 ms 194 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
16 199 ms 199 ms 199 ms 195.219.83.186
17 194 ms 215 ms 231 ms ae-4.r22.londen03.uk.bb.gin.ntt.net [129.250.5.24]
18 266 ms 266 ms 266 ms ae-5.r24.nycmny01.us.bb.gin.ntt.net [129.250.2.18]
19 263 ms 263 ms 262 ms ae-1.r07.nycmny01.us.bb.gin.ntt.net [129.250.3.181]
20 266 ms 266 ms 265 ms ae-8.amazon.nycmny01.us.bb.gin.ntt.net [129.250.201.126]
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 282 ms 291 ms 356 ms 54.239.110.167
27 272 ms 271 ms 271 ms 54.239.111.39
28 270 ms 273 ms 288 ms 205.251.244.205
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
Click to expand...

That's past London. Could you post the address you are running a tracert to, the full test and a sustained ping test (use the ping address -t). Please also try pinging bras.afrihost.com

(you can use the
Code: 
 tag to put your tracert in, it will put it in a nice scroll-box an it won't lose form)
 
OMGWTFLMAO said:
Evening folks - Been getting terrible latency with online gaming and web pages taking ages to load.. I have seen people posting on here now so thought I would give it a bash to see if anyone can help.

Not sure if this helps at all below. My concern is all the time outs?

Thanks all

15 194 ms 195 ms 194 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
16 199 ms 199 ms 199 ms 195.219.83.186
17 194 ms 215 ms 231 ms ae-4.r22.londen03.uk.bb.gin.ntt.net [129.250.5.24]
18 266 ms 266 ms 266 ms ae-5.r24.nycmny01.us.bb.gin.ntt.net [129.250.2.18]
19 263 ms 263 ms 262 ms ae-1.r07.nycmny01.us.bb.gin.ntt.net [129.250.3.181]
20 266 ms 266 ms 265 ms ae-8.amazon.nycmny01.us.bb.gin.ntt.net [129.250.201.126]
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 282 ms 291 ms 356 ms 54.239.110.167
27 272 ms 271 ms 271 ms 54.239.111.39
28 270 ms 273 ms 288 ms 205.251.244.205
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
Click to expand...

The timeouts aren't always a good thing or a bad thing. At some points network devices don't respond to ICMP traffic, so they will return timed out requests like that.

Would you mind posting the entire traceroute?
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X