Using my unlocked Huawei E160 and my Airtel SIM Card (sent "start" t 544 to get 50MB for testing), I was able to sample Airtel's 3.75G... The following stats show you just how ugly it is - all local traffic seem to go out first, then back. KIXP is dead in so far as these guys are concerned, right? smtpout.accesskenya.com and 62.8.64.102 are hosted locally by AK and Zuku respectively, yet you can see the route to those via Airtel:( C:\Users\Washington>tracert www.gmail.com Tracing route to googlemail.l.google.com [74.125.236.85] over a maximum of 30 hops: 1 72 ms 79 ms 78 ms 172.16.5.4 2 76 ms 79 ms 79 ms 172.16.6.1 3 1039 ms 570 ms 69 ms 172.16.15.4 4 86 ms 79 ms 87 ms 172.16.12.2 5 75 ms 78 ms 79 ms 41.223.57.238 6 166 ms 159 ms 158 ms 41.223.59.142 7 175 ms 158 ms 169 ms 10.87.2.89 8 357 ms 328 ms 379 ms dsl-del-static-081.45.246.61.airtelbroadband.in [61.246.45.81] 9 1372 ms 595 ms 519 ms 64.211.193.85 10 387 ms 358 ms 369 ms 74.125.51.189 11 336 ms 345 ms 359 ms 209.85.252.76 12 1221 ms 652 ms 388 ms 216.239.46.224 13 1772 ms 805 ms 409 ms 66.249.95.149 14 436 ms 389 ms 399 ms 66.249.94.22 15 1198 ms 459 ms 619 ms 64.233.174.142 16 585 ms 558 ms 549 ms 64.233.174.179 17 555 ms 548 ms 599 ms 209.85.255.37 18 895 ms 929 ms 939 ms 64.233.175.2 19 926 ms 939 ms 959 ms 66.249.94.93 20 907 ms 969 ms 1323 ms 66.249.94.73 21 648 ms 639 ms 639 ms 209.85.249.235 22 911 ms 1099 ms 978 ms maa03s05-in-f21.1e100.net [74.125.236.85] Trace complete. C:\Users\Washington>ping -n 20 www.gmail.com Pinging googlemail.l.google.com [74.125.236.85] with 32 bytes of data: Reply from 74.125.236.85: bytes=32 time=870ms TTL=44 Reply from 74.125.236.85: bytes=32 time=896ms TTL=44 Reply from 74.125.236.85: bytes=32 time=892ms TTL=44 Reply from 74.125.236.85: bytes=32 time=808ms TTL=44 Reply from 74.125.236.85: bytes=32 time=835ms TTL=44 Reply from 74.125.236.85: bytes=32 time=803ms TTL=44 Reply from 74.125.236.85: bytes=32 time=907ms TTL=44 Reply from 74.125.236.85: bytes=32 time=865ms TTL=44 Reply from 74.125.236.85: bytes=32 time=800ms TTL=44 Reply from 74.125.236.85: bytes=32 time=855ms TTL=44 Reply from 74.125.236.85: bytes=32 time=821ms TTL=44 Reply from 74.125.236.85: bytes=32 time=860ms TTL=44 Reply from 74.125.236.85: bytes=32 time=741ms TTL=44 Reply from 74.125.236.85: bytes=32 time=657ms TTL=44 Reply from 74.125.236.85: bytes=32 time=674ms TTL=44 Reply from 74.125.236.85: bytes=32 time=651ms TTL=44 Reply from 74.125.236.85: bytes=32 time=687ms TTL=44 Reply from 74.125.236.85: bytes=32 time=713ms TTL=44 Reply from 74.125.236.85: bytes=32 time=658ms TTL=44 Reply from 74.125.236.85: bytes=32 time=894ms TTL=44 Ping statistics for 74.125.236.85: Packets: Sent = 20, Received = 20, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 651ms, Maximum = 907ms, Average = 794ms C:\Users\Washington>tracert smtpout.accesskenya.com Tracing route to smtpout.accesskenya.com [196.200.16.40] over a maximum of 30 hops: 1 363 ms 400 ms 397 ms 172.16.5.4 2 354 ms 509 ms 409 ms 172.16.6.1 3 356 ms 479 ms 449 ms 172.16.15.4 4 306 ms 431 ms 356 ms 172.16.12.2 5 352 ms 419 ms 697 ms 41.223.57.238 6 212 ms 209 ms 229 ms 41.223.59.142 7 195 ms 169 ms 168 ms 10.87.2.89 8 334 ms 339 ms 309 ms dsl-del-static-081.45.246.61.airtelbroadband.in [61.246.45.81] 9 1517 ms 626 ms 638 ms 64.211.193.85 10 584 ms 639 ms 661 ms ae5.scr3.LON3.gblx.net [67.17.72.22] 11 387 ms 408 ms 539 ms te9-2-10G.ar3.CDG2.gblx.net [67.16.148.145] 12 345 ms 349 ms 339 ms teleglobe-1.ar3.CDG2.gblx.net [64.208.27.42] 13 1281 ms 779 ms 819 ms if-2-2.tcore1.PYE-Paris.as6453.net[80.231.154.18] 14 794 ms 830 ms 817 ms if-8-1600.tcore1.WYN-Marseille.as6453.net[80.231.217.5] 15 562 ms 497 ms 489 ms if-9-5.tcore1.MLV-Mumbai.as6453.net[80.231.217.18] 16 423 ms * 578 ms if-11-0-0.core1.MLV-Mumbai.as6453.net[180.87.38.22] 17 * * * Request timed out. 18 596 ms * 831 ms TenGE-2-1-BP_CORE01.accesskenya.com[196.207.31.146] 19 586 ms 579 ms 579 ms bp-cr-core-datacenter.accesskenya.com[196.207.31.70] 20 1846 ms 918 ms 889 ms smtpout.accesskenya.com [196.200.16.40] Trace complete. C:\Users\Washington>tracert 62.8.64.102 Tracing route to gw.kictanet.or.ke [62.8.64.102] over a maximum of 30 hops: 1 149 ms 129 ms 68 ms 172.16.5.4 2 84 ms 80 ms 78 ms 172.16.6.1 3 75 ms 79 ms 79 ms 172.16.15.4 4 76 ms 68 ms 69 ms 172.16.12.2 5 85 ms 79 ms 78 ms 41.223.57.238 6 214 ms 229 ms 1699 ms 41.223.59.142 7 497 ms 964 ms 238 ms 10.87.2.89 8 364 ms 359 ms 1854 ms dsl-del-static-081.45.246.61.airtelbroadband.in [61.246.45.81] 9 634 ms 709 ms 639 ms 64.211.193.85 10 584 ms 884 ms 379 ms ae6.scr4.LON3.gblx.net [67.17.106.150] 11 314 ms 299 ms 299 ms te8-1-10GE.ar7.LON3.gblx.net [67.16.143.217] 12 1229 ms 1453 ms 446 ms tata-1.ar7.lon3.gblx.net [64.215.195.238] 13 320 ms 299 ms 309 ms if-14-1-0-466.core4.LDN-London.as6453.net[80.231.76.241] 14 460 ms 450 ms 447 ms ix-3-3-1.core4.LDN-London.as6453.net[195.219.195.214] 15 471 ms 459 ms 448 ms 41.212.32.41.wananchi.com [41.212.32.41] 16 413 ms 369 ms 379 ms g1-0-2.cr01.ke-nbi.wananchi.com[41.212.1.106] 17 379 ms 388 ms 389 ms 41.212.1.194.wananchi.com [41.212.1.194] 18 363 ms * * 41.212.1.46.wananchi.com [41.212.1.46] 19 677 ms 708 ms 709 ms gw.kictanet.or.ke [62.8.64.102] Trace complete. C:\Users\Washington>ping -n 20 62.8.64.102 Pinging 62.8.64.102 with 32 bytes of data: Request timed out. Reply from 62.8.64.102: bytes=32 time=395ms TTL=54 Reply from 62.8.64.102: bytes=32 time=392ms TTL=54 Reply from 62.8.64.102: bytes=32 time=397ms TTL=54 Reply from 62.8.64.102: bytes=32 time=373ms TTL=54 Reply from 62.8.64.102: bytes=32 time=379ms TTL=54 Reply from 62.8.64.102: bytes=32 time=1628ms TTL=54 Reply from 62.8.64.102: bytes=32 time=676ms TTL=54 Reply from 62.8.64.102: bytes=32 time=533ms TTL=54 Reply from 62.8.64.102: bytes=32 time=590ms TTL=54 Reply from 62.8.64.102: bytes=32 time=576ms TTL=54 Reply from 62.8.64.102: bytes=32 time=553ms TTL=54 Request timed out. Reply from 62.8.64.102: bytes=32 time=557ms TTL=54 Reply from 62.8.64.102: bytes=32 time=542ms TTL=54 Request timed out. Reply from 62.8.64.102: bytes=32 time=546ms TTL=54 Reply from 62.8.64.102: bytes=32 time=572ms TTL=54 Request timed out. Reply from 62.8.64.102: bytes=32 time=525ms TTL=54 Ping statistics for 62.8.64.102: Packets: Sent = 20, Received = 16, Lost = 4 (20% loss), Approximate round trip times in milli-seconds: Minimum = 373ms, Maximum = 1628ms, Average = 577ms ..and for me to RDP to a Desktop in the office (Wilson Airport), I have to take the path below: C:\Users\Washington>tracert 196.200.26.114 Tracing route to 196.200.26.114.accesskenya.com [196.200.26.114] over a maximum of 30 hops: 1 411 ms 489 ms 439 ms 172.16.5.4 2 365 ms 359 ms 398 ms 172.16.6.1 3 350 ms 79 ms 79 ms 172.16.15.4 4 76 ms 79 ms 118 ms 172.16.12.2 5 75 ms 79 ms 79 ms 41.223.57.238 6 175 ms 209 ms 159 ms 41.223.59.142 7 200 ms 190 ms 201 ms 10.87.2.89 8 325 ms 329 ms 378 ms dsl-del-static-081.45.246.61.airtelbroadband.in [61.246.45.81] 9 322 ms 329 ms 309 ms 64.211.193.85 10 304 ms 329 ms 329 ms ae5.scr3.LON3.gblx.net [67.17.72.22] 11 314 ms 329 ms 309 ms po10-20g.ar3.CDG2.gblx.net [67.16.130.221] 12 315 ms 318 ms 329 ms teleglobe-1.ar3.CDG2.gblx.net [64.208.27.42] 13 443 ms 449 ms 439 ms if-2-2.tcore1.PYE-Paris.as6453.net[80.231.154.18] 14 413 ms 429 ms 419 ms if-8-1600.tcore1.WYN-Marseille.as6453.net[80.231.217.5] 15 424 ms 429 ms 429 ms if-9-5.tcore1.MLV-Mumbai.as6453.net[80.231.217.18] 16 434 ms 419 ms 429 ms if-11-0-0.core1.MLV-Mumbai.as6453.net[180.87.38.22] 17 * * * Request timed out. 18 * 517 ms * TenGE-2-1-BP_CORE01.accesskenya.com[196.207.31.146] 19 * 540 ms 511 ms 196.200.26.114.accesskenya.com[196.200.26.114] Trace complete. *I think they will make so much money out of two classes of fools:* *1. those who are stupid enough to go with them at this point in time* *2. those who believe they still have no better options :)* * * [image: Inline image 1] -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ I can't hear you -- I'm using the scrambler. Please consider the environment before printing this email.
