|
Forum Home | Broadbandinfo.com | Broadband Speed Test | Site Map |
|
|||||||
![]() |
|
|
Thread Tools | Display Modes |
|
#1 ()
|
|||
|
|||
|
I've run tests and download/upload speeds are perfectly fine, but I get very erratic ping from 30-150 and when I ping yahoo.com I get 100+ ms.
|
|
#2 ()
|
|||
|
|||
|
your ping is actually good because 100ms is like 0.1 second (is my conversion correct?)
![]() |
|
#3 ()
|
|||
|
|||
|
I have been suffering the same. Extremely high ping on yahoo/att DSL
since the 1st of the month. Im in Kalamazoo Michigan. Pings to my own city are high. And if I try to ping Kansas City, MO its worse than any dial up connections ive had 15+ years ago. There is something cut somewhere and ATT or whoever Owns the lines needs to fix it. Something is wrong in Kansas City, Missouri, and SpringField, MO. My ping over to Prince Rupert, CANADA!! is way better than pinging places in my own state. Now that is screwed up! Here is a log. The times are off. Because of GMT. but from 11:00am-Eastern to sometime after 1:00am-Eastern. my pings are so high, playing online games is impossible. I have noticed this same pattern to the T, since July 10, 2008. 2nd Tech comming out today. Oh I must mention the fact that getting AT&T to send a tech out for "HIGH PINGS" is nearly impossible. I basically have to tell the idiots on the other end that I dont have internet. Otherwise they say everything is fine just because they can see my modem is online. Mind you 5pm my downlaod speeds are 1.5mb most of the time. I'm paying for 5mb service. TEST_DATE,IP_ADDRESS,DOWNLOAD_SPEED,UPLOAD_SPEED,L ATENCY,SERVER_NAME,DISTANCE "7/28/2008 10:30 PM GMT","69.208.92.225","5090 kb/s","610 kb/s","164 ms","Radnor, OH","~ 200 mi" "7/28/2008 10:45 PM GMT","69.208.92.225","5152 kb/s","616 kb/s","144 ms","Stanton, MI","~ 50 mi" "7/28/2008 10:46 PM GMT","69.208.92.225","3529 kb/s","606 kb/s","185 ms","San Jose, CA","~ 1950 mi" "7/28/2008 10:46 PM GMT","69.208.92.225","5152 kb/s","612 kb/s","139 ms","Radnor, OH","~ 200 mi" "7/28/2008 10:47 PM GMT","69.208.92.225","2033 kb/s","499 kb/s","395 ms","Kansas City, MO","~ 550 mi" "7/28/2008 10:47 PM GMT","69.208.92.225","3325 kb/s","472 kb/s","479 ms","Owensboro, KY","~ 350 mi" "7/28/2008 10:48 PM GMT","69.208.92.225","1050 kb/s","613 kb/s","181 ms","Chicago, IL","~ 150 mi" "7/28/2008 10:49 PM GMT","69.208.92.225","4912 kb/s","614 kb/s","200 ms","Radnor, OH","~ 200 mi" "7/28/2008 10:50 PM GMT","69.208.92.225","3220 kb/s","430 kb/s","460 ms","Owensboro, KY","~ 350 mi" "7/28/2008 10:50 PM GMT","69.208.92.225","3835 kb/s","589 kb/s","223 ms","Tallahassee, FL","~ 850 mi" "7/28/2008 10:51 PM GMT","69.208.92.225","4851 kb/s","617 kb/s","170 ms","Iron Mountain, MI","~ 250 mi" "7/28/2008 10:52 PM GMT","69.208.92.225","5136 kb/s","616 kb/s","174 ms","Twin Cities, MN","~ 400 mi" "7/28/2008 10:53 PM GMT","69.208.92.225","1424 kb/s","562 kb/s","227 ms","Calgary","~ 1450 mi" "7/28/2008 10:54 PM GMT","69.208.92.225","5154 kb/s","620 kb/s","134 ms","Springfield, MO","~ 550 mi" "7/28/2008 10:55 PM GMT","69.208.92.225","4329 kb/s","461 kb/s","464 ms","Kansas City, MO","~ 550 mi" "7/28/2008 10:56 PM GMT","69.208.92.225","4906 kb/s","600 kb/s","206 ms","Norfolk, NE","~ 600 mi" "7/28/2008 10:56 PM GMT","69.208.92.225","5153 kb/s","620 kb/s","185 ms","Germantown, WI","~ 150 mi" "7/28/2008 10:57 PM GMT","69.208.92.225","5063 kb/s","617 kb/s","136 ms","Chicago, IL","~ 150 mi" "7/28/2008 10:58 PM GMT","69.208.92.225","5165 kb/s","549 kb/s","312 ms","Houston, TX","~ 1050 mi" "7/28/2008 10:59 PM GMT","69.208.92.225","5150 kb/s","617 kb/s","166 ms","Twin Cities, MN","~ 400 mi" "7/28/2008 11:00 PM GMT","69.208.92.225","5056 kb/s","527 kb/s","337 ms","Kansas City, MO","~ 550 mi" "7/28/2008 11:00 PM GMT","69.208.92.225","5148 kb/s","622 kb/s","183 ms","Springfield, MO","~ 550 mi" "7/28/2008 11:01 PM GMT","69.208.92.225","2149 kb/s","601 kb/s","173 ms","Fort Worth, TX","~ 1000 mi" "7/28/2008 11:02 PM GMT","69.208.92.225","5054 kb/s","538 kb/s","349 ms","Kansas City, MO","~ 550 mi" "7/28/2008 11:04 PM GMT","69.208.92.225","2809 kb/s","494 kb/s","190 ms","Colorado Springs","~ 1050 mi" "7/29/2008 12:51 AM GMT","69.208.92.225","3400 kb/s","302 kb/s","601 ms","Kansas City, MO","~ 550 mi" "7/29/2008 12:53 AM GMT","69.208.92.225","3746 kb/s","586 kb/s","264 ms","Stanton, MI","~ 50 mi" "7/29/2008 12:55 AM GMT","69.208.92.225","3881 kb/s","568 kb/s","260 ms","Chicago, IL","~ 150 mi" "7/29/2008 12:56 AM GMT","69.208.92.225","4262 kb/s","599 kb/s","237 ms","Springfield, MO","~ 550 mi" "7/29/2008 12:57 AM GMT","69.208.92.225","3306 kb/s","288 kb/s","673 ms","Kansas City, MO","~ 550 mi" "7/29/2008 12:58 AM GMT","69.208.92.225","3328 kb/s","504 kb/s","310 ms","Germantown, WI","~ 150 mi" "7/29/2008 12:58 AM GMT","69.208.92.225","3333 kb/s","545 kb/s","315 ms","Kalamazoo, MI","~ 50 mi" "7/29/2008 12:59 AM GMT","69.208.92.225","3761 kb/s","602 kb/s","237 ms","Stanton, MI","~ 50 mi" "7/29/2008 1:00 AM GMT","69.208.92.225","4751 kb/s","607 kb/s","190 ms","Fenton, MI","~ 100 mi" "7/29/2008 1:02 AM GMT","69.208.92.225","2426 kb/s","476 kb/s","353 ms","Portland, OR","~ 1850 mi" "7/29/2008 1:02 AM GMT","69.208.92.225","2816 kb/s","540 kb/s","292 ms","New York, NY","~ 600 mi" "7/29/2008 12:55 PM GMT","69.208.92.225","5069 kb/s","618 kb/s","79 ms","Kansas City, MO","~ 550 mi" "7/29/2008 12:56 PM GMT","69.208.92.225","5150 kb/s","643 kb/s","19 ms","Chicago, IL","~ 150 mi" "7/29/2008 2:11 PM GMT","69.208.92.225","5072 kb/s","621 kb/s","79 ms","Kansas City, MO","~ 550 mi" "7/29/2008 3:31 PM GMT","69.208.92.225","5082 kb/s","618 kb/s","87 ms","Kansas City, MO","~ 550 mi" "7/29/2008 3:33 PM GMT","69.208.92.225","4863 kb/s","623 kb/s","107 ms","Prince Rupert","~ 2150 mi" "7/29/2008 4:09 PM GMT","69.208.92.225","5143 kb/s","641 kb/s","23 ms","Chicago, IL","~ 150 mi" "7/29/2008 5:03 PM GMT","69.208.92.225","5061 kb/s","544 kb/s","293 ms","Kansas City, MO","~ 550 mi" "7/29/2008 5:03 PM GMT","69.208.92.225","5150 kb/s","618 kb/s","156 ms","Stanton, MI","~ 50 mi" "7/29/2008 6:40 PM GMT","69.208.92.225","4198 kb/s","597 kb/s","228 ms","Kalamazoo, MI","~ 50 mi" "7/29/2008 6:41 PM GMT","69.208.92.225","4292 kb/s","436 kb/s","454 ms","Kansas City, MO","~ 550 mi" "7/29/2008 6:49 PM ______________________ As you can see, VERY unstable. I have tried 4 different PC's on this DSL line. All had the same problem. I used the neighbors Comcast open wireless to test some things. pings are much better but there is still something wrong in Missouri. Maybe the Floods messed something up? I preyed the day wouldnt have to come up to me going back to comcrap cable. Overpriced piece of crap too. but better than what im getting now. Since March of 08. This DSL line was FLAWLESS. I was so happy to have a descent ISP after dealing with Comcast for a year. They had a bad line out here and couldnt dig it up till april 14'th due to the Frost laws here. With 30%+ packet loss with Comcast I had to do something about it. Now im dealing with a whole new issue with yet another ISP. |
|
#4 ()
|
|||
|
|||
|
Quote:
I'm not sure about the conversion table. but on a 5mb line your ping should be less than 100ms anywhere in this country. My DSL was flawlessly running 15ms to 40ms pings all over the world. Untill now. In order to play First Person Shooters of any type. You need to have Sub 100mb ping times. Anything over 100 you see noticeable lag. Yes I know 15 years ago we had 300ms to 500ms on DIAL UP!. I even remember getting 150ms when I had a really nice dial up isp. So yea FYI anything over 100ms. = bad. |