Afrihost New Network Feedback

Status
Not open for further replies.
Hey everyone,

I'm on Afrihost Capped with 10Mb Telkom line but recently have been syncing more than 25% slower (i.e. getting 750KBps down when I used to get 1MBps). Speed tests and everything are all 25% slower than perhaps a month ago.

I know there was some development with Telkom about their new system or something but that's about the extent of my knowledge on that matter.

I've been paying Telkom for a 10Mbps line but I'm getting slower speeds. So obviously (hopefully) it's not Afrihost at fault here since their capped account speeds go beyong 10Mbs. Who do I contact with regards to this 'issue'? Tried the whole log-a-fault on Telkom's website but it doesn't have the option of slower-than-expected line syncing nor does it allow one to type their own fault in.

Cheers
 
Voxratio said:
Hey everyone,

I'm on Afrihost Capped with 10Mb Telkom line but recently have been syncing more than 25% slower (i.e. getting 750KBps down when I used to get 1MBps). Speed tests and everything are all 25% slower than perhaps a month ago.

I know there was some development with Telkom about their new system or something but that's about the extent of my knowledge on that matter.

I've been paying Telkom for a 10Mbps line but I'm getting slower speeds. So obviously (hopefully) it's not Afrihost at fault here since their capped account speeds go beyong 10Mbs. Who do I contact with regards to this 'issue'? Tried the whole log-a-fault on Telkom's website but it doesn't have the option of slower-than-expected line syncing nor does it allow one to type their own fault in.

Cheers
Click to expand...

Hi :)

Slower syncs are never great, could very well be that your line's being stabilised by ASSIA.
Have you been able to get in touch with our Support team to determine the cause and run some tests?
 
AfriGuy said:
Hi :)

Slower syncs are never great, could very well be that your line's being stabilised by ASSIA.
Have you been able to get in touch with our Support team to determine the cause and run some tests?
Click to expand...

No, I have not yet. Didn't think it would help to contact Afrihost support with this specific issue but I'll file a ticket now. Thanks for the help
 
Voxratio said:
No, I have not yet. Didn't think it would help to contact Afrihost support with this specific issue but I'll file a ticket now. Thanks for the help
Click to expand...

Happy to help here too, up to you :)
Drop me a PM with the deets and I can see what's going on here.
 
I know off topic, but where do I go if one wanted to update from Windows 7 to windows 10? And also what is the size of the update? I'm trying to help a friend of mine, but not sure how or where lol
 
Icemanbrfc said:
I know off topic, but where do I go if one wanted to update from Windows 7 to windows 10? And also what is the size of the update? I'm trying to help a friend of mine, but not sure how or where lol
Click to expand...

We don't want to upgrade coz win 10 is spyware at the end of the day.

Nothing is "free", ever.
 
Vio said:
I just caught one. Here is what it looks like in my ping trace when it occurs:

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=18ms TTL=63
[...]

Pinging cpt-rx2.ip.adsl.co.za [169.1.5.82] with 32 bytes of data:
Reply from 169.1.5.82: bytes=32 time=14ms TTL=60
Reply from 169.1.5.82: bytes=32 time=13ms TTL=60
Reply from 169.1.5.82: bytes=32 time=12ms TTL=60
Reply from 169.1.5.82: bytes=32 time=12ms TTL=60
Reply from 169.1.5.82: bytes=32 time=12ms TTL=60
Reply from 169.1.5.82: bytes=32 time=12ms TTL=60
Reply from 169.1.5.82: bytes=32 time=14ms TTL=60
[...]

cpt-rx2.ip.adsl.co.za
Pinging 169.1.5.128 with 32 bytes of data:
Reply from 169.1.5.128: bytes=32 time=104ms TTL=60
Reply from 169.1.5.128: bytes=32 time=13ms TTL=60
Reply from 169.1.5.128: bytes=32 time=12ms TTL=60
Reply from 169.1.5.128: bytes=32 time=12ms TTL=60
Reply from 169.1.5.128: bytes=32 time=14ms TTL=60
Reply from 169.1.5.128: bytes=32 time=23ms TTL=60
Reply from 169.1.5.128: bytes=32 time=14ms TTL=60
Reply from 169.1.5.128: bytes=32 time=24ms TTL=60
Reply from 169.1.5.128: bytes=32 time=14ms TTL=60
Reply from 169.1.5.128: bytes=32 time=13ms TTL=60
Reply from 169.1.5.128: bytes=32 time=12ms TTL=60
Reply from 169.1.5.128: bytes=32 time=118ms TTL=60
Reply from 169.1.5.128: bytes=32 time=12ms TTL=60
Reply from 169.1.5.128: bytes=32 time=15ms TTL=60
Reply from 169.1.5.128: bytes=32 time=12ms TTL=60
Reply from 169.1.5.128: bytes=32 time=105ms TTL=60
Reply from 169.1.5.128: bytes=32 time=12ms TTL=60
Reply from 169.1.5.128: bytes=32 time=13ms TTL=60

Here's a tracert to the quake live server I am connecting to:
Tracing route to my.spikey.ninja [196.44.45.98]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 13 ms 12 ms 12 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 26 ms 22 ms 25 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 13 ms 13 ms 11 ms adept.ct1.napafrica.net [196.10.140.72]
6 57 ms 53 ms 57 ms v498.pe0.adc.adept.za.net [196.44.40.193]
7 16 ms 18 ms 14 ms g0-9.bb3.adc.adept.za.net [196.44.40.118]
8 34 ms 38 ms 43 ms my.spikey.ninja [196.44.45.98]

Trace complete.

The latency is primarily focused between that 3rd and 4th hop though I have seen pings to cpt-rx2.ip.adsl.co.za climb into the 30s randomly from time to time from low 12s. bras seems to be like a fortress always pinging relatively low to it 10-13ms.

These pings are ran in parallel btw.
Click to expand...

I'm really tired of sounding like a broken record but that 3rd to 4th hop is broken again latency wise tonight:

bras.afrihost.com:
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of dat
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63

cpt-rx2.ip.adsl.co.za (3rd hop):
Pinging cpt-rx2.ip.adsl.co.za [169.1.5.82] with 32 bytes of data:
Reply from 169.1.5.82: bytes=32 time=13ms TTL=59
Reply from 169.1.5.82: bytes=32 time=12ms TTL=59
Reply from 169.1.5.82: bytes=32 time=13ms TTL=59
Reply from 169.1.5.82: bytes=32 time=12ms TTL=59
Reply from 169.1.5.82: bytes=32 time=15ms TTL=59
Reply from 169.1.5.82: bytes=32 time=13ms TTL=59
Reply from 169.1.5.82: bytes=32 time=13ms TTL=59
Reply from 169.1.5.82: bytes=32 time=14ms TTL=59
Reply from 169.1.5.82: bytes=32 time=12ms TTL=59
Reply from 169.1.5.82: bytes=32 time=14ms TTL=59
Reply from 169.1.5.82: bytes=32 time=13ms TTL=59
Reply from 169.1.5.82: bytes=32 time=28ms TTL=59
Reply from 169.1.5.82: bytes=32 time=12ms TTL=59
Reply from 169.1.5.82: bytes=32 time=17ms TTL=59
Reply from 169.1.5.82: bytes=32 time=13ms TTL=59
Reply from 169.1.5.82: bytes=32 time=19ms TTL=59
Reply from 169.1.5.82: bytes=32 time=12ms TTL=59
Reply from 169.1.5.82: bytes=32 time=13ms TTL=59
Reply from 169.1.5.82: bytes=32 time=13ms TTL=59
Reply from 169.1.5.82: bytes=32 time=14ms TTL=59
Reply from 169.1.5.82: bytes=32 time=12ms TTL=59
Reply from 169.1.5.82: bytes=32 time=13ms TTL=59
Reply from 169.1.5.82: bytes=32 time=13ms TTL=59
Reply from 169.1.5.82: bytes=32 time=15ms TTL=59
Reply from 169.1.5.82: bytes=32 time=15ms TTL=59
Reply from 169.1.5.82: bytes=32 time=13ms TTL=59
Reply from 169.1.5.82: bytes=32 time=12ms TTL=59
Reply from 169.1.5.82: bytes=32 time=12ms TTL=59
Reply from 169.1.5.82: bytes=32 time=12ms TTL=59
Reply from 169.1.5.82: bytes=32 time=13ms TTL=59
Reply from 169.1.5.82: bytes=32 time=13ms TTL=59
Reply from 169.1.5.82: bytes=32 time=12ms TTL=59
Reply from 169.1.5.82: bytes=32 time=13ms TTL=59
Reply from 169.1.5.82: bytes=32 time=14ms TTL=59
Reply from 169.1.5.82: bytes=32 time=14ms TTL=59
Reply from 169.1.5.82: bytes=32 time=12ms TTL=59
Reply from 169.1.5.82: bytes=32 time=12ms TTL=59
Reply from 169.1.5.82: bytes=32 time=13ms TTL=59
Reply from 169.1.5.82: bytes=32 time=12ms TTL=59
Reply from 169.1.5.82: bytes=32 time=12ms TTL=59
Reply from 169.1.5.82: bytes=32 time=12ms TTL=59
Reply from 169.1.5.82: bytes=32 time=14ms TTL=59
Reply from 169.1.5.82: bytes=32 time=13ms TTL=59
Reply from 169.1.5.82: bytes=32 time=13ms TTL=59
Reply from 169.1.5.82: bytes=32 time=12ms TTL=59
Reply from 169.1.5.82: bytes=32 time=12ms TTL=59
Reply from 169.1.5.82: bytes=32 time=14ms TTL=59
Reply from 169.1.5.82: bytes=32 time=14ms TTL=59
Reply from 169.1.5.82: bytes=32 time=13ms TTL=59
Reply from 169.1.5.82: bytes=32 time=14ms TTL=59
Reply from 169.1.5.82: bytes=32 time=14ms TTL=59
Reply from 169.1.5.82: bytes=32 time=22ms TTL=59
Reply from 169.1.5.82: bytes=32 time=15ms TTL=59
Reply from 169.1.5.82: bytes=32 time=23ms TTL=59
Reply from 169.1.5.82: bytes=32 time=14ms TTL=59
Reply from 169.1.5.82: bytes=32 time=13ms TTL=59
Reply from 169.1.5.82: bytes=32 time=13ms TTL=59
Reply from 169.1.5.82: bytes=32 time=13ms TTL=59
Reply from 169.1.5.82: bytes=32 time=13ms TTL=59
Reply from 169.1.5.82: bytes=32 time=13ms TTL=59

169.1.5.128 aka cpt-net1.ip.adsl.co.za (the 4th hop)
Reply from 169.1.5.128: bytes=32 time=35ms TTL=61
Reply from 169.1.5.128: bytes=32 time=47ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=26ms TTL=61
Reply from 169.1.5.128: bytes=32 time=101ms TTL=61
Reply from 169.1.5.128: bytes=32 time=69ms TTL=61
Reply from 169.1.5.128: bytes=32 time=95ms TTL=61
Reply from 169.1.5.128: bytes=32 time=100ms TTL=61
Reply from 169.1.5.128: bytes=32 time=83ms TTL=61
Reply from 169.1.5.128: bytes=32 time=87ms TTL=61
Reply from 169.1.5.128: bytes=32 time=141ms TTL=61
Reply from 169.1.5.128: bytes=32 time=69ms TTL=61
Reply from 169.1.5.128: bytes=32 time=74ms TTL=61
Reply from 169.1.5.128: bytes=32 time=57ms TTL=61
Reply from 169.1.5.128: bytes=32 time=60ms TTL=61
Reply from 169.1.5.128: bytes=32 time=52ms TTL=61
Reply from 169.1.5.128: bytes=32 time=66ms TTL=61
Reply from 169.1.5.128: bytes=32 time=42ms TTL=61
Reply from 169.1.5.128: bytes=32 time=50ms TTL=61
Reply from 169.1.5.128: bytes=32 time=60ms TTL=61
Reply from 169.1.5.128: bytes=32 time=36ms TTL=61
Reply from 169.1.5.128: bytes=32 time=35ms TTL=61
Reply from 169.1.5.128: bytes=32 time=58ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=52ms TTL=61
Reply from 169.1.5.128: bytes=32 time=37ms TTL=61
Reply from 169.1.5.128: bytes=32 time=56ms TTL=61
Reply from 169.1.5.128: bytes=32 time=83ms TTL=61


All pings taken in parallel experience in game - trash.
 
It tends to happen between 5pm and 11pm; but that may just be because I pick up on it because I play latency dependent games during that period: it only happens on my Afrihost business uncapped unshaped 2mbit account and according to my traces the increased latency always manifests on their network between the connection from the 3rd to 4th hop aka: cpt-rx2.ip.adsl.co.za [169.1.5.82]'s connection to cpt-net1.ip.adsl.co.za [169.1.5.128]. I am in Durbanville area in CT if that helps.
 
Vio said:
It tends to happen between 5pm and 11pm; but that may just be because I pick up on it because I play latency dependent games during that period: it only happens on my Afrihost business uncapped unshaped 2mbit account and according to my traces the increased latency always manifests on their network between the connection from the 3rd to 4th hop aka: cpt-rx2.ip.adsl.co.za [169.1.5.82]'s connection to cpt-net1.ip.adsl.co.za [169.1.5.128]. I am in Durbanville area in CT if that helps.
Click to expand...

Are you on WiFi or LAN?
 
Vio said:
LAN.
Click to expand...

This only happens at night/evening?

Currently I have no problems on the 4th hop (pinging the same address as you):
Code: 
Pinging 169.1.5.128 with 32 bytes of data:
Reply from 169.1.5.128: bytes=32 time=25ms TTL=60
Reply from 169.1.5.128: bytes=32 time=32ms TTL=60
Reply from 169.1.5.128: bytes=32 time=27ms TTL=60
Reply from 169.1.5.128: bytes=32 time=25ms TTL=60
Reply from 169.1.5.128: bytes=32 time=27ms TTL=60
Reply from 169.1.5.128: bytes=32 time=25ms TTL=60
Reply from 169.1.5.128: bytes=32 time=25ms TTL=60
Reply from 169.1.5.128: bytes=32 time=24ms TTL=60
Reply from 169.1.5.128: bytes=32 time=24ms TTL=60
Reply from 169.1.5.128: bytes=32 time=25ms TTL=60
Reply from 169.1.5.128: bytes=32 time=24ms TTL=60
Reply from 169.1.5.128: bytes=32 time=25ms TTL=60
Reply from 169.1.5.128: bytes=32 time=25ms TTL=60
Reply from 169.1.5.128: bytes=32 time=23ms TTL=60
Reply from 169.1.5.128: bytes=32 time=49ms TTL=60
Reply from 169.1.5.128: bytes=32 time=24ms TTL=60
Reply from 169.1.5.128: bytes=32 time=24ms TTL=60
Reply from 169.1.5.128: bytes=32 time=25ms TTL=60
Reply from 169.1.5.128: bytes=32 time=27ms TTL=60
Reply from 169.1.5.128: bytes=32 time=24ms TTL=60
Reply from 169.1.5.128: bytes=32 time=24ms TTL=60
Reply from 169.1.5.128: bytes=32 time=29ms TTL=60

Ping statistics for 169.1.5.128:
    Packets: Sent = 22, Received = 22, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 23ms, Maximum = 49ms, Average = 26ms

The Afrihost reps don't work on Weekends, so let's build up a couple of pings and see if we both experience the same problem (just to try and isolate it a bit) and then the reps can check it out on Monday. I am in Cape Town as well.
 
AfriMan said:
You won't see airtime used for data on our side, because it only uses your airtime if you are using MTN's APN. If you're on ours, you'll just get capped.
Click to expand...

I've just seen your mobile airtime and data which is valid for 1 year. It might be just what I'm looking for. You show the courier delivery system but that costs R149. Do you have an office here in Port Elizabeth so I can do it myself?
 
Hi,

If you finish your cap, does the 12 - 6 uncapped not apply or is it just me?

I'm on the 100gb capped account.
 
C:\Users\m>tracert bbc.co.uk

Tracing route to www.bbc.co.uk [31.3.246.202]
over a maximum of 30 hops:

1 * * * Request timed out.
2 4 ms 3 ms 4 ms jhb-up3.ip.adsl.co.za [169.1.5.29]
3 5 ms 4 ms 4 ms jhb-in1.ip.adsl.co.za [169.1.5.42]
4 * 4 ms 4 ms jhb-up8b.ip.adsl.co.za [169.1.5.56]
5 4 ms 4 ms 4 ms 41.169.57.218
6 4 ms 4 ms 4 ms if-7-0.tcore2.JSO-Johannesburg.as6453.net [41.206.179.13]
7 180 ms 192 ms 180 ms if-2-2.tcore1.JSO-Johannesburg.as6453.net [216.6.55.85]
8 172 ms 175 ms 175 ms if-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
9 177 ms 177 ms 177 ms if-5-40.tcore2.PV9-Lisbon.as6453.net [80.231.159.89]
10 182 ms 182 ms 182 ms if-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
11 176 ms 175 ms 175 ms if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
12 178 ms 175 ms 175 ms if-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
13 179 ms 180 ms 179 ms if-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
14 175 ms 175 ms 175 ms if-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
15 176 ms 176 ms 176 ms be3040.ccr21.lon01.atlas.cogentco.com [130.117.15.177]
16 184 ms 184 ms 184 ms be2328.ccr21.lon02.atlas.cogentco.com [130.117.49.86]
17 179 ms 179 ms 183 ms 149.6.149.118
18 187 ms 187 ms 187 ms 205.dc9.redstation.co.uk [185.5.1.209]
19 184 ms 184 ms 184 ms 663.g21.r.dc9.redstation.co.uk [185.5.2.66]
20 179 ms 179 ms 179 ms h31-3-246-202.host.redstation.co.uk [31.3.246.202]

Trace complete.
Click to expand...

Excellent.
 
OK my internet got crippled, seacom again?

EDIT: seems to have recovered
 
Last edited:
My Internet is also crippled... At the other home on a 4meg capped 100gig account and getting a 380ms ping and download of 0.34mbps

http://www.speedtest.net/my-result/5044725682

1 <1 ms <1 ms <1 ms my.router [192.168.1.1]
2 488 ms 442 ms 432 ms 169-0-46-1.ip.afrihost.co.za [169.0.46.1]
3 477 ms 457 ms 384 ms jhb-up1.ip.adsl.co.za [169.1.5.5]
4 438 ms 466 ms 513 ms jhb-up7.ip.adsl.co.za [169.1.5.6]
5 443 ms 425 ms 418 ms jhb-up8b.ip.adsl.co.za [169.1.5.56]
6 472 ms 511 ms 477 ms 41.169.57.218
7 474 ms 439 ms 342 ms if-7-0.tcore1.JSO-Johannesburg.as6453.net [41.206.178.29]
8 564 ms 643 ms 620 ms if-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
9 636 ms 597 ms 500 ms Pos-channel6.core2.PV9-Lisbon.as6453.net [41.206.164.6]
10 529 ms 576 ms 634 ms if-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.231.158.1]
11 678 ms 627 ms 605 ms if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
12 631 ms 633 ms 596 ms if-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
13 610 ms 512 ms 519 ms if-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
14 513 ms 547 ms 559 ms if-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
15 628 ms 653 ms 664 ms 195.219.83.102
16 639 ms 588 ms 556 ms ae-232-3608.edge4.London1.Level3.net [4.69.166.29]
17 522 ms 515 ms 525 ms ae-232-3608.edge4.London1.Level3.net [4.69.166.29]
18 498 ms 535 ms 589 ms BBC-TECHNOL.edge4.London1.Level3.net [212.113.14.222]
19 * * * Request timed out.
20 513 ms 552 ms * ae0.er01.telhc.bbc.co.uk [132.185.254.109]
21 646 ms 645 ms 589 ms 132.185.255.148
22 672 ms 638 ms 598 ms 212.58.244.23
 
Last edited:
adamr said:
My Internet is also crippled... At the other home on a 4meg capped 100gig account and getting a 380ms ping and download of 0.34mbps

http://www.speedtest.net/my-result/5044725682

1 <1 ms <1 ms <1 ms my.router [192.168.1.1]
2 488 ms 442 ms 432 ms 169-0-46-1.ip.afrihost.co.za [169.0.46.1]
3 477 ms 457 ms 384 ms jhb-up1.ip.adsl.co.za [169.1.5.5]
4 438 ms 466 ms 513 ms jhb-up7.ip.adsl.co.za [169.1.5.6]
5 443 ms 425 ms 418 ms jhb-up8b.ip.adsl.co.za [169.1.5.56]
6 472 ms 511 ms 477 ms 41.169.57.218
7 474 ms 439 ms 342 ms if-7-0.tcore1.JSO-Johannesburg.as6453.net [41.206.178.29]
8 564 ms 643 ms 620 ms if-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
9 636 ms 597 ms 500 ms Pos-channel6.core2.PV9-Lisbon.as6453.net [41.206.164.6]
10 529 ms 576 ms 634 ms if-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.231.158.1]
11 678 ms 627 ms 605 ms if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
12 631 ms 633 ms 596 ms if-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
13 610 ms 512 ms 519 ms if-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
14 513 ms 547 ms 559 ms if-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
15 628 ms 653 ms 664 ms 195.219.83.102
16 639 ms 588 ms 556 ms ae-232-3608.edge4.London1.Level3.net [4.69.166.29]
17 522 ms 515 ms 525 ms ae-232-3608.edge4.London1.Level3.net [4.69.166.29]
18 498 ms 535 ms 589 ms BBC-TECHNOL.edge4.London1.Level3.net [212.113.14.222]
19 * * * Request timed out.
20 513 ms 552 ms * ae0.er01.telhc.bbc.co.uk [132.185.254.109]
21 646 ms 645 ms 589 ms 132.185.255.148
22 672 ms 638 ms 598 ms 212.58.244.23
Click to expand...

Would you mind also pinging bras.afrihost.com?
Mine:
Code: 
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\WINDOWS\System32>tracert 212.58.244.23

Tracing route to 212.58.244.23 over a maximum of 30 hops

  1     1 ms     2 ms     1 ms  home.gateway.pace.net [192.168.1.1]
  2     *        *        *     Request timed out.
  3    24 ms    25 ms    28 ms  cpt-up1.ip.adsl.co.za [169.1.5.105]
  4    27 ms    25 ms    25 ms  cpt-up2.ip.adsl.co.za [169.1.5.106]
  5    24 ms    24 ms    23 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6    26 ms    32 ms    25 ms  41.164.52.40
  7    25 ms    25 ms    25 ms  if-7-0.tcore1.KLT-Cape-Town.as6453.net [41.206.164.53]
  8   178 ms   172 ms   174 ms  if-5-40.tcore2.PV9-Lisbon.as6453.net [80.231.159.89]
  9   178 ms   176 ms   260 ms  if-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
 10   172 ms   173 ms   172 ms  if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
 11   177 ms   177 ms   176 ms  if-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
 12   177 ms   176 ms   177 ms  if-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
 13   173 ms   172 ms   173 ms  if-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
 14   172 ms   172 ms   172 ms  ^C
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X