Afrihost Business Uncapped Feedback - 2

Status
Not open for further replies.
Hi AfriMan,

Our internet sucks again this morning. I have done a tracert (see below), and every time we have a problem, it is the same IP where things go wrong, namely, 41.181.221.218. Is this the local IPC or a crappy MTN router?




C:\WINDOWS\System32>tracert afrihost.com

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

1 2 ms 1 ms 2 ms 192.168.100.50
2 10 ms 13 ms 9 ms 105-236-0-65-esr-lo.mtnbusiness.co.za [105.236.0.65]
3 161 ms 169 ms 165 ms 41.181.221.218
4 178 ms 169 ms 172 ms rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.118]
5 179 ms 170 ms 177 ms rb-cr-1.za--rb-dca-2.mtnns.net [196.44.31.122]
6 180 ms 179 ms 180 ms 196.44.31.97
7 201 ms 194 ms 204 ms 196.31.220.10
8 178 ms 176 ms 181 ms 196.31.220.21
9 146 ms 142 ms 152 ms 196.31.63.202
10 179 ms 178 ms 169 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
11 183 ms 175 ms 170 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

Get similar result on wired computer as well.
 
10m line & account:

International
Download Speed: 247 kbps (30.9 KB/sec transfer rate)
Upload Speed: 724 kbps (90.5 KB/sec transfer rate)
Latency: 207 ms
10/17/2014, 9:05:03 AM
 
Tested Diablo 3 again and seeing lots of packet loss and the ping remains terrible at 1000ms+

Code:
Tracing route to 213-155-155-233.customer.teliacarrier.com [213.155.155.233]
over a maximum of 30 hops:
  0  PC [192.168.0.13]
  1  192.168.0.1
  2  105-236-4-193-esr-lo.mtnbusiness.co.za [105.236.4.193]
  3  41.181.51.182
  4  tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
  5  compj-cpt-1.mtnns.net [196.44.18.2]
  6  ls-cr-2.uk--tb-cr-1.za.mtnns.net [196.44.31.113]
  7  am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.183]
  8  am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.141]
  9  xe-4-1-0.edge5.Amsterdam1.Level3.net [212.72.41.89]
 10     *        *        *
Computing statistics for 225 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           PC [192.168.0.13]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.0.1
                                5/ 100 =  5%   |
  2   35ms    10/ 100 = 10%     5/ 100 =  5%  105-236-4-193-esr-lo.mtnbusiness.co.za [105.236.4.193]
                                0/ 100 =  0%   |
  3   36ms     9/ 100 =  9%     4/ 100 =  4%  41.181.51.182
                                0/ 100 =  0%   |
  4   43ms     9/ 100 =  9%     4/ 100 =  4%  tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
                                0/ 100 =  0%   |
  5   35ms     5/ 100 =  5%     0/ 100 =  0%  compj-cpt-1.mtnns.net [196.44.18.2]
                               95/ 100 = 95%   |
  6  ---     100/ 100 =100%     0/ 100 =  0%  ls-cr-2.uk--tb-cr-1.za.mtnns.net [196.44.31.113]
                                0/ 100 =  0%   |
  7  ---     100/ 100 =100%     0/ 100 =  0%  am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.183]
                                0/ 100 =  0%   |
  8  ---     100/ 100 =100%     0/ 100 =  0%  am-tpr-1.nl--am-cr-1.nl-a.mtn.net[209.212.111.141]
                                0/ 100 =  0%   |
  9  ---     100/ 100 =100%     0/ 100 =  0%  xe-4-1-0.edge5.Amsterdam1.Level3.net [212.72.41.89]
 
10m line & account:

International
Download Speed: 247 kbps (30.9 KB/sec transfer rate)
Upload Speed: 724 kbps (90.5 KB/sec transfer rate)
Latency: 207 ms
10/17/2014, 9:05:03 AM

Here's mine to Rosebank on a 8mb line

Last Result:
Download Speed: 1039 kbps (129.9 KB/sec transfer rate)
Upload Speed: 491 kbps (61.4 KB/sec transfer rate)
Latency: 26 ms
17/10/2014 10:17:48
 
Tracing route to www.google.com [74.125.133.103]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 8 ms 8 ms 105-236-11-193-esr-lo.mtnbusiness.co.za [105.236
.11.193]
3 11 ms 11 ms 14 ms ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178
.65]
4 13 ms 12 ms 12 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
5 13 ms 12 ms 14 ms jh-cr-2.za--rb-cr-1.za-b.mtnns.net [196.44.31.17
1]
6 12 ms 11 ms 11 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 254 ms 209 ms 209 ms ls-cr-2.uk--rb-cr-1.za.mtnns.net [196.44.31.114]

8 218 ms 214 ms 209 ms ls-cr-1.uk--ls-cr-2.uk-a.mtnns.net [196.44.31.15
6]
9 213 ms 213 ms 209 ms ls-pr-2.uk--ls-cr-1.uk-a.mtn.net [209.212.111.20
3]
10 224 ms 190 ms 194 ms rb-ad-1--msbm-rbg-1-a.mtnns.net [209.212.99.13]

11 196 ms 194 ms 195 ms 209.85.255.76
12 192 ms 191 ms 193 ms 209.85.244.240
13 215 ms 214 ms 222 ms 72.14.242.166
14 223 ms 200 ms 199 ms 216.239.46.56
15 * * * Request timed out.
16 215 ms 226 ms 217 ms 74.125.133.103

Trace complete.




And just some info for AfriMan: a Telkom tech was busy outside our property an hour ago and I politely asked him if he could check the line from the pole to our house and the connections, etc. They are all 100%. There is no attenuation issue on our line according to him.
And the attenuation specs I showed him using the AH test in the client zone is spot on with his tests and show no issues on that side.
There is also no intermittent issue that he can detect either.

So, when can I be expecting my "guaranteed full line speed at all times" that AH boasts about?
 
10m line & account:

International
Download Speed: 247 kbps (30.9 KB/sec transfer rate)
Upload Speed: 724 kbps (90.5 KB/sec transfer rate)
Latency: 207 ms
10/17/2014, 9:05:03 AM

That's definitely poor. We have put up a notice today to ensure that clients are aware that performance in the North is poor at the moment. Other regions should be performing better though :(
 
When capacity arrives. Should be in the next few weeks. In the meantime, full payment is still expected. :D

*Afrihost defines the term "few" as any number less than 52 and will not be held liable for any misinterpretation of the aforementioned term.
 
Tested Diablo 3 again and seeing lots of packet loss and the ping remains terrible at 1000ms+

Code:
Tracing route to 213-155-155-233.customer.teliacarrier.com [213.155.155.233]
over a maximum of 30 hops:
  0  PC [192.168.0.13]
  1  192.168.0.1
  2  105-236-4-193-esr-lo.mtnbusiness.co.za [105.236.4.193]
  3  41.181.51.182
  4  tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
  5  compj-cpt-1.mtnns.net [196.44.18.2]
  6  ls-cr-2.uk--tb-cr-1.za.mtnns.net [196.44.31.113]
  7  am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.183]
  8  am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.141]
  9  xe-4-1-0.edge5.Amsterdam1.Level3.net [212.72.41.89]
 10     *        *        *
Computing statistics for 225 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           PC [192.168.0.13]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.0.1
                                5/ 100 =  5%   |
  2   35ms    10/ 100 = 10%     5/ 100 =  5%  105-236-4-193-esr-lo.mtnbusiness.co.za [105.236.4.193]
                                0/ 100 =  0%   |
  3   36ms     9/ 100 =  9%     4/ 100 =  4%  41.181.51.182
                                0/ 100 =  0%   |
  4   43ms     9/ 100 =  9%     4/ 100 =  4%  tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
                                0/ 100 =  0%   |
  5   35ms     5/ 100 =  5%     0/ 100 =  0%  compj-cpt-1.mtnns.net [196.44.18.2]
                               95/ 100 = 95%   |
  6  ---     100/ 100 =100%     0/ 100 =  0%  ls-cr-2.uk--tb-cr-1.za.mtnns.net [196.44.31.113]
                                0/ 100 =  0%   |
  7  ---     100/ 100 =100%     0/ 100 =  0%  am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.183]
                                0/ 100 =  0%   |
  8  ---     100/ 100 =100%     0/ 100 =  0%  am-tpr-1.nl--am-cr-1.nl-a.mtn.net[209.212.111.141]
                                0/ 100 =  0%   |
  9  ---     100/ 100 =100%     0/ 100 =  0%  xe-4-1-0.edge5.Amsterdam1.Level3.net [212.72.41.89]


Strange that packet loss is so severe on that particular hop. Does this happen consistently on that particular hop?

Please run two or three traces and if the packet loss is consistent, I'll report this directly to MTN :(
 
Good Morning Guys

Before I reply to individual posts, I just want to let you know that we are aware of the Yosemite release this morning and we'll be monitoring very closely. The download is around 5GB and we're not sure how much this will impact us since we haven not as yet received our IPC upgrade.

We'll be working closely with MTN throughout the day should we see any direct effect on performance. I'd also like to humbly request than any Mac users hold off on downloading the OS during peak if possible and schedule their download when the network is quieter, this will really help all of us get a better experience.

Have an awesome Friday :)

This is a joke right? Some good natured humor to get the day going...............
Seriously appalled..You people have problems
 
Another day with terrible speeds... :(

I really cannot wait until the capacity has been increased.
 
Tracing route to www.google.com [74.125.133.103]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 8 ms 8 ms 105-236-11-193-esr-lo.mtnbusiness.co.za [105.236
.11.193]
3 11 ms 11 ms 14 ms ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178
.65]
4 13 ms 12 ms 12 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
5 13 ms 12 ms 14 ms jh-cr-2.za--rb-cr-1.za-b.mtnns.net [196.44.31.17
1]
6 12 ms 11 ms 11 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 254 ms 209 ms 209 ms ls-cr-2.uk--rb-cr-1.za.mtnns.net [196.44.31.114]

8 218 ms 214 ms 209 ms ls-cr-1.uk--ls-cr-2.uk-a.mtnns.net [196.44.31.15
6]
9 213 ms 213 ms 209 ms ls-pr-2.uk--ls-cr-1.uk-a.mtn.net [209.212.111.20
3]
10 224 ms 190 ms 194 ms rb-ad-1--msbm-rbg-1-a.mtnns.net [209.212.99.13]

11 196 ms 194 ms 195 ms 209.85.255.76
12 192 ms 191 ms 193 ms 209.85.244.240
13 215 ms 214 ms 222 ms 72.14.242.166
14 223 ms 200 ms 199 ms 216.239.46.56
15 * * * Request timed out.
16 215 ms 226 ms 217 ms 74.125.133.103

Trace complete.




And just some info for AfriMan: a Telkom tech was busy outside our property an hour ago and I politely asked him if he could check the line from the pole to our house and the connections, etc. They are all 100%. There is no attenuation issue on our line according to him.
And the attenuation specs I showed him using the AH test in the client zone is spot on with his tests and show no issues on that side.
There is also no intermittent issue that he can detect either.

So, when can I be expecting my "guaranteed full line speed at all times" that AH boasts about?

As per previous posts, you've reported several issues not consistent with other clients and I do think there is possibly something else going on in your case. However, if you're not willing to troubleshoot with us, the simple test will be to see if this goes away when we upgrade our IPC.
 
Hi AfriMan,

Our internet sucks again this morning. I have done a tracert (see below), and every time we have a problem, it is the same IP where things go wrong, namely, 41.181.221.218. Is this the local IPC or a crappy MTN router?




C:\WINDOWS\System32>tracert afrihost.com

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

1 2 ms 1 ms 2 ms 192.168.100.50
2 10 ms 13 ms 9 ms 105-236-0-65-esr-lo.mtnbusiness.co.za [105.236.0.65]
3 161 ms 169 ms 165 ms 41.181.221.218
4 178 ms 169 ms 172 ms rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.118]
5 179 ms 170 ms 177 ms rb-cr-1.za--rb-dca-2.mtnns.net [196.44.31.122]
6 180 ms 179 ms 180 ms 196.44.31.97
7 201 ms 194 ms 204 ms 196.31.220.10
8 178 ms 176 ms 181 ms 196.31.220.21
9 146 ms 142 ms 152 ms 196.31.63.202
10 179 ms 178 ms 169 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
11 183 ms 175 ms 170 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

Get similar result on wired computer as well.

I'm not seeing latency on our performance graphs, but given the demand on the network, it's very possible that we're not seeing the same results that some clients are seeing. We're pushing really hard to get the IPC in as quickly as possible and we're also looking for any possible ways to make traffic management more efficient :(
 
Another day with terrible speeds... :(

I really cannot wait until the capacity has been increased.

I really do believe it won't be long. Our technical director is in constant meetings with MTN to see how much more pressure we can apply to Telkom to deliver as quickly as possible.
 
Strange that packet loss is so severe on that particular hop. Does this happen consistently on that particular hop?

Please run two or three traces and if the packet loss is consistent, I'll report this directly to MTN :(

I've switched back to Axxess since Destiny started giving connection errors again. I didn't save the other traces I ran, but they all showed about the same amount of loss at the same hops.

Axxess gives better pings, but also shows packet loss (less severe). Not sure if traces from them would be any help.

Code:
AXXESS yesterday with bad ping
Computing statistics for 225 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           PC [192.168.0.9]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.0.1
                                6/ 100 =  6%   |
  2   31ms    20/ 100 = 20%    14/ 100 = 14%  105-236-4-193-esr-lo.mtnbusiness.co.za [105.236.4.193]
                                0/ 100 =  0%   |
  3   34ms    10/ 100 = 10%     4/ 100 =  4%  ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
                                0/ 100 =  0%   |
  4   32ms     6/ 100 =  6%     0/ 100 =  0%  tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
                                7/ 100 =  7%   |
  5   32ms    13/ 100 = 13%     0/ 100 =  0%  compj-cpt-1.mtnns.net [196.44.18.2]
                               87/ 100 = 87%   |
  6  ---     100/ 100 =100%     0/ 100 =  0%  ls-cr-2--tb-cr-1.uk-b.mtnns.net [196.44.31.113]
                                0/ 100 =  0%   |
  7  ---     100/ 100 =100%     0/ 100 =  0%  am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.183]
                                0/ 100 =  0%   |
  8  ---     100/ 100 =100%     0/ 100 =  0%  am-tpr-1.nl--am-cr-1.nl-a.mtn.net[209.212.111.141]
                                0/ 100 =  0%   |
  9  ---     100/ 100 =100%     0/ 100 =  0%  xe-4-1-0.edge5.Amsterdam1.Level3.net [212.72.41.89]

AXXESS today
Computing statistics for 225 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           PC [192.168.0.13]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.0.1
                                2/ 100 =  2%   |
  2   37ms     2/ 100 =  2%     0/ 100 =  0%  105-236-4-193-esr-lo.mtnbusiness.co.za [105.236.4.193]
                                1/ 100 =  1%   |
  3   34ms     6/ 100 =  6%     3/ 100 =  3%  41.181.221.254
                                0/ 100 =  0%   |
  4   32ms     4/ 100 =  4%     1/ 100 =  1%  tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
                                0/ 100 =  0%   |
  5   32ms     3/ 100 =  3%     0/ 100 =  0%  compj-cpt-1.mtnns.net [196.44.18.2]
                               97/ 100 = 97%   |
  6  ---     100/ 100 =100%     0/ 100 =  0%  ls-cr-2--tb-cr-1.uk-b.mtnns.net [196.44.31.113]
                                0/ 100 =  0%   |
  7  ---     100/ 100 =100%     0/ 100 =  0%  am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.183]
                                0/ 100 =  0%   |
  8  ---     100/ 100 =100%     0/ 100 =  0%  am-tpr-1.nl--am-cr-1.nl-a.mtn.net[209.212.111.141]
                                0/ 100 =  0%   |
  9  ---     100/ 100 =100%     0/ 100 =  0%  xe-4-1-0.edge5.Amsterdam1.Level3.net [212.72.41.89]


            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           PC [192.168.0.13]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.0.1
                                1/ 100 =  1%   |
  2   38ms     1/ 100 =  1%     0/ 100 =  0%  105-236-4-193-esr-lo.mtnbusiness.co.za [105.236.4.193]
                                3/ 100 =  3%   |
  3   39ms     4/ 100 =  4%     0/ 100 =  0%  41.181.221.254
                                0/ 100 =  0%   |
  4   33ms     4/ 100 =  4%     0/ 100 =  0%  tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
                                2/ 100 =  2%   |
  5   36ms     6/ 100 =  6%     0/ 100 =  0%  compj-cpt-1.mtnns.net [196.44.18.2]
                               94/ 100 = 94%   |
  6  ---     100/ 100 =100%     0/ 100 =  0%  ls-cr-2.uk--tb-cr-1.za.mtnns.net [196.44.31.113]
                                0/ 100 =  0%   |
  7  ---     100/ 100 =100%     0/ 100 =  0%  am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.183]
                                0/ 100 =  0%   |
  8  ---     100/ 100 =100%     0/ 100 =  0%  am-tpr-1.nl--am-cr-1.nl-a.mtn.net[209.212.111.141]
                                0/ 100 =  0%   |
  9  ---     100/ 100 =100%     0/ 100 =  0%  xe-4-1-0.edge5.Amsterdam1.Level3.net [212.72.41.89]

Trace complete.


            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           PC [192.168.0.13]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.0.1
                                0/ 100 =  0%   |
  2   28ms     3/ 100 =  3%     3/ 100 =  3%  105-236-4-193-esr-lo.mtnbusiness.co.za [105.236.4.193]
                                0/ 100 =  0%   |
  3   29ms     2/ 100 =  2%     2/ 100 =  2%  41.181.221.254
                                0/ 100 =  0%   |
  4   30ms     0/ 100 =  0%     0/ 100 =  0%  tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
                                4/ 100 =  4%   |
  5   28ms     4/ 100 =  4%     0/ 100 =  0%  compj-cpt-1.mtnns.net [196.44.18.2]
                               96/ 100 = 96%   |
  6  ---     100/ 100 =100%     0/ 100 =  0%  ls-cr-2--tb-cr-1.uk-b.mtnns.net [196.44.31.113]
                                0/ 100 =  0%   |
  7  ---     100/ 100 =100%     0/ 100 =  0%  am-cr-1.nl--ls-cr-2.uk-a.mtnns.net
 [196.44.31.183]
                                0/ 100 =  0%   |
  8  ---     100/ 100 =100%     0/ 100 =  0%  am-tpr-1.nl--am-cr-1.nl-a.mtn.net
[209.212.111.141]
                                0/ 100 =  0%   |
  9  ---     100/ 100 =100%     0/ 100 =  0%  xe-4-1-0.edge5.Amsterdam1.Level3.net [212.72.41.89]

Trace complete.
 
So just assuming here, if you look at the Afrihost Network Status page.

All regions except KZN mention IPC upgrades, does this mean only CPT & JHB IPC's will be receiving extra capacity?
 
It will definitely help. If the packet loss is consistently at the same hop, then it means it could be a backbone issue :(

From the previous traces and all the current ones that definitely looks like being the case. Unless I'm mistaken the hops are basically the same for Afrihost/Axxess aside from 1 server. The packet loss I'm seeing seems to occur at the same hops consistently.

Here's what a pathping looks like when getting 230ms ping on Axxess. (Think this was after 11PM)
Code:
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           PC [192.168.0.13]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.0.1
                                0/ 100 =  0%   |
  2   31ms     0/ 100 =  0%     0/ 100 =  0%  105-236-4-193-esr-lo.mtnbusiness.co.za [105.236.4.193]
                                0/ 100 =  0%   |
  3   34ms     0/ 100 =  0%     0/ 100 =  0%  ipc-recieve-tb-2a.mtnbusiness.net[41.181.54.86]
                                0/ 100 =  0%   |
  4   33ms     0/ 100 =  0%     0/ 100 =  0%  tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
                                0/ 100 =  0%   |
  5   29ms     0/ 100 =  0%     0/ 100 =  0%  compj-cpt-1.mtnns.net [196.44.18.2]
                              100/ 100 =100%   |
  6  ---     100/ 100 =100%     0/ 100 =  0%  ls-cr-2.uk--tb-cr-1.za.mtnns.net [196.44.31.113]
                                0/ 100 =  0%   |
  7  ---     100/ 100 =100%     0/ 100 =  0%  am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.183]
                                0/ 100 =  0%   |
  8  ---     100/ 100 =100%     0/ 100 =  0%  am-tpr-1.nl--am-cr-1.nl-a.mtn.net[209.212.111.141]
                                0/ 100 =  0%   |
  9  ---     100/ 100 =100%     0/ 100 =  0%  xe-4-1-0.edge5.Amsterdam1.Level3.net [212.72.41.89]

Trace complete.

As you can see the difference is the absence of any packet loss.

And here's the latest one showing same loss as in previous 4/5 on the same hops.
Code:
Computing statistics for 225 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           PC [192.168.0.13]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.0.1
                                3/ 100 =  3%   |
  2   32ms     5/ 100 =  5%     2/ 100 =  2%  105-236-4-193-esr-lo.mtnbusiness.co.za [105.236.4.193]
                                0/ 100 =  0%   |
  3   30ms     3/ 100 =  3%     0/ 100 =  0%  41.181.221.254
                                0/ 100 =  0%   |
  4   32ms     3/ 100 =  3%     0/ 100 =  0%  tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
                                1/ 100 =  1%   |
  5   29ms     4/ 100 =  4%     0/ 100 =  0%  compj-cpt-1.mtnns.net [196.44.18.2]
                               96/ 100 = 96%   |
  6  ---     100/ 100 =100%     0/ 100 =  0%  ls-cr-2.uk--tb-cr-1.za.mtnns.net [196.44.31.113]
                                0/ 100 =  0%   |
  7  ---     100/ 100 =100%     0/ 100 =  0%  am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.183]
                                0/ 100 =  0%   |
  8  ---     100/ 100 =100%     0/ 100 =  0%  am-tpr-1.nl--am-cr-1.nl-a.mtn.net[209.212.111.141]
                                0/ 100 =  0%   |
  9  ---     100/ 100 =100%     0/ 100 =  0%  xe-4-1-0.edge5.Amsterdam1.Level3.net [212.72.41.89]

Trace complete.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X