Youtube streaming speed is better after 1AM.
Back to slow speed after 9 - 10AM.
●●~Extreme Screamyx Slowdowns V6~●●, !♥Oh we "love" streamyx!♥
●●~Extreme Screamyx Slowdowns V6~●●, !♥Oh we "love" streamyx!♥
|
|
Nov 13 2009, 08:59 PM
Return to original view | Post
#1
|
![]() ![]()
Junior Member
182 posts Joined: Jan 2007 From: Kepong |
Youtube streaming speed is better after 1AM.
Back to slow speed after 9 - 10AM. |
|
|
|
|
|
Dec 1 2009, 05:47 PM
Return to original view | Post
#2
|
![]() ![]()
Junior Member
182 posts Joined: Jan 2007 From: Kepong |
Yesterday 12:30PM, can't go online (so have to go to internet cafe for my works). Hoping TM will fixed the slow speed.
Now at 5:30PM, internet is back. Now to check whether any improvements. Streaming Youtube vids, STILL VERY SLOW!! WHAT THE HELL ARE TMNUT WORKERS DOING? Waste my 1 bloody day without internet! SCREW SCREAMYX!! Report @ Kepong |
|
|
Dec 18 2009, 04:49 PM
Return to original view | Post
#3
|
![]() ![]()
Junior Member
182 posts Joined: Jan 2007 From: Kepong |
Why suddenly int'l sites speed become so slow?
I get quite a lot of timed outs. Did DNS fakap again? |
|
|
Dec 21 2009, 04:04 PM
Return to original view | Post
#4
|
![]() ![]()
Junior Member
182 posts Joined: Jan 2007 From: Kepong |
CODE Pinging youtube-ui.l.google.com [72.14.203.139] with 32 bytes of data: Reply from 72.14.203.139: bytes=32 time=74ms TTL=54 Reply from 72.14.203.139: bytes=32 time=71ms TTL=54 Reply from 72.14.203.139: bytes=32 time=73ms TTL=54 Reply from 72.14.203.139: bytes=32 time=73ms TTL=54 Reply from 72.14.203.139: bytes=32 time=73ms TTL=54 Reply from 72.14.203.139: bytes=32 time=74ms TTL=54 Reply from 72.14.203.139: bytes=32 time=74ms TTL=54 Reply from 72.14.203.139: bytes=32 time=74ms TTL=54 Reply from 72.14.203.139: bytes=32 time=75ms TTL=54 Request timed out. Reply from 72.14.203.139: bytes=32 time=73ms TTL=54 Reply from 72.14.203.139: bytes=32 time=72ms TTL=54 Request timed out. Reply from 72.14.203.139: bytes=32 time=72ms TTL=54 Reply from 72.14.203.139: bytes=32 time=74ms TTL=54 Request timed out. Reply from 72.14.203.139: bytes=32 time=71ms TTL=54 Request timed out. Reply from 72.14.203.139: bytes=32 time=73ms TTL=54 Request timed out. Reply from 72.14.203.139: bytes=32 time=72ms TTL=54 Request timed out. Reply from 72.14.203.139: bytes=32 time=73ms TTL=54 Reply from 72.14.203.139: bytes=32 time=74ms TTL=54 Can't surf Youtube. SO SLOW! Bravo, slowmyx. Your DNS fakap again. This post has been edited by reddevils500: Dec 21 2009, 04:06 PM |
|
|
Dec 26 2009, 06:39 PM
Return to original view | Post
#5
|
![]() ![]()
Junior Member
182 posts Joined: Jan 2007 From: Kepong |
Starting December, surfing internet @ 4-5PM & 4-5AM everyday always get requested timed out.
Loading websites very SLOW or sometime stop halfway!! Both local & int'l. After 5PM, it's back to normal. TM Snailmyx routing sucks BIG TIME!! @ IP 115.135. |
|
|
Dec 27 2009, 01:34 PM
Return to original view | Post
#6
|
![]() ![]()
Junior Member
182 posts Joined: Jan 2007 From: Kepong |
Google and Youtube lag very BADLY!!
Lots of request timed out! THE HELL, TMNutz Snailmyx?! CODE Pinging youtube-ui.l.google.com [64.233.181.101] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Reply from 64.233.181.101: bytes=32 time=99ms TTL=55 Reply from 64.233.181.101: bytes=32 time=98ms TTL=55 Request timed out. Reply from 64.233.181.101: bytes=32 time=98ms TTL=55 Reply from 64.233.181.101: bytes=32 time=99ms TTL=55 Request timed out. Reply from 64.233.181.101: bytes=32 time=98ms TTL=55 Request timed out. Reply from 64.233.181.101: bytes=32 time=100ms TTL=55 Request timed out. Reply from 64.233.181.101: bytes=32 time=98ms TTL=55 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 64.233.181.101: bytes=32 time=98ms TTL=55 Reply from 64.233.181.101: bytes=32 time=98ms TTL=55 Request timed out. Reply from 64.233.181.101: bytes=32 time=100ms TTL=55 Request timed out. Reply from 64.233.181.101: bytes=32 time=110ms TTL=55 Request timed out. Reply from 64.233.181.101: bytes=32 time=98ms TTL=55 Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 64.233.181.101: Packets: Sent = 58, Received = 30, Lost = 28 (48% loss), Approximate round trip times in milli-seconds: Minimum = 97ms, Maximum = 206ms, Average = 102ms This post has been edited by reddevils500: Dec 27 2009, 01:34 PM |
|
|
|
|
|
Jan 2 2010, 04:29 AM
Return to original view | Post
#7
|
![]() ![]()
Junior Member
182 posts Joined: Jan 2007 From: Kepong |
Always get request timed outs at around 3 to 5 PM and AM since mid-Dec.
|
|
|
Jan 6 2010, 06:13 PM
Return to original view | Post
#8
|
![]() ![]()
Junior Member
182 posts Joined: Jan 2007 From: Kepong |
CODE Pinging www.l.google.com [64.233.181.99] with 32 bytes of data: Reply from 64.233.181.99: bytes=32 time=15ms TTL=55 Reply from 64.233.181.99: bytes=32 time=17ms TTL=55 Request timed out. Reply from 64.233.181.99: bytes=32 time=16ms TTL=55 Reply from 64.233.181.99: bytes=32 time=17ms TTL=55 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 64.233.181.99: bytes=32 time=14ms TTL=55 Request timed out. Reply from 64.233.181.99: bytes=32 time=15ms TTL=55 Reply from 64.233.181.99: bytes=32 time=15ms TTL=55 Reply from 64.233.181.99: bytes=32 time=16ms TTL=55 Google is so slow! DNS Fakap again? |
|
|
Jan 19 2010, 06:01 PM
Return to original view | Post
#9
|
![]() ![]()
Junior Member
182 posts Joined: Jan 2007 From: Kepong |
While driving on the way home, I saw some TM workers doing some line cable maintainence underground in Kepong to increase internet speed performance.
Expecting internet downtime at midnight. |
|
|
Mar 6 2010, 11:58 AM
Return to original view | Post
#10
|
![]() ![]()
Junior Member
182 posts Joined: Jan 2007 From: Kepong |
F***!!! Youtube suddenly slow for 2 days now!!
Is this because of Taiwan earthquake?!! |
|
Topic ClosedOptions
|
| Change to: | 0.0444sec
0.61
7 queries
GZIP Disabled
Time is now: 11th December 2025 - 02:35 PM |