- Joined
- Jun 2, 2015
- Messages
- 2,830
- Reaction score
- 82
There is always the LTE route.![]()
Correct!
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
There is always the LTE route.![]()
There is always the LTE route.![]()
Wow, that is superfast.Nope can't get Telkom LTE where I live.
Vodacom LTE rocks on the other hand, but they are too expensive.
Check my recent speedtest from Vodacom : http://www.speedtest.net/my-result/a/1433034419![]()
@AfriFella,
Will you be continuing AfriGreen during October? It is working so well that I hardly used my other account.
Cool!So far it looks like Afrigreen is here to stay.![]()
So far it looks like Afrigreen is here to stay.![]()
Good.. been jamming some Trackmania and rock solid still.![]()
Whaaat a fellow Trackmania player!? Best. Game. Ever.
Pinging facebook.com [173.252.74.22] with 32 bytes of data:
Reply from 173.252.74.22: bytes=32 time=337ms TTL=69
Reply from 173.252.74.22: bytes=32 time=336ms TTL=69
Reply from 173.252.74.22: bytes=32 time=337ms TTL=69
Reply from 173.252.74.22: bytes=32 time=335ms TTL=69
Ping statistics for 173.252.74.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 335ms, Maximum = 337ms, Average = 336ms
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Users\Lara>tracert facebook.com
Tracing route to facebook.com [173.252.74.22]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 51 ms 51 ms 51 ms 41.170.79.229
4 58 ms 50 ms 52 ms 41.170.79.230
5 53 ms 50 ms 50 ms 41.170.79.236
6 49 ms 46 ms 45 ms 41.160.2.33
7 46 ms 46 ms 47 ms ix-0-3-0-0.tcore1.JSO-Johannesburg.as6453.net [216.6.55.37]
8 223 ms 225 ms 242 ms if-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
9 241 ms 344 ms 201 ms if-1-0-0-2.core2.PV9-Lisbon.as6453.net [195.219.214.30]
10 226 ms 226 ms 226 ms if-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.231.158.1]
11 231 ms 230 ms 230 ms if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
12 230 ms 230 ms 309 ms if-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
13 230 ms 230 ms 230 ms if-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
14 229 ms 230 ms 230 ms if-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
15 222 ms 222 ms 222 ms 195.219.83.102
16 * * * Request timed out.
17 359 ms * 359 ms ae-4-90.edge2.SanJose3.Level3.net [4.69.152.209]
18 360 ms 360 ms 360 ms 4.53.210.78
19 361 ms 361 ms 361 ms ae3.bb04.sjc1.tfbnw.net [31.13.26.166]
20 367 ms 366 ms 367 ms be22.bb01.prn2.tfbnw.net [31.13.25.196]
21 375 ms 376 ms 375 ms ae0.dr02.prn2.tfbnw.net [173.252.64.11]
22 * * * Request timed out.
23 * * * Request timed out.
24 365 ms 366 ms 365 ms edge-star-shv-04-prn2.facebook.com [173.252.74.22]
Trace complete.
I don't have browsing delays though.And it seems to not only be Facebook .. there is that browsing delay when opening pages again.
Yikes, Facebook has a long route.
Code:Microsoft Windows [Version 10.0.10240] (c) 2015 Microsoft Corporation. All rights reserved. C:\Users\Lara>tracert facebook.com Tracing route to facebook.com [173.252.74.22] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 * * * Request timed out. 3 51 ms 51 ms 51 ms 41.170.79.229 4 58 ms 50 ms 52 ms 41.170.79.230 5 53 ms 50 ms 50 ms 41.170.79.236 6 49 ms 46 ms 45 ms 41.160.2.33 7 46 ms 46 ms 47 ms ix-0-3-0-0.tcore1.JSO-Johannesburg.as6453.net [216.6.55.37] 8 223 ms 225 ms 242 ms if-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2] 9 241 ms 344 ms 201 ms if-1-0-0-2.core2.PV9-Lisbon.as6453.net [195.219.214.30] 10 226 ms 226 ms 226 ms if-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.231.158.1] 11 231 ms 230 ms 230 ms if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30] 12 230 ms 230 ms 309 ms if-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1] 13 230 ms 230 ms 230 ms if-11-2.tcore1.L78-London.as6453.net [80.231.139.42] 14 229 ms 230 ms 230 ms if-17-2.tcore1.LDN-London.as6453.net [80.231.130.130] 15 222 ms 222 ms 222 ms 195.219.83.102 16 * * * Request timed out. 17 359 ms * 359 ms ae-4-90.edge2.SanJose3.Level3.net [4.69.152.209] 18 360 ms 360 ms 360 ms 4.53.210.78 19 361 ms 361 ms 361 ms ae3.bb04.sjc1.tfbnw.net [31.13.26.166] 20 367 ms 366 ms 367 ms be22.bb01.prn2.tfbnw.net [31.13.25.196] 21 375 ms 376 ms 375 ms ae0.dr02.prn2.tfbnw.net [173.252.64.11] 22 * * * Request timed out. 23 * * * Request timed out. 24 365 ms 366 ms 365 ms edge-star-shv-04-prn2.facebook.com [173.252.74.22] Trace complete.
FB seems to have some issues ...
And it seems to not only be Facebook .. there is that browsing delay when opening pages again.
Test with my normal account via PPPoE. Think I'll stick to AfriGreen.Looks the same on my side too.Have you checked with your original account?
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Users\Lara>tracert facebook.com
Tracing route to facebook.com [173.252.74.22]
over a maximum of 30 hops:
1 * * * Request timed out.
2 * * * Request timed out.
3 24 ms 60 ms 24 ms 41.181.222.102
4 25 ms 24 ms 24 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 32 ms * 33 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 213 ms 210 ms 210 ms 196.44.29.40
7 171 ms 170 ms 171 ms caxtn-indust-1--jp-ad-1-a.mtnns.net [209.212.98.30]
8 211 ms 212 ms 210 ms 195.66.237.69
9 196 ms 196 ms 207 ms ae1.bb01.lhr2.tfbnw.net [31.13.30.174]
10 273 ms 272 ms 273 ms be11.bb01.ewr2.tfbnw.net [31.13.30.98]
11 286 ms 286 ms 286 ms be44.bb02.iad3.tfbnw.net [31.13.26.5]
12 317 ms 315 ms 317 ms ae4.bb03.prn2.tfbnw.net [31.13.27.243]
13 348 ms 349 ms 348 ms ae54.dr01.prn2.tfbnw.net [173.252.64.251]
14 * * * Request timed out.
15 * * * Request timed out.
16 322 ms 322 ms * edge-star-shv-04-prn2.facebook.com [173.252.74.22]
17 322 ms 322 ms 322 ms edge-star-shv-04-prn2.facebook.com [173.252.74.22]
Trace complete.
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Users\Lara>tracert facebook.com
Tracing route to facebook.com [173.252.74.22]
over a maximum of 30 hops:
1 * * * Request timed out.
2 24 ms 23 ms 24 ms wbs-ip-hsll-2-gi3-1-0-vl102.telkom-ipnet.co.za [105.226.0.29]
3 18 ms 17 ms 17 ms ipc-4-up.south.dsl.telkomsa.net [105.226.0.30]
4 17 ms 18 ms 16 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
5 161 ms 165 ms 160 ms 165.165.214.213
6 293 ms 283 ms 278 ms lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.43.9.58]
7 438 ms 438 ms 445 ms linx.br01.lhr1.tfbnw.net [195.66.225.69]
8 410 ms 416 ms 435 ms ae1.bb02.lhr2.tfbnw.net [31.13.30.198]
9 550 ms 542 ms 539 ms be21.bb01.lga1.tfbnw.net [173.252.65.52]
10 544 ms 541 ms 533 ms be29.bb01.dca1.tfbnw.net [74.119.78.78]
11 505 ms 485 ms 495 ms be21.bb01.prn2.tfbnw.net [74.119.76.61]
12 630 ms 621 ms 600 ms ae0.dr01.prn2.tfbnw.net [173.252.64.9]
13 * * * Request timed out.
14 * * * Request timed out.
15 629 ms 639 ms 628 ms edge-star-shv-04-prn2.facebook.com [173.252.74.22]
Trace complete.
Out of curiosity I tested with Telkom over PPPoE and it gave much higher latency figures.
Code:Microsoft Windows [Version 10.0.10240] (c) 2015 Microsoft Corporation. All rights reserved. C:\Users\Lara>tracert facebook.com Tracing route to facebook.com [173.252.74.22] over a maximum of 30 hops: 1 * * * Request timed out. 2 24 ms 23 ms 24 ms wbs-ip-hsll-2-gi3-1-0-vl102.telkom-ipnet.co.za [105.226.0.29] 3 18 ms 17 ms 17 ms ipc-4-up.south.dsl.telkomsa.net [105.226.0.30] 4 17 ms 18 ms 16 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57] 5 161 ms 165 ms 160 ms 165.165.214.213 6 293 ms 283 ms 278 ms lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.43.9.58] 7 438 ms 438 ms 445 ms linx.br01.lhr1.tfbnw.net [195.66.225.69] 8 410 ms 416 ms 435 ms ae1.bb02.lhr2.tfbnw.net [31.13.30.198] 9 550 ms 542 ms 539 ms be21.bb01.lga1.tfbnw.net [173.252.65.52] 10 544 ms 541 ms 533 ms be29.bb01.dca1.tfbnw.net [74.119.78.78] 11 505 ms 485 ms 495 ms be21.bb01.prn2.tfbnw.net [74.119.76.61] 12 630 ms 621 ms 600 ms ae0.dr01.prn2.tfbnw.net [173.252.64.9] 13 * * * Request timed out. 14 * * * Request timed out. 15 629 ms 639 ms 628 ms edge-star-shv-04-prn2.facebook.com [173.252.74.22] Trace complete.