Afrihost Uncapped ADSL Feedback

Status
Not open for further replies.
And now, for google :


Hourly :
google hourly.jpg

Daily :
google daily.jpg

Weekly :
google weekly.jpg



edit : reason why smokeping stats is not complete is that I forgot to add /etc/smokeping.dist to a startup script :o But it is fixed now, should restart automatically after a power failure (thanks for nothing eskom :mad:) or a reboot.
 
Last edited:
AfriMan said:
Last night latencies went a little bit ape! We are not sure what the actual cause is, there are theories involving backhaul and QoS, but I'd rather not post hearsay until I know what the actual story is.

What I do know is that MTN have got this back to normal sometime this morning. The extent to which all users experienced this is not certain, I was personally not online at all last night so I can't honestly add anything.

We've implementing some monitoring controls to identify these issues as an Early Warning System to avert things getting out of hand in the future. We'll also be addressing the shaping policies and QoS so that we can try to pin down exactly where these issues are arising from and how we can ensure best overall experience for everyone.

I see someone has taken to quoting me on Twitter. So as I've mentioned before, it's a learning curve for us, we're getting better at this everyday, and our goal is to eventually be the best network and service in the country. I have every confidence in our team.
Click to expand...

Thanks for the feedback :)

Should be interesting to hear what the root cause of the latency issues were... We all do make mistakes, no doubt somebody made a slight oopsie somewhere :D


edit : should look at if the latency spikes correlate with NZB downloads :o and tweak if it do. :o

But so far I don't have any serious problems.
 
Agreed. I'm viewing these teething troubles as just that. Still the best priced 10mb uncapped bundle, and for most of what I use it for it's great, and there's no reason the D3 latency issues won't be resolved soon...

Still seeing hectic packet loss and routing instability between telia and my IP at home:

1 64.208.27.93 (64.208.27.93) [AS 3549] 0.514 ms 0.501 ms 0.409 ms
2 MTN-DUBAI-LIMITED.TenGigabitEthernet1-4.ar8.AMS2.gblx.net (208.48.1.110) [AS 3549] 0.938 ms 0.965 ms 0.959 ms
3 am-tpr-1.nl--am-cr-2.nl-a.mtn.net (209.212.111.219) [AS 16637] 1.031 ms 0.996 ms 1.002 ms
MPLS Label=584490 CoS=0 TTL=1 S=1
4 ct-nt-1--rb-nt-1-b.mtnns.net (196.44.31.154) [AS 16637] 18.032 ms 8.769 ms 9.740 ms
MPLS Label=740390 CoS=0 TTL=1 S=1
5 tb-cr-2.za--ls-cr-1.uk.mtnns.net (196.44.31.240) [AS 16637] 157.343 ms tb-cr-2.za--ls-cr-1.uk.mtnns.net (196.44.31.112) [AS 16637] 164.395 ms tb-cr-2.za--ls-cr-1.uk.mtnns.net (196.44.31.240) [AS 16637] 156.994 ms
MPLS Label=512880 CoS=0 TTL=1 S=1
6 196.44.31.106 (196.44.31.106) [AS 16637] 157.388 ms ct-cr-2.za--tb-cr-1.za.mtnns.net (196.44.31.134) [AS 16637] 157.903 ms 157.666 ms
MPLS Label=790388 CoS=0 TTL=1 S=1
7 196.44.31.106 (196.44.31.106) [AS 16637] 157.472 ms ct-cr-2.za--ct-cr-1.za-a.mtnns.net (196.44.31.108) [AS 16637] 157.489 ms jh-dca-2.za--jh-cr-2.za-a.mtnns.net (196.44.0.225) [AS 16637] 192.930 ms
MPLS Label=790436 CoS=1 TTL=1 S=1
8 rb-cr-1.za--ct-cr-2.za-b.mtnns.net (196.44.31.250) [AS 16637] 174.938 ms 197.185 ms rb-cr-1.za--ct-cr-1.za.mtnns.net (196.44.31.128) [AS 16637] 174.942 ms
MPLS Label=646310 CoS=1 TTL=1 S=1
9 jh-cr-1.za--rb-cr-2.za.mtnns.net (196.44.0.42) [AS 16637] 177.208 ms 196.44.31.110 (196.44.31.110) [AS 16637] 180.514 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net (196.44.31.95) [AS 16637] 176.517 ms
MPLS Label=690160 CoS=1 TTL=1 S=1
10 41.181.180.11 (41.181.180.11) [AS 16637] 181.596 ms 174.446 ms 174.645 ms
11 * * *
12 jh-cr-2.za--jh-dca-2.za-a.mtnns.net (196.44.0.224) [AS 16637] 197.358 ms * ipc-send-jh-4a.za.mtnbusiness.net (41.181.178.45) [AS 16637] 185.000 ms
MPLS Label=686336 CoS=1 TTL=1 S=0
MPLS Label=308704 CoS=1 TTL=1 S=0
MPLS Label=509 CoS=1 TTL=1 S=1
13 rb-cr-1.za--jh-cr-2.za-a.mtnns.net (196.44.31.94) [AS 16637] 175.436 ms 198.463 ms 194.720 ms
MPLS Label=308704 CoS=1 TTL=1 S=0
MPLS Label=507 CoS=1 TTL=2 S=1
14 41.181.178.69 (41.181.178.69) [AS 16637] 175.185 ms 196.731 ms *
15 * * *
 
You guys on the forum are weird. Last night there is some high latency. Everyone is complaining on the forums that they are immediately cancelling their service, leaving bad reviews, setting reminders to not vote isp of the year at certain dates, twittering their hate. Today its ok, and everyone is like "Im holding out for a few months to see how the service it since its new." Fickle eh? I mentioned in another thread, it is normal in this country for the providers to have high latency from time to time. They are not on international level yet. Things do seem to be improving even since as little as 3 years ago.
 
Pete_A said:
You guys on the forum are weird. Last night there is some high latency. Everyone is complaining on the forums that they are immediately cancelling their service, leaving bad reviews, setting reminders to not vote isp of the year at certain dates, twittering their hate. Today its ok, and everyone is like "Im holding out for a few months to see how the service it since its new." Fickle eh? I mentioned in another thread, it is normal in this country for the providers to have high latency from time to time. They are not on international level yet. Things do seem to be improving even since as little as 3 years ago.
Click to expand...

Time to time fine, not every night and not with the high latency we have been getting. 300MS is beyond ridiculous.
 
To be fair,not everybody is experiencing it ^ My line has NEVER ran better
 
Sinbad said:
Do me a favour and run a traceroute to your IP from telia's looking glass in amsterdam?

http://looking-glass.telia.net/
Click to expand...

Code: 
Tracing route to juniperlg1-sn4.m-sp.skanova.net [81.228.10.74]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     4 ms     4 ms     4 ms  105-236-xx-xx-esr-lo.mtnbusiness.co.za [105.236.xx.xx]
  3     7 ms     6 ms     6 ms  ipc-recieve-jh-3a.za.mtnbusiness.net [41.181.17
.29]
  4     6 ms     6 ms     6 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.16
.115]
  5     7 ms     8 ms     7 ms  jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.1
5.114]
  6   180 ms   180 ms   182 ms  am-cr-2.nl--am-tpr-1.nl-a.mtn.net [209.212.111.
18]
  7   185 ms   185 ms   185 ms  xe-4-1-0.edge5.Amsterdam1.Level3.net [212.72.41
89]
  8   182 ms   181 ms   190 ms  4.69.162.137
  9   180 ms   180 ms   180 ms  ae-1-51.edge4.Amsterdam1.Level3.net [4.69.139.1
8]
 10   187 ms   185 ms   191 ms  Telia-level3-10g.Amsterdam1.level3.net [4.68.62
98]
 11   189 ms   230 ms   185 ms  adm-bb4-link.telia.net [80.91.247.66]
 12   187 ms   187 ms   186 ms  hbg-bb2-link.telia.net [80.91.245.125]
 13   196 ms   212 ms   195 ms  kbn-bb2-link.telia.net [213.155.134.204]
 14   197 ms   252 ms   194 ms  kbn-b4-link.telia.net [80.91.253.245]
 15   200 ms   215 ms   214 ms  ld-h-peer3-link.telia.net [80.91.253.89]
 16   207 ms   218 ms   211 ms  m-b-c5-link.se.telia.net [81.228.75.92]
 17   195 ms   196 ms   195 ms  m-sp-d3-link.se.telia.net [81.228.74.114]
 18   197 ms   196 ms   195 ms  semal11rs-link.fre.skanova.net [81.228.18.145]
 19   201 ms   201 ms   203 ms  juniperlg1-sn4.m-sp.skanova.net [81.228.10.74]

Trace complete.
 
No... not to. From.

browse there, select the amsterdam node, put in YOUR IP and paste the results :)
 
Sinbad said:
Do me a favour and run a traceroute to your IP from telia's looking glass in amsterdam?

http://looking-glass.telia.net/
Click to expand...

Here is one from CPT:

Code: 
traceroute to looking-glass.telia.net (81.228.10.74), 30 hops max, 60 byte packets
 1  192.168.1.1 (192.168.1.1)  0.290 ms  0.660 ms  0.650 ms
 2  105-236-8-65-esr-lo.mtnbusiness.co.za (105.236.8.65)  13.536 ms  16.295 ms  18.634 ms
 3  ipc-recieve-rb-3a.za.mtnbusiness.net (41.181.178.77)  45.465 ms  47.441 ms  49.633 ms
 4  rb-cr-1.za--rb-dca-1.za-a.mtnns.net (196.44.0.146)  55.068 ms  57.512 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net (196.44.31.120)  58.958 ms
 5  jh-cr-1.za--rb-cr-2.za.mtnns.net (196.44.0.42)  60.420 ms  62.875 ms  65.328 ms
 6  qux-jh-dca-2.za-b.za.mtnbusiness.net (41.181.165.115)  67.010 ms  33.000 ms  32.980 ms
 7  xe-4-1-0.edge5.Amsterdam1.Level3.net (212.72.41.89)  230.790 ms  231.803 ms  233.725 ms
 8  4.69.162.145 (4.69.162.145)  248.262 ms 4.69.162.137 (4.69.162.137)  247.254 ms 4.69.162.149 (4.69.162.149)  269.940 ms
 9  ae-2-52.edge4.Amsterdam1.Level3.net (4.69.139.170)  224.321 ms  226.747 ms ae-1-51.edge4.Amsterdam1.Level3.net (4.69.139.138)  231.298 ms
10  4.68.70.30 (4.68.70.30)  256.807 ms telia-level3-xe.amsterdam1.Level3.net (213.244.165.250)  253.445 ms 4.68.70.30 (4.68.70.30)  259.196 ms
11  adm-bb4-link.telia.net (213.155.132.172)  241.703 ms adm-bb4-link.telia.net (80.91.253.183)  264.103 ms adm-bb4-link.telia.net (80.91.247.66)  278.649 ms
12  hbg-bb2-link.telia.net (80.91.246.205)  254.937 ms hbg-bb1-link.telia.net (80.91.253.46)  265.541 ms hbg-bb2-link.telia.net (80.91.246.205)  216.544 ms
13  kbn-bb2-link.telia.net (213.155.130.103)  242.154 ms kbn-bb1-link.telia.net (80.91.249.204)  222.523 ms kbn-bb2-link.telia.net (213.155.133.27)  245.093 ms
14  kbn-b3-link.telia.net (213.155.135.173)  265.980 ms kbn-b4-link.telia.net (80.91.246.47)  305.388 ms kbn-b3-link.telia.net (80.91.252.23)  266.975 ms
15  ld-h-peer3-link.telia.net (213.155.133.255)  254.372 ms ld-h-peer3.telia.net (80.91.253.131)  255.341 ms ld-h-peer3-link.telia.net (213.155.133.253)  262.491 ms
16  m-b-c5-link.se.telia.net (81.228.75.92)  280.424 ms m-b-c5-link.se.telia.net (81.228.93.56)  257.374 ms m-b-c5-link.se.telia.net (81.228.74.92)  227.323 ms
17  m-sp-d3-link.se.telia.net (81.228.74.114)  253.403 ms  231.186 ms  245.279 ms
18  semal11rs-link.fre.skanova.net (81.228.18.145)  245.742 ms  250.970 ms  250.544 ms
19  juniperlg1-sn4.m-sp.skanova.net (81.228.10.74)  252.834 ms  237.836 ms  259.206 ms
 
My bad.

Here:

Code: 
traceroute to xxx-xxxx.myftp.org (105.236.xxx.xxx), 30 hops max, 40 byte packets
 1  te4-1-10G.ar2.AMS1.gblx.net (64.215.195.173) [AS  3549]  12.677 ms te8-3-10G.ar2.AMS1.gblx.net (64.215.195.17) [AS  3549]  0.482 ms te4-1-10G.ar2.AMS1.gblx.net (64.215.195.173) [AS  3549]  0.477 ms
 2  MTN-DUBAI-LIMITED.TenGigabitEthernet1-4.ar8.AMS2.gblx.net (208.48.1.110) [AS  3549]  1.030 ms  1.006 ms  1.004 ms
 3  am-cr-1.nl--am-tpr-1.nl-a.mtn.net (209.212.111.140) [AS  16637]  1.191 ms am-tpr-1.nl--am-cr-2.nl-a.mtn.net (209.212.111.219) [AS  16637]  1.095 ms  2.100 ms
     MPLS Label=584490 CoS=0 TTL=1 S=1
 4  ls-cr-1.uk--am-cr-2.nl-a.mtnns.net (196.44.31.154) [AS  16637]  8.963 ms  11.988 ms  9.860 ms
     MPLS Label=319703 CoS=0 TTL=1 S=1
 5  tb-cr-2.za--ls-cr-1.uk.mtnns.net (196.44.31.112) [AS  16637]  156.759 ms  156.655 ms  158.076 ms
     MPLS Label=736462 CoS=0 TTL=1 S=1
 6  196.44.31.106 (196.44.31.106) [AS  16637]  159.664 ms  161.394 ms  160.123 ms
     MPLS Label=430383 CoS=0 TTL=1 S=1
 7  196.44.31.106 (196.44.31.106) [AS  16637]  164.007 ms db-cr-2.za--ct-cr-2.za.mtnns.net (196.44.31.77) [AS  16637]  205.909 ms ct-cr-2.za--ct-cr-1.za-a.mtnns.net (196.44.31.108) [AS  16637]  157.781 ms
     MPLS Label=794724 CoS=1 TTL=1 S=1
 8  rb-cr-1.za--ct-cr-2.za-b.mtnns.net (196.44.31.250) [AS  16637]  220.523 ms  175.916 ms  175.834 ms
     MPLS Label=424519 CoS=1 TTL=1 S=1
 9  jh-cr-1.za--rb-cr-2.za.mtnns.net (196.44.0.42) [AS  16637]  177.571 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net (196.44.31.95) [AS  16637]  177.316 ms jh-cr-1.za--rb-cr-2.za.mtnns.net (196.44.0.42) [AS  16637]  177.464 ms
     MPLS Label=404050 CoS=0 TTL=1 S=1
10  jh-cr-2.za--rb-cr-1.za-a.mtnns.net (196.44.31.95) [AS  16637]  182.402 ms jh-dca-2.za--jh-cr-2.za-a.mtnns.net (196.44.0.225) [AS  16637]  177.290 ms  179.754 ms
     MPLS Label=686976 CoS=0 TTL=1 S=1
11  * * *
12  jh-cr-2.za--jh-dca-2.za-a.mtnns.net (196.44.0.224) [AS  16637]  180.901 ms  195.394 ms *
     MPLS Label=686336 CoS=1 TTL=1 S=0
     MPLS Label=308704 CoS=1 TTL=1 S=0
     MPLS Label=507 CoS=1 TTL=1 S=1
13  rb-cr-1.za--jh-cr-2.za-a.mtnns.net (196.44.31.94) [AS  16637]  198.845 ms * 41.181.178.57 (41.181.178.57) [AS  16637]  200.228 ms
     MPLS Label=308704 CoS=1 TTL=1 S=0
     MPLS Label=508 CoS=1 TTL=2 S=1
14  * * 41.181.178.69 (41.181.178.69) [AS  16637]  196.391 ms
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
 
Last edited:
Pete_A said:
You guys on the forum are weird. Last night there is some high latency. Everyone is complaining on the forums that they are immediately cancelling their service, leaving bad reviews, setting reminders to not vote isp of the year at certain dates, twittering their hate. Today its ok, and everyone is like "Im holding out for a few months to see how the service it since its new." Fickle eh? I mentioned in another thread, it is normal in this country for the providers to have high latency from time to time. They are not on international level yet. Things do seem to be improving even since as little as 3 years ago.
Click to expand...


Errr not quote. I think we were all baffled regarding WHY it was so chaotic, yet the Site reported everything as being 100%. Its understood that there are always bound to be issues, but communication is key. If you report it and explain it, cool ill understand. No where (regarding last nights issue), has anyone stated they'd be cancelling their contracts. It was the last day of the month, so im only assuming there was some HEAVY downloads hit or massive increase in server usage for those people that still had cap which ultimately affected the uncapped users (us being shaped). I am interested though as to what the upper levels of downloads for a 2mb uncapped line would be, im hoping its around 200gigs a month.

AfriMan said:
Last night latencies went a little bit ape! We are not sure what the actual cause is, there are theories involving backhaul and QoS, but I'd rather not post hearsay until I know what the actual story is.

What I do know is that MTN have got this back to normal sometime this morning. The extent to which all users experienced this is not certain, I was personally not online at all last night so I can't honestly add anything.

We've implementing some monitoring controls to identify these issues as an Early Warning System to avert things getting out of hand in the future. We'll also be addressing the shaping policies and QoS so that we can try to pin down exactly where these issues are arising from and how we can ensure best overall experience for everyone.

I see someone has taken to quoting me on Twitter. So as I've mentioned before, it's a learning curve for us, we're getting better at this everyday, and our goal is to eventually be the best network and service in the country. I have every confidence in our team.
Click to expand...

Thanks for the feedback Afriman. Early this morning, my line went back to normal and started downloading the new Crysis 3 alpha stage at 220kbp/s :). Big ups to Afrihost. Been a subscriber since 2008/9 and will stay with afrihost.
 
Sinbad said:
;)

It seems that routing to the new ranges within MTN's AS is very broken from what I've seen. You won't see the results of this on an outbound traceroute.
Click to expand...

Mweb:
Code: 
traceroute to 41.133.**.** (41.133.**.**), 30 hops max, 40 byte packets
 1  cogent-ic-151320-adm-b5.c.telia.net (80.239.128.238)  2.303 ms cogent-ic-143007-adm-b5.c.telia.net (80.239.160.14)  6.783 ms  9.987 ms
 2  te0-2-0-7.ccr22.ams03.atlas.cogentco.com (154.54.36.129) [AS  174]  10.053 ms te0-0-0-7.mpd21.ams03.atlas.cogentco.com (130.117.2.61) [AS  174]  2.652 ms te0-0-0-7.mpd22.ams03.atlas.cogentco.com (130.117.49.9) [AS  174]  10.955 ms
 3  te0-2-0-0.ccr22.lon13.atlas.cogentco.com (130.117.1.170) [AS  174]  21.444 ms te0-2-0-0.mpd21.lon13.atlas.cogentco.com (130.117.38.125) [AS  174]  13.160 ms te0-0-0-0.ccr22.lon13.atlas.cogentco.com (130.117.1.225) [AS  174]  10.435 ms
 4  te0-2-0-1.ccr22.lon01.atlas.cogentco.com (154.54.57.166) [AS  174]  11.901 ms 154.54.74.69 (154.54.74.69) [AS  174]  9.246 ms te0-2-0-0.ccr22.lon01.atlas.cogentco.com (154.54.57.174) [AS  174]  11.775 ms
 5  te2-1.ccr01.lon09.atlas.cogentco.com (154.54.36.170) [AS  174]  11.007 ms  10.172 ms  9.994 ms
 6  149.6.98.18 (149.6.98.18) [AS  174]  18.583 ms 149.6.98.6 (149.6.98.6) [AS  174]  18.083 ms  18.682 ms
 7  176.67.177.146 (176.67.177.146) [AS  10474]  205.741 ms 176.67.177.129 (176.67.177.129) [AS  10474]  204.237 ms 176.67.177.145 (176.67.177.145) [AS  10474]  207.217 ms
     MPLS Label=1048279 CoS=1 TTL=255 S=1
 8  pos0-3-0-0.vic-p-1.mweb.co.za (197.80.5.6) [AS  10474]  207.410 ms  186.462 ms 176.67.177.162 (176.67.177.162) [AS  10474]  196.679 ms
     MPLS Label=16379 CoS=1 TTL=255 S=0
     MPLS Label=16240 CoS=1 TTL=255 S=1
 9  pos0-3-0-0.vic-p-1.mweb.co.za (197.80.5.6) [AS  10474]  193.730 ms  194.721 ms vl-11.vic-hscore-1.mweb.co.za (196.22.169.227) [AS  10474]  200.034 ms
     MPLS Label=16190 CoS=1 TTL=255 S=0
     MPLS Label=16240 CoS=1 TTL=255 S=1
10  tengig-0-0-0-92.vic-ipc-2.mweb.co.za (196.22.189.18) [AS  10474]  211.530 ms tengig0-7-0-0.vic-p-2.mweb.co.za (197.84.4.36) [AS  10474]  196.697 ms  195.870 ms
     MPLS Label=16240 CoS=1 TTL=255 S=1
11  * vl-12.vic-hscore-2.mweb.co.za (196.22.169.243) [AS  10474]  193.372 ms *
12  * tengig-0-0-0-92.vic-ipc-2.mweb.co.za (196.22.189.18) [AS  10474]  193.190 ms *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

Afrihost:
Code: 
traceroute to 105.236.**.** (105.236.**.**), 30 hops max, 40 byte packets
 1  te4-1-10G.ar2.AMS1.gblx.net (64.215.195.173) [AS  3549]  0.477 ms  0.470 ms te8-3-10G.ar2.AMS1.gblx.net (64.215.195.17) [AS  3549]  0.446 ms
 2  MTN-DUBAI-LIMITED.TenGigabitEthernet1-4.ar8.AMS2.gblx.net (208.48.1.110) [AS  3549]  0.933 ms  1.066 ms  0.935 ms
 3  am-tpr-1.nl--am-cr-2.nl-a.mtn.net (209.212.111.219) [AS  16637]  1.256 ms  6.460 ms  0.977 ms
     MPLS Label=590090 CoS=0 TTL=1 S=1
 4  ct-nt-1--rb-nt-1-b.mtnns.net (196.44.31.154) [AS  16637]  26.402 ms  8.875 ms  8.705 ms
     MPLS Label=319671 CoS=0 TTL=1 S=1
 5  tb-cr-2.za--ls-cr-1.uk.mtnns.net (196.44.31.240) [AS  16637]  157.011 ms tb-cr-2.za--ls-cr-1.uk.mtnns.net (196.44.31.112) [AS  16637]  156.640 ms tb-cr-2.za--ls-cr-1.uk.mtnns.net (196.44.31.240) [AS  16637]  166.238 ms
     MPLS Label=512896 CoS=0 TTL=1 S=1
 6  tb-cr-2.za--tb-cr-1.za-a.mtnns.net (196.44.31.5) [AS  16637]  179.971 ms jh-cr-2.za--jh-cr-1.za-a.mtnns.net (196.44.31.255) [AS  16637]  203.007 ms ct-cr-2.za--tb-cr-1.za.mtnns.net (196.44.31.134) [AS  16637]  161.619 ms
     MPLS Label=794868 CoS=0 TTL=1 S=1
 7  ct-cr-2.za--ct-cr-1.za-a.mtnns.net (196.44.31.108) [AS  16637]  160.023 ms 196.44.31.106 (196.44.31.106) [AS  16637]  167.056 ms db-cr-2.za--ct-cr-2.za.mtnns.net (196.44.31.77) [AS  16637]  205.751 ms
     MPLS Label=339913 CoS=0 TTL=1 S=1
 8  rb-cr-1.za--ct-cr-2.za-b.mtnns.net (196.44.31.250) [AS  16637]  175.962 ms  182.809 ms  194.442 ms
     MPLS Label=424551 CoS=1 TTL=1 S=1
 9  jh-cr-2.za--rb-cr-1.za-a.mtnns.net (196.44.31.95) [AS  16637]  177.163 ms  202.826 ms  179.703 ms
     MPLS Label=686960 CoS=1 TTL=1 S=1
10  41.181.180.11 (41.181.180.11) [AS  16637]  179.464 ms  174.624 ms *
11  * * ipc-send-jh-2a.za.mtnbusiness.net (41.181.178.21) [AS  16637]  183.340 ms
12  * jh-cr-2.za--jh-dca-2.za-a.mtnns.net (196.44.0.224) [AS  16637]  216.011 ms ipc-send-jh-1a.za.mtnbusiness.net (41.181.178.9) [AS  16637]  217.328 ms
     MPLS Label=686336 CoS=1 TTL=1 S=0
     MPLS Label=308704 CoS=1 TTL=1 S=0
     MPLS Label=509 CoS=1 TTL=1 S=1
13  41.181.178.57 (41.181.178.57) [AS  16637]  175.575 ms rb-cr-1.za--jh-cr-2.za-a.mtnns.net (196.44.31.94) [AS  16637]  195.214 ms *
     MPLS Label=308704 CoS=1 TTL=1 S=0
     MPLS Label=508 CoS=1 TTL=2 S=1
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X