QUOTE(cherasbabe @ Aug 4 2007, 12:35 AM)
can do a traceroute to www.tm.net.my & flying spaghetti monster.org? (

, mod can i put the blue address here? )
let's see if we can dota on it..
your flyingspaghettimonster.org cannot ping....
» Click to show Spoiler - click again to hide... «
CODE
Pinging flyingspaghettimonster.org [205.178.189.131] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 205.178.189.131:
Packets: Sent = 6, Received = 0, Lost = 6 (100% loss),
Here's it's traceroute...
» Click to show Spoiler - click again to hide... «
CODE
Tracing route to flyingspaghettimonster.org [205.178.189.131]
over a maximum of 30 hops:
1 172 ms 45 ms 39 ms 116.206.1.1
2 58 ms 44 ms 44 ms 116.206.0.98
3 161 ms 84 ms 54 ms 116.206.0.26
4 63 ms 50 ms 49 ms 116.206.0.1
5 52 ms 45 ms 43 ms 202.76.239.1
6 57 ms 42 ms * 202.76.224.46
7 53 ms 46 ms 45 ms 202.76.224.2
8 62 ms 49 ms 55 ms 202.76.230.14
9 74 ms 53 ms 62 ms 203.208.143.141
10 68 ms 49 ms 55 ms 203.208.182.5
11 * 69 ms 55 ms 203.208.183.57
12 273 ms 374 ms * 203.208.172.189
13 268 ms 249 ms 254 ms 203.208.149.26
14 322 ms 374 ms 527 ms 206.111.12.45
15 369 ms 320 ms 244 ms 203.208.149.26
16 375 ms 264 ms 1030 ms 206.111.12.45
17 357 ms 284 ms 489 ms 65.106.3.250
18 376 ms * 397 ms 65.106.0.37
19 1192 ms 390 ms * 65.106.3.250
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * *
traceroute to tm.net.my:
» Click to show Spoiler - click again to hide... «
CODE
C:\> tracert -d www.tm.net.my
Tracing route to www.3dns.tm.net.my [202.71.97.48]
over a maximum of 30 hops:
1 47 ms 44 ms 44 ms 116.206.1.1
2 68 ms 44 ms 44 ms 116.206.0.98
3 89 ms 61 ms 65 ms 116.206.0.27
4 66 ms 44 ms 44 ms 116.206.0.1
5 53 ms 44 ms 44 ms 202.76.239.1
6 58 ms 44 ms 44 ms 202.76.224.62
7 200 ms 48 ms * 202.76.224.19
8 53 ms 44 ms 44 ms 218.100.22.41
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
QUOTE(schrodinger_cat @ Aug 5 2007, 08:27 AM)
Can anyone draw a conclusion about this service? Is it better than streamyx? or is too soon to tell? Thanks for help!
Better than Streamyx.... not really. If you're outdoors a lot, or live in a fairly open area that's within 1km from any of their base stations, you'll have better luck using their service.
--
Over the weekend and this morning, I checked out their coverage in Sunway at a couple of places -- at an apartment (friend's place) and Sunway Hospital.
At the apartment, signal was strong and stable indoors at 90% since there are a lot of windows. No complaints there.
At Sunway Hospital which isn't too far away (within 1km from the first location), the signal was not stable. I was located fairly indoors (on purpose) so signal fluctuated between 0% and 90%. It was still usable, though on many occasions, coverage went down to 0%. Sometimes, signal was 40%, sometimes 70-80% and maxed out at ~92%. Bear in mind, though, that they have a base station in Bandar Sunway, and I'd have assumed that the site is very nearby.
Although these two test locations are located <1km apart, they are served by two different base stations!! Here's the proof:
Traceroute to google.com at Sunway apartment (note the first hop):
» Click to show Spoiler - click again to hide... «
CODE
Tracing route to google.com [64.233.187.99]
over a maximum of 30 hops:
1 73 ms 48 ms 44 ms 116.206.1.1
2 61 ms 45 ms 44 ms 116.206.0.98
3 57 ms 39 ms 40 ms 116.206.0.26
4 57 ms 43 ms 44 ms 116.206.0.1
5 81 ms * 264 ms 202.76.239.1
6 230 ms 1118 ms 85 ms 202.76.224.62
7 62 ms 44 ms * 202.76.224.17
8 63 ms 49 ms 49 ms 216.6.121.45
9 122 ms 105 ms 244 ms 216.6.95.21
10 170 ms 159 ms 154 ms 209.58.61.1
11 271 ms 259 ms 395 ms 216.6.29.17
12 274 ms * 272 ms 216.6.29.50
13 267 ms 244 ms 255 ms 207.45.202.38
14 * 510 ms 264 ms 216.6.50.6
15 1033 ms 374 ms 258 ms 209.85.130.4
16 327 ms 328 ms 759 ms 72.14.239.15
17 324 ms 879 ms 318 ms 66.249.95.212
18 526 ms 664 ms 323 ms 72.14.236.19
19 434 ms 322 ms 1327 ms 216.239.49.222
20 324 ms 432 ms 319 ms 64.233.187.99
Trace complete.
Traceroute to MetroFON at Sunway Hospital (again, note the first hop):
» Click to show Spoiler - click again to hide... «
CODE
Tracing route to 202.73.10.4 over a maximum of 30 hops
1 209 ms 113 ms 99 ms 116.206.1.3
2 107 ms 65 ms 104 ms 116.206.0.98
3 92 ms 65 ms 64 ms 116.206.0.26
4 117 ms 70 ms 94 ms 116.206.0.1
5 287 ms 140 ms 92 ms 202.76.239.1 <---- AIMS
6 82 ms 64 ms 74 ms 202.76.224.46
7 104 ms 87 ms 79 ms 202.76.224.3
8 112 ms 115 ms 102 ms 203.115.248.81 <---- NTT
9 111 ms 124 ms 114 ms 203.115.224.53
10 181 ms 155 ms 119 ms 203.115.225.3
11 167 ms 140 ms 194 ms 203.115.224.62
12 122 ms 89 ms * 218.189.12.46 <---- HGC (Hutchison)
13 145 ms 99 ms * 202.73.8.130 <---- MetroFON
14 132 ms 116 ms 153 ms 202.73.10.4
Trace complete.
So now, I'm begging to ask this question: Where are base stations 116.206.1.1 and 116.206.1.3 located?? I find it hard to believe that Sunway is being served by two base stations, when their coverage map only indicates one base station for this area. Is 116.206.1.1, by any chance... Kelana Jaya?
Here's the ping test to next hop (connected from Sunway Hospital):
» Click to show Spoiler - click again to hide... «
CODE
C:\> ping -n 20 116.206.1.3
Pinging 116.206.1.3 with 32 bytes of data:
Reply from 116.206.1.3: bytes=32 time=110ms TTL=255
Reply from 116.206.1.3: bytes=32 time=78ms TTL=255
Reply from 116.206.1.3: bytes=32 time=70ms TTL=255
Reply from 116.206.1.3: bytes=32 time=97ms TTL=255
Reply from 116.206.1.3: bytes=32 time=105ms TTL=255
Reply from 116.206.1.3: bytes=32 time=83ms TTL=255
Reply from 116.206.1.3: bytes=32 time=78ms TTL=255
Reply from 116.206.1.3: bytes=32 time=115ms TTL=255
Reply from 116.206.1.3: bytes=32 time=67ms TTL=255
Reply from 116.206.1.3: bytes=32 time=125ms TTL=255
Reply from 116.206.1.3: bytes=32 time=87ms TTL=255
Reply from 116.206.1.3: bytes=32 time=99ms TTL=255
Reply from 116.206.1.3: bytes=32 time=71ms TTL=255
Reply from 116.206.1.3: bytes=32 time=68ms TTL=255
Reply from 116.206.1.3: bytes=32 time=66ms TTL=255
Reply from 116.206.1.3: bytes=32 time=88ms TTL=255
Reply from 116.206.1.3: bytes=32 time=68ms TTL=255
Reply from 116.206.1.3: bytes=32 time=116ms TTL=255
Reply from 116.206.1.3: bytes=32 time=64ms TTL=255
Reply from 116.206.1.3: bytes=32 time=68ms TTL=255
Ping statistics for 116.206.1.3:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 125ms, Average = 86ms
Speedtest at Sunway apartment:
» Click to show Spoiler - click again to hide... «
Speedtest at Sunway Hospital (note that uplink may not be accurate because the coverage went from "Good" to Zilch towards the end of the speedtest):
» Click to show Spoiler - click again to hide... «
So overall, looks like my bandwidth tests have never exceeded ~250kbps (DL) in all my three test locations. Note that all my speedtests are rated against the MetroFON server in KL. Further analysis may need to be done, to verify whether the bottleneck is due to distance from base station or due to their uplink Internet gateway provider (i.e., AIMS). MetroFON does not peer with AIMS.
Final note: I don't think I'll be doing further testing on iBurst after today since I'm returning the card to its rightful owner. Hope this is helpful to those who are curious/interested in their service.