Outline ·
[ Standard ] ·
Linear+
The "extreme Screamyx Slowdowns" V4, Edisi :Extreme International Slowdowns
|
shin gouki
|
Jun 3 2009, 10:51 PM
|
Getting Started

|
I called them just now. They said whole Sabah is having connection problem WTF. Even worse is the 2 operator hang up on me!!! BTW here is my ping.
Pinging 202.188.0.133 with 32 bytes of data:
Reply from 202.188.0.133: bytes=32 time=346ms TTL=247 Reply from 202.188.0.133: bytes=32 time=50ms TTL=247 Request timed out. Request timed out.
Ping statistics for 202.188.0.133: Packets: Sent = 4, Received = 2, Lost = 2 (50% loss), Approximate round trip times in milli-seconds: Minimum = 50ms, Maximum = 346ms, Average = 198ms
|
|
|
|
|
|
shin gouki
|
Jun 18 2009, 06:26 PM
|
Getting Started

|
High ping n timeout n random dc from Sandakan. Is it me only? What L**J*** is screamyx doing??? » Click to show Spoiler - click again to hide... « Reply from 202.188.0.133: bytes=32 time=660ms TTL=247 Reply from 202.188.0.133: bytes=32 time=656ms TTL=247 Reply from 202.188.0.133: bytes=32 time=688ms TTL=247 Reply from 202.188.0.133: bytes=32 time=686ms TTL=247 Reply from 202.188.0.133: bytes=32 time=673ms TTL=247 Reply from 202.188.0.133: bytes=32 time=668ms TTL=247 Reply from 202.188.0.133: bytes=32 time=701ms TTL=247 Reply from 202.188.0.133: bytes=32 time=679ms TTL=247 Request timed out. Request timed out. Reply from 202.188.0.133: bytes=32 time=664ms TTL=247 Reply from 202.188.0.133: bytes=32 time=739ms TTL=247 Reply from 202.188.0.133: bytes=32 time=683ms TTL=247 Reply from 202.188.0.133: bytes=32 time=669ms TTL=247 Reply from 202.188.0.133: bytes=32 time=677ms TTL=247 Reply from 202.188.0.133: bytes=32 time=668ms TTL=247 Reply from 202.188.0.133: bytes=32 time=669ms TTL=247 Reply from 202.188.0.133: bytes=32 time=675ms TTL=247 Reply from 202.188.0.133: bytes=32 time=670ms TTL=247 Reply from 202.188.0.133: bytes=32 time=672ms TTL=247 Reply from 202.188.0.133: bytes=32 time=663ms TTL=247 Request timed out. Request timed out. Reply from 202.188.0.133: bytes=32 time=661ms TTL=247 Reply from 202.188.0.133: bytes=32 time=680ms TTL=247 Reply from 202.188.0.133: bytes=32 time=678ms TTL=247 Reply from 202.188.0.133: bytes=32 time=690ms TTL=247 Reply from 202.188.0.133: bytes=32 time=653ms TTL=247 Reply from 202.188.0.133: bytes=32 time=674ms TTL=247 Reply from 202.188.0.133: bytes=32 time=736ms TTL=247 Request timed out. Reply from 202.188.0.133: bytes=32 time=708ms TTL=247 Reply from 202.188.0.133: bytes=32 time=738ms TTL=247 Request timed out. Reply from 202.188.0.133: bytes=32 time=672ms TTL=247 Reply from 202.188.0.133: bytes=32 time=687ms TTL=247 Reply from 202.188.0.133: bytes=32 time=649ms TTL=247 Reply from 202.188.0.133: bytes=32 time=681ms TTL=247 Reply from 202.188.0.133: bytes=32 time=670ms TTL=247 Reply from 202.188.0.133: bytes=32 time=666ms TTL=247 Request timed out. Reply from 202.188.0.133: bytes=32 time=676ms TTL=247 Reply from 202.188.0.133: bytes=32 time=655ms TTL=247 Reply from 202.188.0.133: bytes=32 time=667ms TTL=247 Request timed out.
This post has been edited by shin gouki: Jun 18 2009, 06:31 PM
|
|
|
|
|
|
shin gouki
|
Jun 18 2009, 06:36 PM
|
Getting Started

|
Mile 6
|
|
|
|
|
|
shin gouki
|
Jun 18 2009, 08:53 PM
|
Getting Started

|
Correction Tmnut screamyx is NO effort or WORST effort not BEST effort I wonder why their company won't bankrupt since many users are cursing them everyday.........
This post has been edited by shin gouki: Jun 18 2009, 09:05 PM
|
|
|
|
|
|
shin gouki
|
Jun 19 2009, 02:32 AM
|
Getting Started

|
It take ages to load a SINGLE pic WTF
|
|
|
|
|
|
shin gouki
|
Jun 24 2009, 06:32 PM
|
Getting Started

|
QUOTE(fabianz03 @ Jun 24 2009, 12:10 PM) Driving~~ Cabinet? I don't know coz that 'box' got written 'HUAWEI' on top. You should scream at them abt the slow speed This post has been edited by shin gouki: Jun 24 2009, 06:34 PM
|
|
|
|
|
|
shin gouki
|
Jun 25 2009, 08:59 PM
|
Getting Started

|
good job tmnut » Click to show Spoiler - click again to hide... « Reply from 202.188.0.133: bytes=32 time=674ms TTL=247 Reply from 202.188.0.133: bytes=32 time=681ms TTL=247 Reply from 202.188.0.133: bytes=32 time=835ms TTL=247 Reply from 202.188.0.133: bytes=32 time=925ms TTL=247 Reply from 202.188.0.133: bytes=32 time=993ms TTL=247 Reply from 202.188.0.133: bytes=32 time=1006ms TTL=247 Reply from 202.188.0.133: bytes=32 time=956ms TTL=247 Reply from 202.188.0.133: bytes=32 time=991ms TTL=247 Reply from 202.188.0.133: bytes=32 time=1009ms TTL=247 Reply from 202.188.0.133: bytes=32 time=990ms TTL=247 Reply from 202.188.0.133: bytes=32 time=956ms TTL=247 Reply from 202.188.0.133: bytes=32 time=944ms TTL=247 Reply from 202.188.0.133: bytes=32 time=936ms TTL=247 Reply from 202.188.0.133: bytes=32 time=906ms TTL=247 Reply from 202.188.0.133: bytes=32 time=796ms TTL=247 Reply from 202.188.0.133: bytes=32 time=777ms TTL=247 Reply from 202.188.0.133: bytes=32 time=692ms TTL=247 Reply from 202.188.0.133: bytes=32 time=711ms TTL=247 Reply from 202.188.0.133: bytes=32 time=724ms TTL=247 Reply from 202.188.0.133: bytes=32 time=707ms TTL=247 Reply from 202.188.0.133: bytes=32 time=642ms TTL=247
|
|
|
|
|
|
shin gouki
|
Jul 3 2009, 06:52 PM
|
Getting Started

|
screamyx become slow when i added new torrent >< WTF is this!!! sandakan area 124.82.xx.xxx » Click to show Spoiler - click again to hide... « Reply from 202.188.0.133: bytes=32 time=124ms TTL=247 Reply from 202.188.0.133: bytes=32 time=155ms TTL=247 Reply from 202.188.0.133: bytes=32 time=149ms TTL=247 Request timed out. Reply from 202.188.0.133: bytes=32 time=288ms TTL=247 Reply from 202.188.0.133: bytes=32 time=221ms TTL=247 Request timed out. Reply from 202.188.0.133: bytes=32 time=59ms TTL=247 Reply from 202.188.0.133: bytes=32 time=54ms TTL=247 Request timed out. Reply from 202.188.0.133: bytes=32 time=57ms TTL=247 Reply from 202.188.0.133: bytes=32 time=55ms TTL=247 Reply from 202.188.0.133: bytes=32 time=81ms TTL=247 Reply from 202.188.0.133: bytes=32 time=58ms TTL=247 Reply from 202.188.0.133: bytes=32 time=62ms TTL=247 Reply from 202.188.0.133: bytes=32 time=61ms TTL=247 Request timed out. Reply from 202.188.0.133: bytes=32 time=86ms TTL=247 Reply from 202.188.0.133: bytes=32 time=108ms TTL=247 Request timed out. Reply from 202.188.0.133: bytes=32 time=58ms TTL=247 Request timed out. Reply from 202.188.0.133: bytes=32 time=64ms TTL=247 Reply from 202.188.0.133: bytes=32 time=58ms TTL=247
|
|
|
|
|
|
shin gouki
|
Jul 3 2009, 06:54 PM
|
Getting Started

|
arghh double post dam screamyx
This post has been edited by shin gouki: Jul 3 2009, 06:59 PM
|
|
|
|
|
|
shin gouki
|
Jul 5 2009, 07:28 PM
|
Getting Started

|
Anyone can tell me why I always get request timeout? Izzit cable problem? Or izzit screamyx problem? I'm having this problem for months!!! » Click to show Spoiler - click again to hide... « Request timed out. Reply from 202.188.0.133: bytes=32 time=56ms TTL=247 Request timed out. Request timed out. Reply from 202.188.0.133: bytes=32 time=58ms TTL=247 Request timed out. Request timed out. Reply from 202.188.0.133: bytes=32 time=112ms TTL=247 Reply from 202.188.0.133: bytes=32 time=114ms TTL=247 Request timed out. Reply from 202.188.0.133: bytes=32 time=78ms TTL=247 Reply from 202.188.0.133: bytes=32 time=83ms TTL=247 Request timed out. Reply from 202.188.0.133: bytes=32 time=75ms TTL=247 Request timed out. Reply from 202.188.0.133: bytes=32 time=113ms TTL=247 Reply from 202.188.0.133: bytes=32 time=75ms TTL=247 Request timed out. Reply from 202.188.0.133: bytes=32 time=80ms TTL=247 Reply from 202.188.0.133: bytes=32 time=78ms TTL=247 Reply from 202.188.0.133: bytes=32 time=86ms TTL=247 Request timed out. Request timed out. Reply from 202.188.0.133: bytes=32 time=72ms TTL=247
|
|
|
|
|
|
shin gouki
|
Jul 5 2009, 10:16 PM
|
Getting Started

|
QUOTE(miahahaha @ Jul 5 2009, 08:15 PM) Did you complaint to TM?? Call them, ask the tech guy to come to your place & check...tried restarting modem?? If yes, then maybe there are problem with the port or your line... I called them just now and ask them to change a new port for me. But dunno those monkey will do it or not?
|
|
|
|
|
|
shin gouki
|
Jul 15 2009, 12:01 AM
|
Getting Started

|
QUOTE(chunjiet @ Jul 14 2009, 10:07 PM) i called at least 30 times, email wrote more than 8. report number more than 9......... that unstable connection make me hard to confirm it has problem less, just like yesterday that technician came my place again.... but that time my line is imba fantastic... ping tm.net.my only 11ms.... no matter wht i telling also no prove to support..... he just leave an email address and ask me send the screen shot when it high ping.... but then, email was sent, call also made(to technician), but he remarks to my report as " user side problem "................ WTF-----------> Shitmyx your case is same like me >_< but i added timeout sumore they just don wan to admit is their problem!!! This post has been edited by shin gouki: Jul 15 2009, 12:09 AM
|
|
|
|
|
|
shin gouki
|
Jul 15 2009, 08:42 PM
|
Getting Started

|
Better to nuke TM building then we can have a new ISP
|
|
|
|
|