Afrihost Capped ADSL Feedback (MTN) - New beginning

Status
Not open for further replies.
AfriGenie said:
Are you using our default DNS Servers 196.7.7.7 / 196.7.8.9?

If so, could you maybe switch to 196.7.7.7 / 8.8.8.8 and see if that changes the load times at all.
Click to expand...

My router is configured to take the first DNS server you provide, the second is the 8.8.8.8 one which is defined by me and then assign them by DHCP to the devices. My current configuration is 196.7.7.7. and 8.8.8.8. This was done some months ago when I had issues with your services.
 
Ovenmit said:
Our local arma server we run, again. 2 users (myself and another) on AH were experienceing terrible desync... simple ping test to the servers IP showed 50% packet loss. Ping was 12 though.

Switched to a Vox account and all was fine. Ping was a little higher (like 16 IRC), but no packet loss or desync.

The dedicated server is hosted at Hetzner if that matters.

I didnt test other services at the time.... was more interested in gaming.
Click to expand...

Would you be able to run a traceroute to your server at Hetzner, there maybe an issue with the routing if you are seeing that much packet loss to a server in South Africa.
 
terrya said:
I was using unblock-us. I swapped to a friend's Unotelly settings, problem persisted. I then removed all of that and reverted to your normal DNS and youtube streaming was still terrible. I did run speedtest a few times through the course of the evening and download speeds hovered between 7.5 and 8.5, which on my 10 mbps line is pretty much normal for me. I don't know if it's related, but I ran a WoW update which I believe uses P2P, and that seemed normal, but I can't really comment on that since I seldom, if ever, download torrents.
Click to expand...

It could be that you are being routed to the incorrect Youtube server, can you quickly run a traceroute to it please.
 
Sonic2k said:
My router is configured to take the first DNS server you provide, the second is the 8.8.8.8 one which is defined by me and then assign them by DHCP to the devices. My current configuration is 196.7.7.7. and 8.8.8.8. This was done some months ago when I had issues with your services.
Click to expand...

That's very strange... Can you then switch your secondary DNS to 196.7.8.9, I just want to make sure your Google traffic is being routed to the local server.
 
AfriGenie said:
Would you be able to run a traceroute to your server at Hetzner, there maybe an issue with the routing if you are seeing that much packet loss to a server in South Africa.
Click to expand...

Obviously looks good now.... lol

Code: 
Tracing route to WIN-INSN38I8IF7 [197.221.37.99]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.0.0.2 
  2     7 ms     7 ms     6 ms  105-236-240-129-esr-lo.mtnbusiness.co.za [105.236.240.129] 
  3     *        *        *     Request timed out.
  4    11 ms    23 ms    11 ms  41.181.222.102 
  5    12 ms    12 ms    11 ms  tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188] 
  6    12 ms    11 ms    11 ms  unc-cpt-1.mtnns.net [196.44.18.8] 
  7    12 ms    13 ms    13 ms  196.44.31.106 
  8    12 ms    12 ms    21 ms  nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121] 
  9    12 ms    12 ms    11 ms  africainx.cinx.net.za [196.223.22.47] 
 10    12 ms    11 ms    12 ms  CORE.WC-RO-HET-MEE-1.TO.WC-RO-MEC-2.AINX.P2P.10G.za [41.84.13.37] 
 11    12 ms    12 ms    11 ms  41-66-133-2-3.HET001-CPE-1-to-WC-RO-HET-MEE-1.africainx.net [41.66.133.2] 
 12    26 ms     *       15 ms  core-access-switch1-vlan1001.cpt.host-h.net [196.40.102.70] 
 13    13 ms    13 ms    12 ms  WIN-INSN38I8IF7 [197.221.37.99] 

Trace complete.

Code: 
Pinging 197.221.37.99 with 32 bytes of data:
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=12ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=12ms TTL=114
Reply from 197.221.37.99: bytes=32 time=14ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=12ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=12ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=24ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=24ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Request timed out.
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=14ms TTL=114
Reply from 197.221.37.99: bytes=32 time=12ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=12ms TTL=114
Reply from 197.221.37.99: bytes=32 time=12ms TTL=114
Reply from 197.221.37.99: bytes=32 time=12ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=12ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=23ms TTL=114
Reply from 197.221.37.99: bytes=32 time=12ms TTL=114
Reply from 197.221.37.99: bytes=32 time=24ms TTL=114
Reply from 197.221.37.99: bytes=32 time=12ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114

Ping statistics for 197.221.37.99:
    Packets: Sent = 38, Received = 37, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
    Minimum = 12ms, Maximum = 24ms, Average = 13ms
Control-C
 
AfriGenie said:
That's very strange... Can you then switch your secondary DNS to 196.7.8.9, I just want to make sure your Google traffic is being routed to the local server.
Click to expand...

No its not strange... I just know how the internet works.
I will do that and let you know, but I am not holding my breath..
 
Sonic2k said:
No its not strange... I just know how the internet works.
I will do that and let you know, but I am not holding my breath..
Click to expand...

I meant that it is strange that you are seeing poor performance on Google-related services, and not your DNS Settings. :)
 
Ovenmit said:
Obviously looks good now.... lol

Code: 
Tracing route to WIN-INSN38I8IF7 [197.221.37.99]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.0.0.2 
  2     7 ms     7 ms     6 ms  105-236-240-129-esr-lo.mtnbusiness.co.za [105.236.240.129] 
  3     *        *        *     Request timed out.
  4    11 ms    23 ms    11 ms  41.181.222.102 
  5    12 ms    12 ms    11 ms  tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188] 
  6    12 ms    11 ms    11 ms  unc-cpt-1.mtnns.net [196.44.18.8] 
  7    12 ms    13 ms    13 ms  196.44.31.106 
  8    12 ms    12 ms    21 ms  nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121] 
  9    12 ms    12 ms    11 ms  africainx.cinx.net.za [196.223.22.47] 
 10    12 ms    11 ms    12 ms  CORE.WC-RO-HET-MEE-1.TO.WC-RO-MEC-2.AINX.P2P.10G.za [41.84.13.37] 
 11    12 ms    12 ms    11 ms  41-66-133-2-3.HET001-CPE-1-to-WC-RO-HET-MEE-1.africainx.net [41.66.133.2] 
 12    26 ms     *       15 ms  core-access-switch1-vlan1001.cpt.host-h.net [196.40.102.70] 
 13    13 ms    13 ms    12 ms  WIN-INSN38I8IF7 [197.221.37.99] 

Trace complete.

Code: 
Pinging 197.221.37.99 with 32 bytes of data:
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=12ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=12ms TTL=114
Reply from 197.221.37.99: bytes=32 time=14ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=12ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=12ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=24ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=24ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Request timed out.
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=14ms TTL=114
Reply from 197.221.37.99: bytes=32 time=12ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=12ms TTL=114
Reply from 197.221.37.99: bytes=32 time=12ms TTL=114
Reply from 197.221.37.99: bytes=32 time=12ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=12ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114
Reply from 197.221.37.99: bytes=32 time=23ms TTL=114
Reply from 197.221.37.99: bytes=32 time=12ms TTL=114
Reply from 197.221.37.99: bytes=32 time=24ms TTL=114
Reply from 197.221.37.99: bytes=32 time=12ms TTL=114
Reply from 197.221.37.99: bytes=32 time=13ms TTL=114

Ping statistics for 197.221.37.99:
    Packets: Sent = 38, Received = 37, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
    Minimum = 12ms, Maximum = 24ms, Average = 13ms
Control-C
Click to expand...

It does look okay now... If the packet loss rears it's head again, can you run a traceroute then perhaps?
 
You shouldn't ever have to resort to a goodle DNS..... Your ISP's DNS's should be more than up to the task, So why does AH always reccomend that? Dont you trust your own DNS settings?
 
Ovenmit said:
You shouldn't ever have to resort to a goodle DNS..... Your ISP's DNS's should be more than up to the task, So why does AH always reccomend that? Dont you trust your own DNS settings?
Click to expand...

Yes I know, but the problem is I can't give them a piece of my mind, I will just pick up flack again. But I have a card up my sleeve ;)
 
Ovenmit said:
You shouldn't ever have to resort to a goodle DNS..... Your ISP's DNS's should be more than up to the task, So why does AH always reccomend that? Dont you trust your own DNS settings?
Click to expand...

I use those DNS settings myself, as I like having a bit of redundancy that if something does go wrong - not saying that it will - with either of those DNS servers, I still have a usable ADSL connection.
 
Supes said:
Yup, sucks big time. They replied again; it's been escalated, etc. That was over 24 hours ago, nothing yet.

I agree that there needs to be something implemented to safe guard against this type of thing.
I definitely want to know what happened and why it was allowed and will certainly push for reimbursement of the affected duration.
Click to expand...

This morning I received a SMS from Telkom informing me that there was a technician due at my house tomorrow sometime to "fulfill my service request". I have sent Afrihost another email about this and no reply.

This is becoming very, very annoying...
 
Code: 
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                   No response from host -  100 |   37 |    0 |    0 |    0 |    0 |    0 |
|                          41.181.222.101 -   95 |   38 |    2 |    0 |   25 |   26 |   25 |
|                          41.181.222.102 -   10 |  132 |  119 |   24 |   69 |  811 |   29 |
|   tb-dca-2.za--qux-c.za.mtnbusiness.net -    8 |  140 |  129 |   24 |   78 |  811 |   28 |
|                     unc-cpt-1.mtnns.net -   10 |  132 |  119 |   24 |   56 |  678 |   25 |
|        jh-cr-1.za--tb-cr-2.za.mtnns.net -   10 |  132 |  119 |   44 |   78 |  671 |   45 |
|     jh-dca-1.za--jh-cr-1.za-a.mtnns.net -    8 |  140 |  129 |   43 |   96 |  832 |   46 |
|       18.185.181.41.in-addr.aserv.co.za -    9 |  136 |  124 |   43 |   96 |  832 |   45 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

4501204032.png


^^ Just bombing along... surprised the network status is not green actually.... seems to be normal Afrihost performance...

Meanwhile...

Code: 
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                            41.193.121.9 -    0 |  149 |  149 |   21 |   36 |   38 |   22 |
|                           41.193.121.10 -    0 |  149 |  149 |   21 |   26 |   43 |   22 |
|                            209.203.1.41 -    0 |  149 |  149 |   20 |   23 |   48 |   22 |
|                          41.193.120.113 -    0 |  149 |  149 |   21 |   24 |   34 |   23 |
|                           41.193.120.94 -    0 |  149 |  149 |   21 |   22 |   35 |   22 |
|                          41.193.106.105 -    0 |  149 |  149 |   32 |   33 |   42 |   33 |
|                           41.193.106.97 -    0 |  149 |  149 |   32 |   36 |   54 |   34 |
|                          41.193.106.101 -    0 |  149 |  149 |   37 |   39 |   56 |   38 |
|                            41.193.32.29 -    0 |  149 |  149 |   38 |   41 |   53 |   38 |
|                          41.193.118.126 -    0 |  149 |  149 |   38 |   42 |   60 |   40 |
|                     mtnns-2.jinx.net.za -    0 |  149 |  149 |   41 |   48 |  110 |   51 |
|       jh-cr-1.za-jh-pr-1.za-a.mtnns.net -    0 |  150 |  150 |   40 |   42 |   74 |   42 |
|     jh-dca-1.za--jh-cr-1.za-a.mtnns.net -    0 |  150 |  150 |   39 |   45 |  137 |   40 |
|       18.185.181.41.in-addr.aserv.co.za -    0 |  149 |  149 |   39 |   44 |   76 |   49 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

4501214037.png
 
Last edited:
Supes said:
This morning I received a SMS from Telkom informing me that there was a technician due at my house tomorrow sometime to "fulfill my service request". I have sent Afrihost another email about this and no reply.

This is becoming very, very annoying...
Click to expand...

:(
Would you mind dropping me a PM with the deets? I can follow this up from there.
 
i.got~issues said:
Code: 
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                   No response from host -  100 |   37 |    0 |    0 |    0 |    0 |    0 |
|                          41.181.222.101 -   95 |   38 |    2 |    0 |   25 |   26 |   25 |
|                          41.181.222.102 -   10 |  132 |  119 |   24 |   69 |  811 |   29 |
|   tb-dca-2.za--qux-c.za.mtnbusiness.net -    8 |  140 |  129 |   24 |   78 |  811 |   28 |
|                     unc-cpt-1.mtnns.net -   10 |  132 |  119 |   24 |   56 |  678 |   25 |
|        jh-cr-1.za--tb-cr-2.za.mtnns.net -   10 |  132 |  119 |   44 |   78 |  671 |   45 |
|     jh-dca-1.za--jh-cr-1.za-a.mtnns.net -    8 |  140 |  129 |   43 |   96 |  832 |   46 |
|       18.185.181.41.in-addr.aserv.co.za -    9 |  136 |  124 |   43 |   96 |  832 |   45 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

4501204032.png


^^ Just bombing along... surprised the network status is not green actually.... seems to be normal Afrihost performance...

Meanwhile...

Code: 
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                   No response from host -  100 |   30 |    0 |    0 |    0 |    0 |    0 |
|                            41.193.121.9 -    0 |  149 |  149 |   21 |   36 |   38 |   22 |
|                           41.193.121.10 -    0 |  149 |  149 |   21 |   26 |   43 |   22 |
|                            209.203.1.41 -    0 |  149 |  149 |   20 |   23 |   48 |   22 |
|                          41.193.120.113 -    0 |  149 |  149 |   21 |   24 |   34 |   23 |
|                           41.193.120.94 -    0 |  149 |  149 |   21 |   22 |   35 |   22 |
|                          41.193.106.105 -    0 |  149 |  149 |   32 |   33 |   42 |   33 |
|                           41.193.106.97 -    0 |  149 |  149 |   32 |   36 |   54 |   34 |
|                          41.193.106.101 -    0 |  149 |  149 |   37 |   39 |   56 |   38 |
|                            41.193.32.29 -    0 |  149 |  149 |   38 |   41 |   53 |   38 |
|                          41.193.118.126 -    0 |  149 |  149 |   38 |   42 |   60 |   40 |
|                     mtnns-2.jinx.net.za -    0 |  149 |  149 |   41 |   48 |  110 |   51 |
|       jh-cr-1.za-jh-pr-1.za-a.mtnns.net -    0 |  150 |  150 |   40 |   42 |   74 |   42 |
|     jh-dca-1.za--jh-cr-1.za-a.mtnns.net -    0 |  150 |  150 |   39 |   45 |  137 |   40 |
|       18.185.181.41.in-addr.aserv.co.za -    0 |  149 |  149 |   39 |   44 |   76 |   49 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

4501214037.png
Click to expand...

I think we'll see a good turn around on this soon :)
 
i.got~issues said:
Soon

Soon

Soon

Soon

Soon

Is it Soon yet?

If not, how soon is soon?

If I put a space in soon, like thus;

so on

See... same old same old.
Click to expand...

As I've said before, I cannot confirm timeframes - however I'm hoping for some further news this week.
We also promised that feedback/ progress will be communicated - which is what we're doing as soon as it's being made available :)
 
Code: 
Pinging www.afrihost.co.za [41.181.185.18] with 32 bytes of data:
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Request timed out.
Reply from 41.181.185.18: bytes=32 time=30ms TTL=56
Reply from 41.181.185.18: bytes=32 time=30ms TTL=56
Reply from 41.181.185.18: bytes=32 time=30ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=30ms TTL=56
Reply from 41.181.185.18: bytes=32 time=32ms TTL=56
Request timed out.
Reply from 41.181.185.18: bytes=32 time=30ms TTL=56
Request timed out.
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=30ms TTL=56
Request timed out.
Reply from 41.181.185.18: bytes=32 time=32ms TTL=56
Request timed out.
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Request timed out.
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=30ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=30ms TTL=56
Request timed out.
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56

Ping statistics for 41.181.185.18:
    Packets: Sent = 43, Received = 36, Lost = 7 (16% loss),
Approximate round trip times in milli-seconds:
    Minimum = 30ms, Maximum = 32ms, Average = 30ms

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

  1    <1 ms    <1 ms    <1 ms  10.0.0.2 
  2    17 ms     6 ms     6 ms  105-236-240-129-esr-lo.mtnbusiness.co.za [105.236.240.129] 
  3     *        *       12 ms  41.181.222.101 
  4    11 ms    11 ms    11 ms  41.181.222.102 
  5    11 ms    11 ms    11 ms  tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188] 
  6    12 ms    12 ms    12 ms  unc-cpt-1.mtnns.net [196.44.18.8] 
  7    31 ms    31 ms    31 ms  pe-cr-2.za--el-mse-1.za.mtnns.net [196.44.31.66] 
  8    31 ms    31 ms    30 ms  jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217] 
  9    31 ms    31 ms    31 ms  18.185.181.41.in-addr.aserv.co.za [41.181.185.18] 

Trace complete.





... meh.
 
Ovenmit said:
Code: 
Pinging www.afrihost.co.za [41.181.185.18] with 32 bytes of data:
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Request timed out.
Reply from 41.181.185.18: bytes=32 time=30ms TTL=56
Reply from 41.181.185.18: bytes=32 time=30ms TTL=56
Reply from 41.181.185.18: bytes=32 time=30ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=30ms TTL=56
Reply from 41.181.185.18: bytes=32 time=32ms TTL=56
Request timed out.
Reply from 41.181.185.18: bytes=32 time=30ms TTL=56
Request timed out.
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=30ms TTL=56
Request timed out.
Reply from 41.181.185.18: bytes=32 time=32ms TTL=56
Request timed out.
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Request timed out.
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=30ms TTL=56
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56
Reply from 41.181.185.18: bytes=32 time=30ms TTL=56
Request timed out.
Reply from 41.181.185.18: bytes=32 time=31ms TTL=56

Ping statistics for 41.181.185.18:
    Packets: Sent = 43, Received = 36, Lost = 7 (16% loss),
Approximate round trip times in milli-seconds:
    Minimum = 30ms, Maximum = 32ms, Average = 30ms

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

  1    <1 ms    <1 ms    <1 ms  10.0.0.2 
  2    17 ms     6 ms     6 ms  105-236-240-129-esr-lo.mtnbusiness.co.za [105.236.240.129] 
  3     *        *       12 ms  41.181.222.101 
  4    11 ms    11 ms    11 ms  41.181.222.102 
  5    11 ms    11 ms    11 ms  tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188] 
  6    12 ms    12 ms    12 ms  unc-cpt-1.mtnns.net [196.44.18.8] 
  7    31 ms    31 ms    31 ms  pe-cr-2.za--el-mse-1.za.mtnns.net [196.44.31.66] 
  8    31 ms    31 ms    30 ms  jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217] 
  9    31 ms    31 ms    31 ms  18.185.181.41.in-addr.aserv.co.za [41.181.185.18] 

Trace complete.





... meh.
Click to expand...

Not looking great :( Are you also in the South?
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X