creepingdeath

Muy cierto... Yo era cliente de DSL antes de cambiar a Cable. Mientras funcionaba, no ten

Dman! I hate Onelink! Maybe they'll fix the problem the next millenium... year 3000 C:Documents and SettingsCreepingDeath>ping www.google.com -t Pinging www.l.google.com [64.233.161.99] with 32 bytes of data: Request timed out. Request timed out. Reply from 64.233.161.99: bytes=32 time=88ms TTL=242 Reply from 64.233.161.99: bytes=32 time=75ms TTL=242 Reply from 64.233.161.99: bytes=32 time=65ms TTL=242 Reply from 64.233.161.99: bytes=32 time=83ms TTL=242 Reply from 64.233.161.99: bytes=32 time=64ms TTL=242 Reply from 64.233.161.99: bytes=32 time=80ms TTL=242 Reply from 64.233.161.99: bytes=32 time=77ms TTL=242 Reply from 64.233.161.99: bytes=32 time=62ms TTL=242 Reply from 64.233.161.99: bytes=32 time=92ms TTL=242 Reply from 64.233.161.99: bytes=32 time=76ms TTL=242 Request timed out. Reply from 64.233.161.99: bytes=32 time=75ms TTL=242 Reply from 64.233.161.99: bytes=32 time=71ms TTL=242 Reply from 64.233.161.99: bytes=32 time=65ms TTL=242 Reply from 64.233.161.99: bytes=32 time=65ms TTL=242 Reply from 64.233.161.99: bytes=32 time=75ms TTL=242 Reply from 64.233.161.99: bytes=32 time=65ms TTL=242 Request timed out. Request timed out. Reply from 64.233.161.99: bytes=32 time=80ms TTL=242 Reply from 64.233.161.99: bytes=32 time=93ms TTL=242 Reply from 64.233.161.99: bytes=32 time=68ms TTL=242 Reply from 64.233.161.99: bytes=32 time=82ms TTL=242 Reply from 64.233.161.99: bytes=32 time=96ms TTL=242 Reply from 64.233.161.99: bytes=32 time=84ms TTL=242 Reply from 64.233.161.99: bytes=32 time=78ms TTL=242 Reply from 64.233.161.99: bytes=32 time=82ms TTL=242 Reply from 64.233.161.99: bytes=32 time=77ms TTL=242 Reply from 64.233.161.99: bytes=32 time=74ms TTL=242 Request timed out. Reply from 64.233.161.99: bytes=32 time=62ms TTL=242

Well, they did something (i hink). Its the first time in months that I can ping an address without getting a request time out. Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:Documents and SettingsCreepingDeath>ping -t www.google.com Pinging www.l.google.com [64.233.161.99] with 32 bytes o Reply from 64.233.161.99: bytes=32 time=63ms TTL=242 Reply from 64.233.161.99: bytes=32 time=60ms TTL=242 Reply from 64.233.161.99: bytes=32 time=68ms TTL=242 Reply from 64.233.161.99: bytes=32 time=65ms TTL=242 Reply from 64.233.161.99: bytes=32 time=62ms TTL=242 Reply from 64.233.161.99: bytes=32 time=65ms TTL=242 Reply from 64.233.161.99: bytes=32 time=74ms TTL=242 Reply from 64.233.161.99: bytes=32 time=67ms TTL=242 Reply from 64.233.161.99: bytes=32 time=70ms TTL=242 Reply from 64.233.161.99: bytes=32 time=61ms TTL=242 Reply from 64.233.161.99: bytes=32 time=67ms TTL=242 Reply from 64.233.161.99: bytes=32 time=64ms TTL=242 Reply from 64.233.161.99: bytes=32 time=68ms TTL=242 Reply from 64.233.161.99: bytes=32 time=59ms TTL=242 Reply from 64.233.161.99: bytes=32 time=62ms TTL=242 Reply from 64.233.161.99: bytes=32 time=67ms TTL=242 Reply from 64.233.161.99: bytes=32 time=59ms TTL=242 Reply from 64.233.161.99: bytes=32 time=59ms TTL=242 Reply from 64.233.161.99: bytes=32 time=64ms TTL=242 Reply from 64.233.161.99: bytes=32 time=69ms TTL=242 Reply from 64.233.161.99: bytes=32 time=68ms TTL=242 Reply from 64.233.161.99: bytes=32 time=59ms TTL=242 Reply from 64.233.161.99: bytes=32 time=63ms TTL=242 Reply from 64.233.161.99: bytes=32 time=62ms TTL=242 Reply from 64.233.161.99: bytes=32 time=67ms TTL=242 Reply from 64.233.161.99: bytes=32 time=63ms TTL=242 Reply from 64.233.161.99: bytes=32 time=68ms TTL=242 Reply from 64.233.161.99: bytes=32 time=67ms TTL=242 Reply from 64.233.161.99: bytes=32 time=67ms TTL=242 Reply from 64.233.161.99: bytes=32 time=64ms TTL=242 Reply from 64.233.161.99: bytes=32 time=59ms TTL=242 Reply from 64.233.161.99: bytes=32 time=67ms TTL=242 Reply from 64.233.161.99: bytes=32 time=60ms TTL=242 Reply from 64.233.161.99: bytes=32 time=59ms TTL=242 Reply from 64.233.161.99: bytes=32 time=61ms TTL=242 Reply from 64.233.161.99: bytes=32 time=64ms TTL=242 Reply from 64.233.161.99: bytes=32 time=72ms TTL=242 Reply from 64.233.161.99: bytes=32 time=115ms TTL=242 Reply from 64.233.161.99: bytes=32 time=64ms TTL=242 Reply from 64.233.161.99: bytes=32 time=64ms TTL=242 Reply from 64.233.161.99: bytes=32 time=64ms TTL=242 Reply from 64.233.161.99: bytes=32 time=67ms TTL=242 Reply from 64.233.161.99: bytes=32 time=65ms TTL=242 Reply from 64.233.161.99: bytes=32 time=61ms TTL=242 Reply from 64.233.161.99: bytes=32 time=58ms TTL=242 Reply from 64.233.161.99: bytes=32 time=67ms TTL=242 Reply from 64.233.161.99: bytes=32 time=67ms TTL=242 Reply from 64.233.161.99: bytes=32 time=63ms TTL=242 Reply from 64.233.161.99: bytes=32 time=59ms TTL=242 Reply from 64.233.161.99: bytes=32 time=66ms TTL=242 Reply from 64.233.161.99: bytes=32 time=78ms TTL=242 Reply from 64.233.161.99: bytes=32 time=61ms TTL=242 Reply from 64.233.161.99: bytes=32 time=60ms TTL=242

osva is one of the lucky ones... look at my ping test: Pinging www.l.google.com [64.233.161.99] with 32 bytes of data: Reply from 64.233.161.99: bytes=32 time=62ms TTL=240 Reply from 64.233.161.99: bytes=32 time=78ms TTL=240 Reply from 64.233.161.99: bytes=32 time=69ms TTL=240 Reply from 64.233.161.99: bytes=32 time=64ms TTL=240 Request timed out. Request timed out. Request timed out. Reply from 64.233.161.99: bytes=32 time=224ms TTL=240 Reply from 64.233.161.99: bytes=32 time=63ms TTL=240 Request timed out. Request timed out. Request timed out. Request timed out. Reply from 64.233.161.99: bytes=32 time=61ms TTL=240 Reply from 64.233.161.99: bytes=32 time=59ms TTL=240 Reply from 64.233.161.99: bytes=32 time=62ms TTL=240 Reply from 64.233.161.99: bytes=32 time=71ms TTL=240 Reply from 64.233.161.99: bytes=32 time=77ms TTL=240 Reply from 64.233.161.99: bytes=32 time=65ms TTL=240 Request timed out. Request timed out. Request timed out. Reply from 64.233.161.99: bytes=32 time=60ms TTL=240 Reply from 64.233.161.99: bytes=32 time=75ms TTL=240 Reply from 64.233.161.99: bytes=32 time=61ms TTL=240 Reply from 64.233.161.99: bytes=32 time=64ms TTL=240 Request timed out. Request timed out. Reply from 64.233.161.99: bytes=32 time=60ms TTL=240 Reply from 64.233.161.99: bytes=32 time=61ms TTL=240 Reply from 64.233.161.99: bytes=32 time=62ms TTL=240

12:10am... Still crappy Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:Documents and SettingsCreepingDeath>ping -t www.yahoo.com Pinging www.yahoo.akadns.net [68.142.197.74] with 32 bytes Reply from 68.142.197.74: bytes=32 time=162ms TTL=48 Reply from 68.142.197.74: bytes=32 time=174ms TTL=49 Reply from 68.142.197.74: bytes=32 time=146ms TTL=49 Request timed out. Reply from 68.142.197.74: bytes=32 time=161ms TTL=49 Reply from 68.142.197.74: bytes=32 time=154ms TTL=49 Reply from 68.142.197.74: bytes=32 time=158ms TTL=49 Reply from 68.142.197.74: bytes=32 time=142ms TTL=48 Reply from 68.142.197.74: bytes=32 time=125ms TTL=48 Request timed out. Request timed out. Reply from 68.142.197.74: bytes=32 time=112ms TTL=48 Reply from 68.142.197.74: bytes=32 time=140ms TTL=48 Reply from 68.142.197.74: bytes=32 time=155ms TTL=49 Request timed out. Reply from 68.142.197.74: bytes=32 time=353ms TTL=49 Reply from 68.142.197.74: bytes=32 time=255ms TTL=49 Reply from 68.142.197.74: bytes=32 time=154ms TTL=49

This sucks... The last time I played and online gme was last december, before the change. Since Onelink started the transition, I can't play online. Latencty is too high... Even the downloads sucks!

9:05am... Pinging googlemail.l.google.com [66.249.83.83] with Reply from 66.249.83.83: bytes=32 time=49ms TTL=243 Reply from 66.249.83.83: bytes=32 time=56ms TTL=243 Reply from 66.249.83.83: bytes=32 time=179ms TTL=243 Reply from 66.249.83.83: bytes=32 time=135ms TTL=243 Reply from 66.249.83.83: bytes=32 time=84ms TTL=243 Reply from 66.249.83.83: bytes=32 time=50ms TTL=243 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 66.249.83.83: bytes=32 time=51ms TTL=243 Reply from 66.249.83.83: bytes=32 time=51ms TTL=243 Reply from 66.249.83.83: bytes=32 time=51ms TTL=243 Reply from 66.249.83.83: bytes=32 time=50ms TTL=243 Reply from 66.249.83.83: bytes=32 time=51ms TTL=243

9:36pm... No luck sending the email... Reply from 68.142.197.88: bytes=32 time=111ms TTL=51 Reply from 68.142.197.88: bytes=32 time=108ms TTL=51 Request timed out. Request timed out. Request timed out. Reply from 68.142.197.88: bytes=32 time=121ms TTL=52 Reply from 68.142.197.88: bytes=32 time=72ms TTL=51 Reply from 68.142.197.88: bytes=32 time=80ms TTL=51 Reply from 68.142.197.88: bytes=32 time=89ms TTL=52 Request timed out. Request timed out. Request timed out. Reply from 68.142.197.88: bytes=32 time=114ms TTL=51 Reply from 68.142.197.88: bytes=32 time=89ms TTL=51 Reply from 68.142.197.88: bytes=32 time=95ms TTL=52 Reply from 68.142.197.88: bytes=32 time=67ms TTL=52 Request timed out. Request timed out. Request timed out. Reply from 68.142.197.88: bytes=32 time=120ms TTL=52 Reply from 68.142.197.88: bytes=32 time=131ms TTL=51 Request timed out. Request timed out. Reply from 68.142.197.88: bytes=32 time=107ms TTL=51 Reply from 68.142.197.88: bytes=32 time=85ms TTL=52 Reply from 68.142.197.88: bytes=32 time=102ms TTL=52 Reply from 68.142.197.88: bytes=32 time=105ms TTL=51 Reply from 68.142.197.88: bytes=32 time=114ms TTL=51 Request timed out.

Damn! Im trying to send an email with a 7mb attachment... Its been almost 10 minutes, and I cant send it! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks! Onelink sucks!

Im at Toa Baja, near Estancias de La Fuente... Ping to www.yahoo.com, at 9:15pm Reply from 68.142.197.88: bytes=32 time=107ms TTL=5 Reply from 68.142.197.88: bytes=32 time=101ms TTL=5 Reply from 68.142.197.88: bytes=32 time=226ms TTL=5 Reply from 68.142.197.88: bytes=32 time=99ms TTL=52 Reply from 68.142.197.88: bytes=32 time=1975ms TTL= Reply from 68.142.197.88: bytes=32 time=82ms TTL=51 Reply from 68.142.197.88: bytes=32 time=133ms TTL=5 Reply from 68.142.197.88: bytes=32 time=90ms TTL=51 Request timed out. Request timed out. Reply from 68.142.197.88: bytes=32 time=111ms TTL=5 Reply from 68.142.197.88: bytes=32 time=66ms TTL=52 Reply from 68.142.197.88: bytes=32 time=82ms TTL=51 Reply from 68.142.197.88: bytes=32 time=83ms TTL=51 Reply from 68.142.197.88: bytes=32 time=95ms TTL=51 Reply from 68.142.197.88: bytes=32 time=113ms TTL=5 Reply from 68.142.197.88: bytes=32 time=70ms TTL=51 Reply from 68.142.197.88: bytes=32 time=116ms TTL=5 Reply from 68.142.197.88: bytes=32 time=102ms TTL=5 Reply from 68.142.197.88: bytes=32 time=116ms TTL=5 Reply from 68.142.197.88: bytes=32 time=118ms TTL=5 Reply from 68.142.197.88: bytes=32 time=98ms TTL=51 Request timed out. Request timed out. Request timed out. Reply from 68.142.197.88: bytes=32 time=190ms TTL=5 Reply from 68.142.197.88: bytes=32 time=158ms TTL=5 Reply from 68.142.197.88: bytes=32 time=91ms TTL=52 Reply from 68.142.197.88: bytes=32 time=102ms TTL=5 Reply from 68.142.197.88: bytes=32 time=93ms TTL=52 Request timed out. Request timed out. Reply from 68.142.197.88: bytes=32 time=97ms TTL=51

Took almost a minute to post the last message! This is a ping to www.google.com Reply from 64.233.161.99: bytes=32 time=62ms TTL=243 Reply from 64.233.161.99: bytes=32 time=62ms TTL=243 Reply from 64.233.161.99: bytes=32 time=58ms TTL=243 Reply from 64.233.161.99: bytes=32 time=60ms TTL=243 Request timed out. Request timed out. Reply from 64.233.161.99: bytes=32 time=60ms TTL=243 Reply from 64.233.161.99: bytes=32 time=58ms TTL=243 Reply from 64.233.161.99: bytes=32 time=56ms TTL=243 Request timed out. Request timed out. Reply from 64.233.161.99: bytes=32 time=67ms TTL=243 Reply from 64.233.161.99: bytes=32 time=67ms TTL=243 Reply from 64.233.161.99: bytes=32 time=79ms TTL=243 Reply from 64.233.161.99: bytes=32 time=64ms TTL=243 Request timed out. Request timed out. Reply from 64.233.161.99: bytes=32 time=72ms TTL=243 Reply from 64.233.161.99: bytes=32 time=59ms TTL=243 Request timed out. Request timed out. Request timed out. Reply from 64.233.161.99: bytes=32 time=58ms TTL=243 Reply from 64.233.161.99: bytes=32 time=59ms TTL=243 Reply from 64.233.161.99: bytes=32 time=59ms TTL=243 Request timed out. Request timed out. Request timed out. Reply from 64.233.161.99: bytes=32 time=59ms TTL=243 Reply from 64.233.161.99: bytes=32 time=57ms TTL=243 Reply from 64.233.161.99: bytes=32 time=56ms TTL=243

February 25, 7:20am, lots of timeouts... :::.. Download Stats ..::: Connection is:: 3606 Kbps about 3.6 Mbps (tested with 2992 kB) Download Speed is:: 440 kB/s Tested From:: https://testmy.net (server1) Test Time:: Sat Feb 25 07:18:37 UTC-0400 2006 Bottom Line:: 64X faster than 56K 1MB download in 2.33 sec Diagnosis: Awesome! 20% + : 68.5 % faster than the average for host (onelinkpr.net) Validation Link:: https://testmy.net/stats/id-X6Q0IEKA3

You couldn't put it better Robocop! Onelink started with the left foot. Maybe they have problem and they're trying to fix them. Fine!!!! But, why they don't tell that to the customers? Why they keep charging us $50 for a service that doesn't work? Any company would give u a credit if their service didn't worked... But NO! Onelink is special! This is the beggining... Im sure that in a couple of months (or weeks!), they will send us a letter with new prices (higher) for the same crappy services... Ill start to look at the PRTC/DirectTV packages.. Do the same!

Im at work right now, but when i get home, ill call and see what onelink's personnel will tell me about this, and when its going to be fixed. If they start talking crap (im sure of that), ill cancel the service, and ill go to DSL (again...)

I think that the idea TheSavior said, about writing to El Nuevo Dia, is a good one. We are paying almost $50 bucks every month (is not cheap!) for the service, and we have the right to demand a better service, or an explanation and our money back.