Super slow Streamyx today

Lowyat.NET forums

Lowyat.NET Kopitiam Garage Sales

Lowyat.NET Rules and Regulations FAQ Help Search Members

Welcome Guest ( Log In | Register )

Lowyat.NET -> Networks and Broadband

Bump Topic Topic Closed RSS Feed

Outline · [ Standard ] · Linear+

Streamyx Super slow Streamyx today

views

basSist	Jun 17 2008, 08:58 PM Return to original view \| Post #1
Don't look at my stars Senior Member 3,567 posts Joined: Jan 2003 From: Paradise	have problem connecting to HK site. slow. With speedtest.net <250Kbps with 512package. IP: 60.54, 118.100 Anyone facing this problem?
Card PM	Report Top Like Quote Reply

basSist	Jun 19 2008, 12:18 PM Return to original view \| Post #2
Don't look at my stars Senior Member 3,567 posts Joined: Jan 2003 From: Paradise	i cant access international sites at all too. before that d/c at all... with 118.100 ip This post has been edited by basSist: Jun 19 2008, 12:18 PM
Card PM	Report Top Like Quote Reply

basSist	Jun 19 2008, 01:06 PM Return to original view \| Post #3
Don't look at my stars Senior Member 3,567 posts Joined: Jan 2003 From: Paradise	I'm in Johor, Kluang as well. having the same problem.. msn cant connect due to keyports problem, international sites down, lowyatnet laggy... ip: 124.13, 118.100
Card PM	Report Top Like Quote Reply

basSist	Jun 19 2008, 05:27 PM Return to original view \| Post #4
Don't look at my stars Senior Member 3,567 posts Joined: Jan 2003 From: Paradise	QUOTE(WildChai @ Jun 19 2008, 05:18 PM) I am seriously stunned! I am downloading via torrent at 400 kB/s! Freaking sweet! Btw...i am NOT in malaysia....am in islamabad now. Haha. In a country like this i am getting these kind of speeds. Shame on BolehLand! idxxt, we are discussing the Streamyx and u were going off topic. still cant access international sites.. lowyatnet lagging. yahoo msger can on , msn msger cannot. ip: 118.100 now Connection Status Connected Us Rate (Kbps) 512 Ds Rate (Kbps) 2048 US Margin 26 DS Margin 30 Trained Modulation ADSL_G.dmt LOS Errors 0 DS Line Attenuation 2 US Line Attenuation 2 Peak Cell Rate 1207 cells per sec CRC Rx Fast 0 CRC Tx Fast 0 CRC Rx Interleaved 0 CRC Tx Interleaved 2 Path Mode Interleaved DSL Statistics Near End F4 Loop Back Count 0 Near End F5 Loop Back Count 0
Card PM	Report Top Like Quote Reply

basSist	Jul 1 2008, 10:22 PM Return to original view \| Post #5
Don't look at my stars Senior Member 3,567 posts Joined: Jan 2003 From: Paradise	Tracing route to www.l.google.com [64.233.189.99] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms login.router [192.168.1.1] 2 12 ms 11 ms 10 ms 219.93.218.177 3 * * * Request timed out. 4 * * * Request timed out. 5 * * * Request timed out. 6 * * * Request timed out. 7 * * * Request timed out. 8 * * * Request timed out. 9 * * .... =.="
Card PM	Report Top Like Quote Reply

basSist	Jul 2 2008, 02:31 PM Return to original view \| Post #6
Don't look at my stars Senior Member 3,567 posts Joined: Jan 2003 From: Paradise	yeap slow again.. before 2pm i got 70-80ms ping to google.. now 180-190ms
Card PM	Report Top Like Quote Reply

basSist	Jul 2 2008, 04:52 PM Return to original view \| Post #7
Don't look at my stars Senior Member 3,567 posts Joined: Jan 2003 From: Paradise	i did the same thing.. but then it is fluctuating .. Pinging google. ip 118.100. location kluang johor » Click to show Spoiler - click again to hide... « Reply from 72.14.235.104: bytes=32 time=88ms TTL=240 Reply from 72.14.235.104: bytes=32 time=87ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=89ms TTL=240 Reply from 72.14.235.104: bytes=32 time=87ms TTL=240 Reply from 72.14.235.104: bytes=32 time=81ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=87ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=84ms TTL=240 Reply from 72.14.235.104: bytes=32 time=87ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=88ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=88ms TTL=240 Request timed out. Reply from 72.14.235.104: bytes=32 time=363ms TTL=240 Request timed out. Reply from 72.14.235.104: bytes=32 time=460ms TTL=240 Reply from 72.14.235.104: bytes=32 time=460ms TTL=240 Request timed out. Reply from 72.14.235.104: bytes=32 time=475ms TTL=240 Reply from 72.14.235.104: bytes=32 time=484ms TTL=240 Request timed out. Reply from 72.14.235.104: bytes=32 time=493ms TTL=240 Reply from 72.14.235.104: bytes=32 time=502ms TTL=240 Reply from 72.14.235.104: bytes=32 time=497ms TTL=240 Reply from 72.14.235.104: bytes=32 time=505ms TTL=240 Request timed out. Request timed out. Request timed out. Request timed out. Reply from 72.14.235.104: bytes=32 time=498ms TTL=240 Request timed out. Reply from 72.14.235.104: bytes=32 time=499ms TTL=240 Request timed out. Reply from 72.14.235.104: bytes=32 time=506ms TTL=240 Reply from 72.14.235.104: bytes=32 time=502ms TTL=240 Reply from 72.14.235.104: bytes=32 time=496ms TTL=240 Request timed out. Reply from 72.14.235.104: bytes=32 time=497ms TTL=240 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 72.14.235.104: bytes=32 time=191ms TTL=240 Request timed out. Request timed out. Reply from 72.14.235.104: bytes=32 time=311ms TTL=240 Reply from 72.14.235.104: bytes=32 time=317ms TTL=240 Request timed out. Request timed out. Reply from 72.14.235.104: bytes=32 time=367ms TTL=240 Reply from 72.14.235.104: bytes=32 time=365ms TTL=240 Request timed out. Reply from 72.14.235.104: bytes=32 time=380ms TTL=240 Request timed out. Reply from 72.14.235.104: bytes=32 time=396ms TTL=240 Request timed out. Reply from 72.14.235.104: bytes=32 time=416ms TTL=240 Reply from 72.14.235.104: bytes=32 time=414ms TTL=240 Request timed out. Request timed out. Request timed out. Reply from 72.14.235.104: bytes=32 time=220ms TTL=240 Reply from 72.14.235.104: bytes=32 time=87ms TTL=240 Reply from 72.14.235.104: bytes=32 time=87ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=87ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=85ms TTL=240 Reply from 72.14.235.104: bytes=32 time=87ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=87ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=91ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=87ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=87ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=87ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=87ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=87ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=87ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=85ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=87ms TTL=240 Reply from 72.14.235.104: bytes=32 time=108ms TTL=240 Reply from 72.14.235.104: bytes=32 time=88ms TTL=240 Reply from 72.14.235.104: bytes=32 time=87ms TTL=240 Reply from 72.14.235.104: bytes=32 time=85ms TTL=240 Reply from 72.14.235.104: bytes=32 time=86ms TTL=240 Reply from 72.14.235.104: bytes=32 time=85ms TTL=240 Reply from 72.14.235.104: bytes=32 time=87ms TTL=240 Reply from 72.14.235.104: bytes=32 time=87ms TTL=240 Reply from 72.14.235.104: bytes=32 time=87ms TTL=240 This post has been edited by basSist: Jul 2 2008, 04:54 PM
Card PM	Report Top Like Quote Reply

basSist	Jul 2 2008, 04:55 PM Return to original view \| Post #8
Don't look at my stars Senior Member 3,567 posts Joined: Jan 2003 From: Paradise	QUOTE(Xtryfe @ Jul 2 2008, 04:53 PM) Did one of the TMnut people see i was having good connection and bam made it slow again. Alright it's slow again guys damn . Everything was loading instantly and now suddenly back to hell mode. I swear their sitting behind computer console giggling like little children going haha ini rumah mari kasi problem sama dia. Tekan butang sekarang connection ok sekarang tekan lagi hahah bodoh sekarang tak boleh main internet hehe kita banyak boringleh. it fluctuates. refer to my previous post.. i think same case goes to u
Card PM	Report Top Like Quote Reply

« Next Oldest · Networks and Broadband · Next Newest »

Topic ClosedOptions

Change to:

0.0567sec

0.61

7 queries

GZIP Disabled
Time is now: 6th December 2025 - 01:56 PM

All Rights Reserved © 2002- 2025 Vijandren Ramadass (~unite against racism~)

Removal Request

Powered by Invision Power Board © 2025 IPS, Inc.