Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
Gonzo.B said:
Tested a different modem and phoned telkom twice for a port reset and to check if the dslam is congested,they say everything is fine their side.

Don't have a spare account to test,eish!


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

1 <1 ms <1 ms <1 ms login.router [10.0.0.2]
2 * * * Request timed out.
3 584 ms 531 ms 425 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 456 ms 441 ms 482 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 526 ms 489 ms 423 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 431 ms 694 ms 470 ms optinet.ixp.capetown [196.10.140.15]
7 493 ms 503 ms 477 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]
8 325 ms 402 ms 422 ms te0-7-0-0.cpt-p-1.optinet.net [197.84.4.33]
9 529 ms 570 ms 559 ms te0-0-0-0.vic-p-2.optinet.net [197.84.4.35]
10 450 ms 454 ms 436 ms 197-84-4-100.cpt.mweb.co.za [197.84.4.100]
11 342 ms 348 ms 356 ms 197-80-7-15.jhb.mweb.co.za [197.80.7.15]
12 379 ms 364 ms 345 ms 197-81-226-81.jhb.mweb.co.za [197.81.226.81]
13 587 ms 468 ms 421 ms 197-81-226-61.jhb.mweb.co.za [197.81.226.61]
14 278 ms 270 ms 316 ms 197-81-229-4.jhb.mweb.co.za [197.81.229.4]
15 470 ms 432 ms 404 ms 197-81-229-11.jhb.mweb.co.za [197.81.229.11]
16 490 ms 468 ms 500 ms www.afrihost.co.za [41.86.112.68]
Click to expand...

I've just PM'ed you with a SAIX-based Test account, you're welcome to test with it to see what's up. You may need to stay connected for 15 to 20 minutes to get an accurate reading.
 
AfriGenie said:
I've just PM'ed you with a SAIX-based Test account, you're welcome to test with it to see what's up. You may need to stay connected for 15 to 20 minutes to get an accurate reading.
Click to expand...

Cool beans will check it out.
 
moedawood said:
Thanks for the update Afrihost!

I'm assuming by 8.8.8.8 working again, the blacklist has been removed and we can use it again?
Click to expand...

It should be fine, but I would really recommend using our DNS. That way you will always route to the optimal CDN and local caches.
 
All Standard Paid Monthly Capped DSL Packages and Bundles, will receive Free‑Time until 30 November 2016, at which point the offer will be revised or extended.
Click to expand...
So, what's happening? Will it be extended?
 
Afrigenie. Not sure if Afriman told you.

I tried the other account and the site still doesn't work for me. Seems to be working for everyone else except me.
 
KoolDaffy said:
Afrigenie. Not sure if Afriman told you.

I tried the other account and the site still doesn't work for me. Seems to be working for everyone else except me.
Click to expand...

Ah! Thanks for the update.

We'll need to start looking at settings that are specific to you. Can you switch back to your Afrihost account then open Command Prompt and enter ipconfig /all and PM me all of the details displayed.
 
AfriGenie said:
Ah! Thanks for the update.

We'll need to start looking at settings that are specific to you. Can you switch back to your Afrihost account then open Command Prompt and enter ipconfig /all and PM me all of the details displayed.
Click to expand...

Sent :)
 
Test account is working so far,2nd hop keeps bombing out tho. Youtube ran 720p on my 4mb line and browsing is fine.


Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms login.router [10.0.0.2]
2 * * * Request timed out.
3 31 ms 37 ms 41 ms 196.43.31.250
4 11 ms 10 ms 10 ms 196.43.31.253
5 32 ms 32 ms 32 ms rrba-ip-lir-1-gig-3-0-0.telkom-ipnet.co.za [196.43.11.134]
6 31 ms 30 ms 31 ms 72.14.212.1
7 35 ms 33 ms 33 ms 72.14.239.117
8 85 ms 86 ms 80 ms google-public-dns-a.google.com [8.8.8.8]


one minute later,but browsing still fine

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms login.router [10.0.0.2]
2 * * * Request timed out.
3 354 ms 377 ms 390 ms 196.43.31.250
4 521 ms 450 ms 384 ms 196.43.31.253
5 189 ms 172 ms 180 ms rrba-ip-lir-1-gig-3-0-0.telkom-ipnet.co.za [196.43.11.134]
6 202 ms 184 ms 181 ms 72.14.212.1
7 214 ms 187 ms 153 ms 72.14.239.117
8 263 ms 235 ms 225 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.


Tracing route to www.afrihost.com [104.20.31.244]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms login.router [10.0.0.2]
2 * * * Request timed out.
3 266 ms 285 ms 315 ms 196.43.31.250
4 * * * Request timed out.
5 462 ms 458 ms 422 ms 196.43.48.158
6 163 ms 166 ms 166 ms rrba-ip-lir-1-gig-2-0-0-201.telkom-ipnet.co.za [196.43.33.5]
7 243 ms 207 ms 198 ms rrba-ip-se-2-gig-2-0-0-102.telkom-ipnet.co.za [196.43.25.138]
8 272 ms 273 ms * cloudflare.ixp.joburg [196.46.25.198]
9 407 ms 418 ms 486 ms www.afrihost.com [104.20.31.244]

Trace complete.

My account

Tracing route to www.afrihost.com [104.20.30.244]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms login.router [10.0.0.2]
2 * * * Request timed out.
3 211 ms 219 ms 202 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 152 ms 162 ms 180 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 177 ms 202 ms 228 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 270 ms 277 ms 289 ms 41.164.52.40
7 272 ms 312 ms 346 ms 172.18.1.162
8 208 ms 209 ms 239 ms cloudflare.ixp.joburg [196.46.25.198]
9 276 ms 267 ms 282 ms www.afrihost.com [104.20.30.244]


Thinking it could be telkom? packet loss/congestion from the dslam?
Even with the high pings browsing seems to be working and youtube.

Last night the browsing was very bad and the day before,could not buffer 240p on youtube.

My account is working better now,test account is slightly better tho.

Telkom "upgraded" the dslam two weeks ago to 4mb only from 2mb,so my guess is they put more people on the dslam and tried to compensate future issues with the higher speed.
 
Hope the double data and free time becomes permanent as well.

Or , bundle free time with Afrihost+
 
Gonzo.B said:
Test account is working so far,2nd hop keeps bombing out tho. Youtube ran 720p on my 4mb line and browsing is fine.


Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms login.router [10.0.0.2]
2 * * * Request timed out.
3 31 ms 37 ms 41 ms 196.43.31.250
4 11 ms 10 ms 10 ms 196.43.31.253
5 32 ms 32 ms 32 ms rrba-ip-lir-1-gig-3-0-0.telkom-ipnet.co.za [196.43.11.134]
6 31 ms 30 ms 31 ms 72.14.212.1
7 35 ms 33 ms 33 ms 72.14.239.117
8 85 ms 86 ms 80 ms google-public-dns-a.google.com [8.8.8.8]


one minute later,but browsing still fine

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms login.router [10.0.0.2]
2 * * * Request timed out.
3 354 ms 377 ms 390 ms 196.43.31.250
4 521 ms 450 ms 384 ms 196.43.31.253
5 189 ms 172 ms 180 ms rrba-ip-lir-1-gig-3-0-0.telkom-ipnet.co.za [196.43.11.134]
6 202 ms 184 ms 181 ms 72.14.212.1
7 214 ms 187 ms 153 ms 72.14.239.117
8 263 ms 235 ms 225 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.


Tracing route to www.afrihost.com [104.20.31.244]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms login.router [10.0.0.2]
2 * * * Request timed out.
3 266 ms 285 ms 315 ms 196.43.31.250
4 * * * Request timed out.
5 462 ms 458 ms 422 ms 196.43.48.158
6 163 ms 166 ms 166 ms rrba-ip-lir-1-gig-2-0-0-201.telkom-ipnet.co.za [196.43.33.5]
7 243 ms 207 ms 198 ms rrba-ip-se-2-gig-2-0-0-102.telkom-ipnet.co.za [196.43.25.138]
8 272 ms 273 ms * cloudflare.ixp.joburg [196.46.25.198]
9 407 ms 418 ms 486 ms www.afrihost.com [104.20.31.244]

Trace complete.

My account

Tracing route to www.afrihost.com [104.20.30.244]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms login.router [10.0.0.2]
2 * * * Request timed out.
3 211 ms 219 ms 202 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 152 ms 162 ms 180 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 177 ms 202 ms 228 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 270 ms 277 ms 289 ms 41.164.52.40
7 272 ms 312 ms 346 ms 172.18.1.162
8 208 ms 209 ms 239 ms cloudflare.ixp.joburg [196.46.25.198]
9 276 ms 267 ms 282 ms www.afrihost.com [104.20.30.244]


Thinking it could be telkom? packet loss/congestion from the dslam?
Even with the high pings browsing seems to be working and youtube.

Last night the browsing was very bad and the day before,could not buffer 240p on youtube.

My account is working better now,test account is slightly better tho.

Telkom "upgraded" the dslam two weeks ago to 4mb only from 2mb,so my guess is they put more people on the dslam and tried to compensate future issues with the higher speed.
Click to expand...

:(

I'm afraid if you're getting those sort of results with that SAIX account it means it's a line or Exchange issue.

Do we manage your DSL line?
 
AfriGenie said:
:(

I'm afraid if you're getting those sort of results with that SAIX account it means it's a line or Exchange issue.

Do we manage your DSL line?
Click to expand...

Nope it's with telkom,yeah i guessed it was with them.

3 phone calls and 2 port resets and they keep saying nothing is wrong with the exchange.

What sort of tests do they run lol We can clearly see there is fault with them
 
Gonzo.B said:
Nope it's with telkom,yeah i guessed it was with them.

3 phone calls and 2 port resets and they keep saying nothing is wrong with the exchange.

What sort of tests do they run lol We can clearly see there is fault with them
Click to expand...

There is definitely an issue, it may not be on the Exchange though, it could be on your physical line.

Best bet is to provide Telkom with those test results using your Afrihost account and the SAIX account that you used.
 
AfriGenie said:
There is definitely an issue, it may not be on the Exchange though, it could be on your physical line.

Best bet is to provide Telkom with those test results using your Afrihost account and the SAIX account that you used.
Click to expand...

Actually asked them specifically about that also,and they said nope nothing wrong. But i know something is up on their side,or on my line. Had this problem couple months back and it was the exchange and they fixed it.

Going to phone them again tomorrow,just hoping i can listen to some podcasts tonight,couldn't listen to them last night.
 
Something appears to have gone horribly wrong:

C:\>ping bras.afrihost.com

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=1856ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1517ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1368ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1413ms TTL=63

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

C:\>tracert bras.afrihost.com

Tracing route to bras.afrihost.com [155.239.255.250]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ARCHER_D7 [192.168.1.1]
2 1058 ms 1218 ms 1312 ms 155.239.255.250

Trace complete.
Click to expand...

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\>ping mybroadband.co.za

Pinging mybroadband.co.za [104.20.10.169] with 32 bytes of data:
Reply from 104.20.10.169: bytes=32 time=1077ms TTL=58
Reply from 104.20.10.169: bytes=32 time=1086ms TTL=58
Reply from 104.20.10.169: bytes=32 time=1158ms TTL=58
Reply from 104.20.10.169: bytes=32 time=1224ms TTL=58

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

C:\>tracert mybroadband.co.za

Tracing route to mybroadband.co.za [104.20.10.169]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ARCHER_D7 [192.168.1.1]
2 * * * Request timed out.
3 * * 1208 ms jhb-up3.ip.adsl.co.za [169.1.5.29]
4 1418 ms 1437 ms 1494 ms 169-1-5-250.ip.afrihost.co.za [169.1.5.250]
5 1693 ms 1848 ms 1374 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
6 1560 ms 1662 ms 1447 ms cloudflare.ixp.joburg [196.46.25.198]
7 1297 ms 1332 ms 1231 ms 104.20.10.169

Trace complete.
Click to expand...

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\>ping google.com

Pinging google.com [216.58.210.46] with 32 bytes of data:
Reply from 216.58.210.46: bytes=32 time=1411ms TTL=55
Reply from 216.58.210.46: bytes=32 time=1446ms TTL=55
Reply from 216.58.210.46: bytes=32 time=1398ms TTL=55
Reply from 216.58.210.46: bytes=32 time=1145ms TTL=55

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

C:\>tracert google.com

Tracing route to google.com [216.58.210.46]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ARCHER_D7 [192.168.1.1]
2 * * * Request timed out.
3 2005 ms * * jhb-up3.ip.adsl.co.za [169.1.5.29]
4 * 1148 ms 1260 ms 169-1-5-250.ip.afrihost.co.za [169.1.5.250]
5 1275 ms 1374 ms 1382 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
6 1421 ms 1437 ms 1161 ms 169-1-5-243.ip.afrihost.co.za [169.1.5.243]
7 968 ms 1030 ms 1099 ms 66.249.95.8
8 1144 ms 1138 ms 1241 ms 72.14.234.247
9 1676 ms 2101 ms 2235 ms 108.170.232.103
10 1847 ms 1343 ms 1453 ms lhr25s11-in-f14.1e100.net [216.58.210.46]

Trace complete.
Click to expand...
 
Gonzo.B said:
Actually asked them specifically about that also,and they said nope nothing wrong. But i know something is up on their side,or on my line. Had this problem couple months back and it was the exchange and they fixed it.

Going to phone them again tomorrow,just hoping i can listen to some podcasts tonight,couldn't listen to them last night.
Click to expand...

Let's hope they get on that for you :(
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X