DSL moving very slow?!?
#1
Posted 24 May 2005 - 11:07 PM
Hi all,
I can't help but noticing that my DSL has been running slowly these last few days. I live in the St. Augustine area, and I have been consitently getting speeds of under 200k everyday for the past few days, usually somewhere around 160k. I know this is more than we had at first, but I have gotten accustomed to the 254k, and besides, for $400 a month we should be getting more than that.
I know that the 201.*.*.* IP addresses were moving very slow a few weeks ago, and then it seemed as if they started working, but then the 200.108*.* addresses started moving slow, and I am getting altogether tired of having to disconnect and reconnect until I get a good IP address every time the internet is moving slow.
Anyway, today I have tried all three types of IP address that I know of from TSTT, the 200.108.*.*, 201.*.*.*, and 209.94.*.*, and all of them are moving at less than 200k. What is odd though is that when I did a traceroute on each IP address, the ping times were all under 300ms, unlike a few weeks ago when some were up in the thousands of ms range. Odd.
Anyway, is anyone else experiencing this?
Laterz,
Stephen.
I can't help but noticing that my DSL has been running slowly these last few days. I live in the St. Augustine area, and I have been consitently getting speeds of under 200k everyday for the past few days, usually somewhere around 160k. I know this is more than we had at first, but I have gotten accustomed to the 254k, and besides, for $400 a month we should be getting more than that.
I know that the 201.*.*.* IP addresses were moving very slow a few weeks ago, and then it seemed as if they started working, but then the 200.108*.* addresses started moving slow, and I am getting altogether tired of having to disconnect and reconnect until I get a good IP address every time the internet is moving slow.
Anyway, today I have tried all three types of IP address that I know of from TSTT, the 200.108.*.*, 201.*.*.*, and 209.94.*.*, and all of them are moving at less than 200k. What is odd though is that when I did a traceroute on each IP address, the ping times were all under 300ms, unlike a few weeks ago when some were up in the thousands of ms range. Odd.
Anyway, is anyone else experiencing this?
Laterz,
Stephen.
#3
Posted 02 June 2005 - 04:05 PM
Nightwolf, on Jun 2 2005, 11:07 AM, said:
Is DSL moving dsnger slow for anyone right now? I'm on the arouca exchange and it sucketh badly right now.
Yes, today it's a real pain. Sites are crawling up on the screen ... No DSL feeling anymore ... latency went up from 100ms to 300+ at all times on a 200.108 address. I presume TSTT switch the backbone routing to a different route.
#4
Posted 02 June 2005 - 07:03 PM
Yup, It's moving slow on both 200.108.*.* addresses, and the 201.238.*.* addresses. I'm going to try for a 209.*.*.* address now, and see how that is running.
By the way, I know it feels very slow, but when I did a bandwidth test I was actually getting 128kbps, the speed we first had on dsl and thought was so fast! Lol. It's funny how we grow used to things ;-).
Laterz,
Stephen.
By the way, I know it feels very slow, but when I did a bandwidth test I was actually getting 128kbps, the speed we first had on dsl and thought was so fast! Lol. It's funny how we grow used to things ;-).
Laterz,
Stephen.
#5
Posted 02 June 2005 - 07:12 PM
Ok, I'm getting 200k on a 209.94.*.* line. Better, but still not good enough. Ping times not bad, at 200ms. Better than they had been:
1 wohinduwolle.eggenet.de (80.66.7.225) 0.756 ms 0.686 ms 0.531 ms
2 at1-2-0-3.frankfurt-1.celox.net (217.146.128.233) 5.947 ms 5.247 ms 5.164 ms
3 ge-2-0.135.ipcolo1.Frankfurt1.Level3.net (212.162.48.105) 5.463 ms 5.264 ms 5.098 ms
4 ae-0-53.bbr1.Frankfurt1.Level3.net (195.122.136.65) 5.350 ms 5.539 ms 5.337 ms
5 ae-0-0.bbr1.Washington1.Level3.net (64.159.0.229) 93.715 ms 93.723 ms as-0-0.bbr2.Washington1.Level3.net (4.68.128.102) 93.739 ms
6 so-6-0-0.edge1.Washington1.Level3.net (209.244.11.10) 94.315 ms 94.183 ms so-7-0-0.edge1.Washington1.Level3.net (209.244.11.14) 94.245 ms
7 uunet-level3-oc48.Washington1.Level3.net (209.244.219.158) 95.371 ms 95.423 ms 95.276 ms
8 0.so-5-0-0.XL2.DCA5.ALTER.NET (152.63.43.178) 95.227 ms 95.323 ms 95.371 ms
9 0.so-2-2-0.XL2.MIA4.ALTER.NET (152.63.81.82) 123.711 ms 123.648 ms 123.730 ms
10 0.so-3-0-0.CL2.MIA4.ALTER.NET (152.63.101.45) 123.778 ms 123.793 ms 123.687 ms
11 176.ATM6-0.GW1.MIA4.ALTER.NET (152.63.83.77) 124.129 ms 124.244 ms 123.799 ms
12 TSTT-gw.customer.alter.net (157.130.90.190) 201.267 ms 205.854 ms 199.530 ms
13 tservq.tstt.net.tt (209.94.205.25) 203.596 ms 211.436 ms 192.526 ms
14 * * *
Laterz,
Stephen.
1 wohinduwolle.eggenet.de (80.66.7.225) 0.756 ms 0.686 ms 0.531 ms
2 at1-2-0-3.frankfurt-1.celox.net (217.146.128.233) 5.947 ms 5.247 ms 5.164 ms
3 ge-2-0.135.ipcolo1.Frankfurt1.Level3.net (212.162.48.105) 5.463 ms 5.264 ms 5.098 ms
4 ae-0-53.bbr1.Frankfurt1.Level3.net (195.122.136.65) 5.350 ms 5.539 ms 5.337 ms
5 ae-0-0.bbr1.Washington1.Level3.net (64.159.0.229) 93.715 ms 93.723 ms as-0-0.bbr2.Washington1.Level3.net (4.68.128.102) 93.739 ms
6 so-6-0-0.edge1.Washington1.Level3.net (209.244.11.10) 94.315 ms 94.183 ms so-7-0-0.edge1.Washington1.Level3.net (209.244.11.14) 94.245 ms
7 uunet-level3-oc48.Washington1.Level3.net (209.244.219.158) 95.371 ms 95.423 ms 95.276 ms
8 0.so-5-0-0.XL2.DCA5.ALTER.NET (152.63.43.178) 95.227 ms 95.323 ms 95.371 ms
9 0.so-2-2-0.XL2.MIA4.ALTER.NET (152.63.81.82) 123.711 ms 123.648 ms 123.730 ms
10 0.so-3-0-0.CL2.MIA4.ALTER.NET (152.63.101.45) 123.778 ms 123.793 ms 123.687 ms
11 176.ATM6-0.GW1.MIA4.ALTER.NET (152.63.83.77) 124.129 ms 124.244 ms 123.799 ms
12 TSTT-gw.customer.alter.net (157.130.90.190) 201.267 ms 205.854 ms 199.530 ms
13 tservq.tstt.net.tt (209.94.205.25) 203.596 ms 211.436 ms 192.526 ms
14 * * *
Laterz,
Stephen.
#7
Posted 06 June 2005 - 08:56 PM
Admin, did you try just changing the IP addresses. Several times now I have come home and found no internet connection, but the modem said it was connected. Once I had disconnected and reconnected enough times to get a new IP address, it then started to work, but was moving at about the same speed as the old 28k dialup modems. I kept trying, and eventually I got an IP address that was ok just over 200k).
It sounds like TSTT is really having problems. It was ridiculous when only certain IP address ranges worked properly, so you knew when you got a good one, but now there is no pattern to it at all. Today I got home and the internet was like molases (200.108.*.*), then got a 201 address, still slow, then got another 200.108. and it is up to full 260k. How do you explain that?
Arg!!!!
Laterz,
Stephen.
It sounds like TSTT is really having problems. It was ridiculous when only certain IP address ranges worked properly, so you knew when you got a good one, but now there is no pattern to it at all. Today I got home and the internet was like molases (200.108.*.*), then got a 201 address, still slow, then got another 200.108. and it is up to full 260k. How do you explain that?
Arg!!!!
Laterz,
Stephen.
#11
Posted 07 June 2005 - 11:32 PM
Yep ... today I had the same download speed of 5 KB/sec via ADSL and GPRS (cell) from my server in the US. Of course the bandwidthtest showed full speed since the problem is not between my computer and TSTT, but between TSTT and the US Internet backbone. Reminds me very much of the modem dialup times ...
Work is only possible at night ... It is highly annoying when you type something in your ssh session and you do not see what you type for 1-15 seconds. I am hoping for another, better route to the US ...
Work is only possible at night ... It is highly annoying when you type something in your ssh session and you do not see what you type for 1-15 seconds. I am hoping for another, better route to the US ...
#12
Posted 10 June 2005 - 05:29 PM
Well in terms of having a better route to the US... we will probably have to look to the stars...... "The satellites that is". The thing to really get is... for the guys that have alternative contracts with these "Satellites" to get more active, because this is currently only available in small pockets....
#15
Posted 10 August 2005 - 01:10 PM
CmacOne, on Jun 10 2005, 05:29 PM, said:
Well in terms of having a better route to the US... we will probably have to look to the stars...... "The satellites that is". The thing to really get is... for the guys that have alternative contracts with these "Satellites" to get more active, because this is currently only available in small pockets....
Dude,
Satellites = HIGH LATENCY . The only reason i chose TSTT was because they have a fiber land link to the Americas. Which is why we can play games like Battlefield 2 and World Of Warcraft. I noticed that on a good day you can get about 130ms to most Eastern US servers, however as of late you cannot get good ping times at all during the day. You have to wait till businesses and other bandwidth sucking places close down. Right now i'm rethinking my choice of TSTT on the whole because i can hardly do anything during the day with it and when you email their tech support they ask you call in and try to convince you that something is wrong with your phone line or modem.