Glad to hear it, I'm sure our rock stars will be able to assist further!
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: What is your employer's plan for the 30 June protests?
Afrihost CAPPED ADSL Feedback (MTN)
- Thread starter eddief1
- Start date
- Status
Glad to hear it, I'm sure our rock stars will be able to assist further!
@AfriGuy
+1 to the support team
Within one hour of submitting a ticket my internet has been restored to full speed!
Tracing route to www.google.com [74.125.233.49]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 5 ms 5 ms 5 ms 105-236-10-1-esr-lo.mtnbusiness.co.za [105.236.
0.1]
3 24 ms 24 ms 24 ms 41.181.222.42
4 26 ms 26 ms 26 ms ng-mse-1--ng-cr-2-a.za.mtnns.net [196.44.27.70]
5 21 ms 21 ms 21 ms jh-cr-2.za--ng-cr-2.za.mtnns.net [196.44.31.252
6 25 ms 24 ms 24 ms rb-cr-1.za--jh-cr-2.za-a.mtnns.net [196.44.31.9
]
7 24 ms 72 ms 24 ms qux--rb-dca-2.za-b.za.mtnbusiness.net [41.181.1
5.119]
8 25 ms 25 ms 23 ms 72.14.194.74
9 22 ms 21 ms 21 ms 64.233.174.21
10 25 ms 26 ms 25 ms jnb01s01-in-f17.1e100.net [74.125.233.49]
Trace complete.
+1 to the support team
Within one hour of submitting a ticket my internet has been restored to full speed!
Tracing route to www.google.com [74.125.233.49]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 5 ms 5 ms 5 ms 105-236-10-1-esr-lo.mtnbusiness.co.za [105.236.
0.1]
3 24 ms 24 ms 24 ms 41.181.222.42
4 26 ms 26 ms 26 ms ng-mse-1--ng-cr-2-a.za.mtnns.net [196.44.27.70]
5 21 ms 21 ms 21 ms jh-cr-2.za--ng-cr-2.za.mtnns.net [196.44.31.252
6 25 ms 24 ms 24 ms rb-cr-1.za--jh-cr-2.za-a.mtnns.net [196.44.31.9
]
7 24 ms 72 ms 24 ms qux--rb-dca-2.za-b.za.mtnbusiness.net [41.181.1
5.119]
8 25 ms 25 ms 23 ms 72.14.194.74
9 22 ms 21 ms 21 ms 64.233.174.21
10 25 ms 26 ms 25 ms jnb01s01-in-f17.1e100.net [74.125.233.49]
Trace complete.
Looking much better al4bb! Glad things are all sorted 
@AfriGuyLooking much better al4bb! Glad things are all sorted
Just pm'd you again - whatever was sorted sadly didn't last long
Tracing route to www.google.com [74.125.233.52]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 5 ms 5 ms 5 ms 105-236-10-1-esr-lo.mtnbusiness.co.za [105.236.1
0.1]
3 295 ms 287 ms 289 ms 41.181.222.42
4 294 ms 297 ms 298 ms ng-mse-1--ng-cr-2-a.za.mtnns.net [196.44.27.70]
5 285 ms 282 ms 289 ms jh-cr-2.za--ng-cr-2.za.mtnns.net [196.44.31.252]
6 300 ms 296 ms 301 ms rb-cr-1.za--jh-cr-2.za-a.mtnns.net [196.44.31.94
]
7 293 ms 278 ms 283 ms qux--rb-dca-2.za-b.za.mtnbusiness.net [41.181.16
5.119]
8 331 ms 298 ms 302 ms 72.14.194.74
9 304 ms 299 ms 290 ms 64.233.174.21
10 288 ms 285 ms 289 ms jnb01s01-in-f20.1e100.net [74.125.233.52]
Trace complete.
Hiya guys,
The problem I reported earlier appears to have been sorted out!
Could have been as AfriGirl suggested... possible exchange issue. Telkom couldn't find anything... but what's new.
Their IVR system indicated a problem with my account, however none of the 4 consultants I talked to could establish what was going on
Anyway here's a couple of tracert's for the record.
www.google.com
www.optimumonline.com
Speeds are back to normal - and are fairly solid at 3.4mbps on International connections.
Let's hope it stays that way.
Rgds,
SD
The problem I reported earlier appears to have been sorted out!
Could have been as AfriGirl suggested... possible exchange issue. Telkom couldn't find anything... but what's new.
Their IVR system indicated a problem with my account, however none of the 4 consultants I talked to could establish what was going on
Anyway here's a couple of tracert's for the record.
www.google.com
Code:
Tracing route to www.google.com [74.125.233.50]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 10 ms 10 ms 10 ms 105-236-8-65-esr-lo.mtnbusiness.co.za [105.236.8
.65]
3 13 ms 12 ms 12 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 13 ms 12 ms 13 ms 41.181.198.188
5 36 ms 36 ms 37 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 35 ms 56 ms 34 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 52 ms 33 ms 34 ms pb-ad-1.za--pb-sla-1-a.mtnns.net [196.44.31.128]
8 33 ms 33 ms 33 ms 41.181.139.109
9 54 ms 55 ms 56 ms 72.14.194.74
10 35 ms 34 ms 34 ms 64.233.174.21
11 58 ms 59 ms 58 ms jnb01s01-in-f18.1e100.net [74.125.233.50]
Trace complete.www.optimumonline.com
Code:
Tracing route to www.optimumonline.com [66.54.17.93]
over a maximum of 30 hops:
1 1 ms 1 ms 2 ms 192.168.0.1
2 11 ms 10 ms 11 ms 105-236-8-65-esr-lo.mtnbusiness.co.za [105.236.8
.65]
3 13 ms 13 ms 13 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 13 ms 14 ms 12 ms 41.181.184.28
5 13 ms 12 ms 13 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 14 ms 14 ms 14 ms 196.44.31.106
7 157 ms 156 ms 156 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.22
1]
8 157 ms 157 ms 156 ms ls-pr-2.uk--ls-cr-1.uk-a.mtn.net [209.212.111.20
3]
9 156 ms 156 ms 191 ms 195.50.122.181
10 260 ms 259 ms 259 ms 4.69.166.30
11 288 ms 260 ms 260 ms ae-58-223.ebr2.London1.Level3.net [4.69.153.137]
12 260 ms 263 ms 260 ms ae-41-41.ebr1.NewYork1.Level3.net [4.69.137.66]
13 284 ms 284 ms 293 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66]
14 282 ms 282 ms 282 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33]
15 259 ms 260 ms 259 ms ae-3-3.ebr2.Dallas1.Level3.net [4.69.137.121]
16 282 ms 283 ms 282 ms ae-62-62.csw1.Dallas1.Level3.net [4.69.151.129]
17 259 ms 259 ms 259 ms ae-11-60.car1.Dallas1.Level3.net [4.69.145.3]
18 262 ms 266 ms 262 ms EDS.car1.Dallas1.Level3.net [4.78.221.146]
19 * * * Request timed out.
20 * * * Request timed out.
21 261 ms 262 ms 261 ms 66.54.17.93
Trace complete.Let's hope it stays that way.
Rgds,
SD
Spoke too soon. Problem is back. Tracert's are showing the issue.
Code:
Tracing route to www.google.com [74.125.233.52]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.0.1
2 * 10 ms 10 ms 105-236-8-65-esr-lo.mtnbusiness.co.za [105.236.8
.65]
3 46 ms 39 ms 41 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 48 ms 44 ms 46 ms 41.181.198.188
5 99 ms 56 ms 52 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 41 ms 41 ms 39 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 86 ms 86 ms 86 ms pb-ad-1.za--pb-sla-1-a.mtnns.net [196.44.31.128]
8 79 ms 77 ms 74 ms 41.181.139.109
9 55 ms 59 ms 55 ms 72.14.194.74
10 82 ms 85 ms 84 ms 64.233.174.21
11 99 ms 100 ms 102 ms jnb01s01-in-f20.1e100.net [74.125.233.52]
Code:
Tracing route to www.optimumonline.com [66.54.17.93]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.0.1
2 10 ms 11 ms 10 ms 105-236-8-65-esr-lo.mtnbusiness.co.za [105.236.8
.65]
3 44 ms 46 ms 44 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 49 ms 49 ms 49 ms 41.181.184.28
5 66 ms 64 ms 62 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 73 ms 69 ms 69 ms 196.44.31.106
7 206 ms 203 ms 198 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.22
1]
8 215 ms 216 ms 219 ms ls-pr-2.uk--ls-cr-1.uk-a.mtn.net [209.212.111.20
3]
9 220 ms 222 ms 234 ms 195.50.122.181
10 316 ms 323 ms 313 ms 4.69.166.30
11 312 ms 312 ms 307 ms ae-58-223.ebr2.London1.Level3.net [4.69.153.137]
12 330 ms 332 ms 329 ms ae-41-41.ebr1.NewYork1.Level3.net [4.69.137.66]
13 302 ms 316 ms 305 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66]
14 292 ms 293 ms 293 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33]
15 330 ms 333 ms 329 ms ae-3-3.ebr2.Dallas1.Level3.net [4.69.137.121]
16 303 ms 304 ms 302 ms ae-62-62.csw1.Dallas1.Level3.net [4.69.151.129]
17 354 ms 355 ms 339 ms ae-11-60.car1.Dallas1.Level3.net [4.69.145.3]
18 311 ms 310 ms 312 ms EDS.car1.Dallas1.Level3.net [4.78.221.146]
19 * * * Request timed out.
20 * * * Request timed out.
21 317 ms 317 ms 322 ms 66.54.17.93
Trace complete.Hop 3 is showing major degradation.
Intl. speeds maxing out at 1.7mbps (as opposed to 3.4mbps in the earlier post).
http://www.speedtest.net/my-result/2813789180
Please help.
Rgds,
SD.
Last edited:
Hi steel_dog
I believe that we've logged this with our Networking guys already. A resolution should be on the cards soon.
I believe that we've logged this with our Networking guys already. A resolution should be on the cards soon.
Neat! Thanks for that. Appreciate it.
Any info you can share with regard to the nature of the issue?
I haven't received feedback from it yet, got off a call with one of our guys who say we're taking a look at it.
One from Durban, PMB and now CPT - so it's a bit tough to isolate at the moment. We'll post feedback as soon as it's available to us.
... and so it was for me until this morning. Then disasterous!
http://www.speedtest.net/my-result/2814847488
0.5mbps down and 0.2mbps up.
Code:
Tracing route to www.optimumonline.com [66.54.17.93] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 427 ms 381 ms 414 ms 105-236-8-65-esr-lo.mtnbusiness.co.za [105.236.8
.65]
3 135 ms 12 ms 12 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 679 ms 528 ms 665 ms 41.181.184.28
5 1252 ms 817 ms 653 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 623 ms 585 ms 639 ms 196.44.31.106
7 957 ms 583 ms 210 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.22
1]
8 870 ms 980 ms 1164 ms ls-pr-2.uk--ls-cr-1.uk-a.mtn.net [209.212.111.20
3]
9 645 ms 156 ms 170 ms 195.50.122.181
10 260 ms 259 ms 263 ms 4.69.166.30
11 260 ms 905 ms 975 ms ae-58-223.ebr2.London1.Level3.net [4.69.153.137]
12 935 ms 886 ms 853 ms ae-41-41.ebr1.NewYork1.Level3.net [4.69.137.66]
13 596 ms 291 ms 673 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66]
14 864 ms 884 ms 980 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33]
15 1122 ms 810 ms 259 ms ae-3-3.ebr2.Dallas1.Level3.net [4.69.137.121]
16 1766 ms 1860 ms 1589 ms ae-62-62.csw1.Dallas1.Level3.net [4.69.151.129]
17 1387 ms 752 ms 1014 ms ae-11-60.car1.Dallas1.Level3.net [4.69.145.3]
18 * 1007 ms 989 ms EDS.car1.Dallas1.Level3.net [4.78.221.146]
19 *
Code:
Tracing route to www.optimumonline.com [66.54.17.93] over a maximum of 30 hops:
1 1 ms <1 ms 1 ms 192.168.0.1
2 57 ms 10 ms 11 ms 105-236-8-65-esr-lo.mtnbusiness.co.za [105.236.8
.65]
3 1234 ms 1578 ms 1491 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 13 ms 12 ms 12 ms 41.181.184.28
5 16 ms 13 ms 15 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 16 ms 13 ms 13 ms 196.44.31.106
7 964 ms 1120 ms 164 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.22
1]
8 809 ms 1391 ms 1451 ms ls-pr-2.uk--ls-cr-1.uk-a.mtn.net [209.212.111.20
3]
9 1279 ms 156 ms 156 ms 195.50.122.181
10 1045 ms 259 ms 260 ms 4.69.166.30
11 434 ms 1847 ms 1836 ms ae-58-223.ebr2.London1.Level3.net [4.69.153.137]
12 1224 ms 305 ms 306 ms ae-41-41.ebr1.NewYork1.Level3.net [4.69.137.66]
13 1453 ms 1637 ms 1739 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66]
14 301 ms 306 ms 306 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33]
15 1036 ms 1126 ms 1043 ms ae-3-3.ebr2.Dallas1.Level3.net [4.69.137.121]
16 1204 ms 409 ms 1023 ms ae-62-62.csw1.Dallas1.Level3.net [4.69.151.129]
17 1633 ms 2047 ms 510 ms ae-11-60.car1.Dallas1.Level3.net [4.69.145.3]
18 833 ms 965 ms 1080 ms EDS.car1.Dallas1.Level3.net [4.78.221.146]
19 * *
... and so it was for me until this morning. Then disasterous!
http://www.speedtest.net/my-result/2814847488
0.5mbps down and 0.2mbps up.
Code:Tracing route to www.optimumonline.com [66.54.17.93] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 192.168.0.1 2 427 ms 381 ms 414 ms 105-236-8-65-esr-lo.mtnbusiness.co.za [105.236.8 .65] 3 135 ms 12 ms 12 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86] 4 679 ms 528 ms 665 ms 41.181.184.28 5 1252 ms 817 ms 653 ms unc-cpt-1.mtnns.net [196.44.18.8] 6 623 ms 585 ms 639 ms 196.44.31.106 7 957 ms 583 ms 210 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.22 1] 8 870 ms 980 ms 1164 ms ls-pr-2.uk--ls-cr-1.uk-a.mtn.net [209.212.111.20 3] 9 645 ms 156 ms 170 ms 195.50.122.181 10 260 ms 259 ms 263 ms 4.69.166.30 11 260 ms 905 ms 975 ms ae-58-223.ebr2.London1.Level3.net [4.69.153.137] 12 935 ms 886 ms 853 ms ae-41-41.ebr1.NewYork1.Level3.net [4.69.137.66] 13 596 ms 291 ms 673 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66] 14 864 ms 884 ms 980 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33] 15 1122 ms 810 ms 259 ms ae-3-3.ebr2.Dallas1.Level3.net [4.69.137.121] 16 1766 ms 1860 ms 1589 ms ae-62-62.csw1.Dallas1.Level3.net [4.69.151.129] 17 1387 ms 752 ms 1014 ms ae-11-60.car1.Dallas1.Level3.net [4.69.145.3] 18 * 1007 ms 989 ms EDS.car1.Dallas1.Level3.net [4.78.221.146] 19 *
Code:Tracing route to www.optimumonline.com [66.54.17.93] over a maximum of 30 hops: 1 1 ms <1 ms 1 ms 192.168.0.1 2 57 ms 10 ms 11 ms 105-236-8-65-esr-lo.mtnbusiness.co.za [105.236.8 .65] 3 1234 ms 1578 ms 1491 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86] 4 13 ms 12 ms 12 ms 41.181.184.28 5 16 ms 13 ms 15 ms unc-cpt-1.mtnns.net [196.44.18.8] 6 16 ms 13 ms 13 ms 196.44.31.106 7 964 ms 1120 ms 164 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.22 1] 8 809 ms 1391 ms 1451 ms ls-pr-2.uk--ls-cr-1.uk-a.mtn.net [209.212.111.20 3] 9 1279 ms 156 ms 156 ms 195.50.122.181 10 1045 ms 259 ms 260 ms 4.69.166.30 11 434 ms 1847 ms 1836 ms ae-58-223.ebr2.London1.Level3.net [4.69.153.137] 12 1224 ms 305 ms 306 ms ae-41-41.ebr1.NewYork1.Level3.net [4.69.137.66] 13 1453 ms 1637 ms 1739 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66] 14 301 ms 306 ms 306 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33] 15 1036 ms 1126 ms 1043 ms ae-3-3.ebr2.Dallas1.Level3.net [4.69.137.121] 16 1204 ms 409 ms 1023 ms ae-62-62.csw1.Dallas1.Level3.net [4.69.151.129] 17 1633 ms 2047 ms 510 ms ae-11-60.car1.Dallas1.Level3.net [4.69.145.3] 18 833 ms 965 ms 1080 ms EDS.car1.Dallas1.Level3.net [4.78.221.146] 19 * *
You have clearly exchange or dslam congestion, therefore the erratic behavior.
Tracing route to 66.54.17.93 over a maximum of 30 hops
1 1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 5 ms 5 ms 4 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 6 ms 6 ms 6 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 7 ms 5 ms 6 ms 41.181.184.28
5 8 ms 6 ms 6 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 7 ms 6 ms 7 ms 196.44.31.106
7 150 ms 149 ms 149 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.221]
8 150 ms 150 ms 149 ms ls-pr-2.uk--ls-cr-1.uk-a.mtn.net [209.212.111.203]
9 150 ms 150 ms 149 ms 195.50.122.181
10 279 ms 278 ms 278 ms 4.69.166.30
11 254 ms 254 ms 255 ms ae-57-222.ebr2.London1.Level3.net [4.69.153.133]
12 254 ms 254 ms 254 ms ae-44-44.ebr1.NewYork1.Level3.net [4.69.137.78]
13 254 ms 254 ms 253 ms ae-81-81.csw3.NewYork1.Level3.net [4.69.134.74]
14 279 ms 288 ms 277 ms ae-72-72.ebr2.NewYork1.Level3.net [4.69.148.37]
15 255 ms 254 ms 254 ms ae-3-3.ebr2.Dallas1.Level3.net [4.69.137.121]
16 254 ms 254 ms 254 ms ae-82-82.csw3.Dallas1.Level3.net [4.69.151.153]
17 254 ms 253 ms 328 ms ae-31-80.car1.Dallas1.Level3.net [4.69.145.131]
18 278 ms 278 ms 277 ms EDS.car1.Dallas1.Level3.net [4.78.221.146]
Hi steel_dog
Are you downloading/ utilising the line when running these tracerts? Hop 2 (being your exchange) is bringing back a result far too high above what it should be
As jannier says, this will affect the rest of your throughput.
Are you downloading/ utilising the line when running these tracerts? Hop 2 (being your exchange) is bringing back a result far too high above what it should be
As jannier says, this will affect the rest of your throughput.
Thanks man.
Not ruling that out however AfriGuy has indicated that the problem is known and is affecting Dbn, Pmb and CPT people. Exchange congestion would be a surprise given my battles with Telkom Internet from Feb regarding TI awful performance. Exchange congestion was investigated numerous times and ruled out (by them) as the cause. Speeds on backup ISP (FNB Connect) kinda supported them. Actually we now know the cause... routing and congestion on the backhaul (see the Telkom Intl. thread). Real-world testing through June with Axxess, Plugg, FNB Connection and Afrihost revealed no problems.
So... really do need AfriGuy to give us a progress update.
Post edited:
Dude! What are you up about? Refer your posts #308 and #310 please, where you indicated you are aware of an issue?!?!Hi steel_dog
Are you downloading/ utilising the line when running these tracerts? Hop 2 (being your exchange) is bringing back a result far too high above what it should be
As jannier says, this will affect the rest of your throughput.
I'm confused!
In response to
- Hop 2 being the exchange...
Perhaps... however we (meaning more than me) saw problems on Hop 3... mtn-mtn, which you acknowledged in your earlier post.
Hop 2 showing up as a problem today... can't comment... that's in Telkom Land and we know nothing useful comes out of that space.
Could this indicate possible IPC issues???... rather than DSLAM congestion.
Would suggest, given yesterdays and today's tracert's that it's not exchange.
Anyhow... a response to what the situation was yesterday that your networking guys were trying to resolve would be appreciated.
Refer your post #310 - Downloads running --> No - No downloads. Generally don't use the line for DLs.
Rgds,
SD.
Last edited:
Sorry if my posts have come across as contradictory
The recent traceroutes you've posted see high latency on hop 2, I was just pointing this out
I'm waiting for feedback on the increased latency over the network, seems like a fairly isolated fault though.
Could you perhaps drop me a PM with another trace result to see if the issues are still there?
Thanks for clearing that upSorry if my posts have come across as contradictory
The recent traceroutes you've posted see high latency on hop 2, I was just pointing this out
I'm waiting for feedback on the increased latency over the network, seems like a fairly isolated fault though.
Could you perhaps drop me a PM with another trace result to see if the issues are still there?
Will await feedback from your networking guys.
I'll re-test and send another tracert later this evening.
Rgds,
SD
Hi.
Still experiencing an issue with International.
Something isn't right
Latest speedtest's and tracert's below. http://www.speedtest.net/result/2816059337.png
http://www.speedtest.net/result/2816061985.png
Between 1mbps and 2mbps.
Local speeds are perfect!... so unlikely to be an exchange problem?!?
http://www.speedtest.net/result/2816082855.png
Anyway here are the tracerts...
Something's up with routing to Google. Different and longer routing than yesterday?!?!?
Code:
Tracing route to www.google.com [74.125.24.99]
over a maximum of 30 hops:
1 3 ms 1 ms 1 ms 192.168.0.1
2 13 ms 10 ms 11 ms 105-236-8-65-esr-lo.mtnbusiness.co.za [105.236.8
.65]
3 15 ms * 24 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
4 14 ms 13 ms 47 ms 41.181.198.188
5 15 ms 13 ms 17 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 16 ms 14 ms 14 ms 196.44.31.106
7 159 ms 157 ms 156 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.22
1]
8 184 ms 159 ms 159 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83
]
9 163 ms 156 ms 157 ms 195.66.224.125
10 162 ms 160 ms 161 ms 209.85.240.63
11 174 ms 167 ms 170 ms 209.85.253.92
12 172 ms 190 ms 167 ms 209.85.251.190
13 188 ms 166 ms 169 ms 72.14.235.139
14 * * * Request timed out.
15 191 ms 215 ms 196 ms de-in-f99.1e100.net [74.125.24.99]
Trace complete.
Code:
Tracing route to www.google.com [74.125.233.51]
over a maximum of 30 hops:
1 4 ms 4 ms 1 ms 192.168.0.1
2 10 ms 15 ms 10 ms 105-236-8-65-esr-lo.mtnbusiness.co.za [105.236.8
.65]
3 16 ms 17 ms 19 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
4 15 ms 13 ms 19 ms 41.181.198.188
5 19 ms 16 ms 17 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 15 ms 15 ms 18 ms 196.44.31.106
7 45 ms 39 ms 37 ms ct-cr-2.za--rb-cr-2.za-a.mtnns.net [196.44.31.30
]
8 77 ms 81 ms 78 ms 41.181.139.99
9 58 ms * 61 ms 72.14.194.74
10 39 ms 40 ms 37 ms 64.233.174.21
11 57 ms 56 ms 57 ms jnb01s01-in-f19.1e100.net [74.125.233.51]
Trace complete.
Code:
Tracing route to www.optimumonline.com [66.54.17.93]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 12 ms 11 ms 10 ms 105-236-8-65-esr-lo.mtnbusiness.co.za [105.236.8
.65]
3 13 ms 17 ms 12 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 19 ms 13 ms 13 ms 41.181.184.28
5 17 ms 15 ms 13 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 14 ms 16 ms 14 ms 196.44.31.106
7 176 ms * 161 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.22
1]
8 162 ms 161 ms 163 ms ls-pr-2.uk--ls-cr-1.uk-a.mtn.net [209.212.111.20
3]
9 166 ms 167 ms 165 ms 195.50.122.181
10 299 ms 260 ms 262 ms 4.69.166.30
11 266 ms 263 ms 262 ms ae-58-223.ebr2.London1.Level3.net [4.69.153.137]
12 265 ms 262 ms 262 ms ae-41-41.ebr1.NewYork1.Level3.net [4.69.137.66]
13 313 ms 295 ms 299 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66]
14 283 ms 284 ms 290 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33]
15 261 ms 264 ms 267 ms ae-3-3.ebr2.Dallas1.Level3.net [4.69.137.121]
16 295 ms 289 ms 291 ms ae-62-62.csw1.Dallas1.Level3.net [4.69.151.129]
17 259 ms 261 ms 262 ms ae-11-60.car1.Dallas1.Level3.net [4.69.145.3]
18 262 ms 262 ms 264 ms EDS.car1.Dallas1.Level3.net [4.78.221.146]
19 * * * Request timed out.
20 * * * Request timed out.
21 271 ms 269 ms 270 ms 66.54.17.93
Trace complete.
Last edited:
Your latency is looking much better compared to last night.
Regarding Google, it looks like your first trace landed up in Germany then on your second it landed on what looks like the local caching box.
I see you've also PM'ed me - lets rather keep things on PM? Will make it easier to track and not duplicate any typing
Could you PM me your current line sync speed?
The increased latency we chatted about last night has been resolved.
Regarding Google, it looks like your first trace landed up in Germany then on your second it landed on what looks like the local caching box.
I see you've also PM'ed me - lets rather keep things on PM? Will make it easier to track and not duplicate any typing
Could you PM me your current line sync speed?
The increased latency we chatted about last night has been resolved.
Hi.
Still experiencing an issue with International.
Something isn't right
http://www.speedtest.net/result/2816059337.png
http://www.speedtest.net/result/2816061985.png
Between 1mbps and 2mbps.
Local speeds are perfect!... so unlikely to be an exchange problem?!?
http://www.speedtest.net/result/2816082855.png
Anyway here are the tracerts...
Something's up with routing to Google. Different and longer routing than yesterday?!?!?
... and then it changed again about 2mins ago. Only 11 hops now.Code:Tracing route to www.google.com [74.125.24.99] over a maximum of 30 hops: 1 3 ms 1 ms 1 ms 192.168.0.1 2 13 ms 10 ms 11 ms 105-236-8-65-esr-lo.mtnbusiness.co.za [105.236.8 .65] 3 15 ms * 24 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214] 4 14 ms 13 ms 47 ms 41.181.198.188 5 15 ms 13 ms 17 ms unc-cpt-1.mtnns.net [196.44.18.8] 6 16 ms 14 ms 14 ms 196.44.31.106 7 159 ms 157 ms 156 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.22 1] 8 184 ms 159 ms 159 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83 ] 9 163 ms 156 ms 157 ms 195.66.224.125 10 162 ms 160 ms 161 ms 209.85.240.63 11 174 ms 167 ms 170 ms 209.85.253.92 12 172 ms 190 ms 167 ms 209.85.251.190 13 188 ms 166 ms 169 ms 72.14.235.139 14 * * * Request timed out. 15 191 ms 215 ms 196 ms de-in-f99.1e100.net [74.125.24.99] Trace complete.
Code:Tracing route to www.google.com [74.125.233.51] over a maximum of 30 hops: 1 4 ms 4 ms 1 ms 192.168.0.1 2 10 ms 15 ms 10 ms 105-236-8-65-esr-lo.mtnbusiness.co.za [105.236.8 .65] 3 16 ms 17 ms 19 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214] 4 15 ms 13 ms 19 ms 41.181.198.188 5 19 ms 16 ms 17 ms unc-cpt-1.mtnns.net [196.44.18.8] 6 15 ms 15 ms 18 ms 196.44.31.106 7 45 ms 39 ms 37 ms ct-cr-2.za--rb-cr-2.za-a.mtnns.net [196.44.31.30 ] 8 77 ms 81 ms 78 ms 41.181.139.99 9 58 ms * 61 ms 72.14.194.74 10 39 ms 40 ms 37 ms 64.233.174.21 11 57 ms 56 ms 57 ms jnb01s01-in-f19.1e100.net [74.125.233.51] Trace complete.
Code:Tracing route to www.optimumonline.com [66.54.17.93] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 192.168.0.1 2 12 ms 11 ms 10 ms 105-236-8-65-esr-lo.mtnbusiness.co.za [105.236.8 .65] 3 13 ms 17 ms 12 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86] 4 19 ms 13 ms 13 ms 41.181.184.28 5 17 ms 15 ms 13 ms unc-cpt-1.mtnns.net [196.44.18.8] 6 14 ms 16 ms 14 ms 196.44.31.106 7 176 ms * 161 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.22 1] 8 162 ms 161 ms 163 ms ls-pr-2.uk--ls-cr-1.uk-a.mtn.net [209.212.111.20 3] 9 166 ms 167 ms 165 ms 195.50.122.181 10 299 ms 260 ms 262 ms 4.69.166.30 11 266 ms 263 ms 262 ms ae-58-223.ebr2.London1.Level3.net [4.69.153.137] 12 265 ms 262 ms 262 ms ae-41-41.ebr1.NewYork1.Level3.net [4.69.137.66] 13 313 ms 295 ms 299 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66] 14 283 ms 284 ms 290 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33] 15 261 ms 264 ms 267 ms ae-3-3.ebr2.Dallas1.Level3.net [4.69.137.121] 16 295 ms 289 ms 291 ms ae-62-62.csw1.Dallas1.Level3.net [4.69.151.129] 17 259 ms 261 ms 262 ms ae-11-60.car1.Dallas1.Level3.net [4.69.145.3] 18 262 ms 262 ms 264 ms EDS.car1.Dallas1.Level3.net [4.78.221.146] 19 * * * Request timed out. 20 * * * Request timed out. 21 271 ms 269 ms 270 ms 66.54.17.93 Trace complete.
Speed test to servers are not really a reliable test.
There are way to much that could influence it.
However, I found that the OOKLA speedtest server in Amsterdam gives constant and accurate information.
MTN international routes via Amsterdam, so it is reliable to test international to that OOKLA server in Amsterdam.
Anything beyond that point is out of the control of MTN.
There are multiple sources being peered to from there, and any international link from that point can be congest, have a problem or even the server you trying to reach.
I am not trying to excuse Afrihost/MTN from there responsibilities, but there is also only so much under there control.
[URL=http://www.speedtest.net/my-result/2816266016]
[/URL]- Status