jhearn
join:2003-01-02
Leesburg, VA
| reply to jeff
Re: Ashburn losing quality (again).
My speed tests have deteriorated dramatically the last few days. Tonight I am seeing around 300 kbps down and 120 kbps up.
In Loudoun County we went through a miserable time with latency and low speeds last year. Looks like its going to be repeated again this year. What happened to the promised upgrades and speeds by the end of 2003? There was a message at the beginning of this forum for a couple months touting the upgrades and speed increases which would be complete by the end of the year. What happened? |
|
cb4492
join:2002-10-09
Westminster, MD
| reply to jeff
Well, I'm not sure if Virginia's problem is directly related to Maryland's or not but support tells me they are aware of the problem and are monitoring it. No ETA for a resolution. BTW, are most of your connections good through out the day and then drop off dramatically approximately between 6 p.m and 12 a.m ? |
|
vortex2050
join:2001-12-23
Purcellville, VA
| reply to csummers67
said by csummers67  :
I have seen the same here in Ashburn, VA. Will they resolve this. I have only been subscribing for 4 months and its been great up until now. I guess this has happened before? How was it resolved?
Was resolved over 6 months later...  This is bad news... |
|
csummers67
join:2003-12-17
Ashburn, VA | reply to jeff
I have seen the same here in Ashburn, VA. Will they resolve this. I have only been subscribing for 4 months and its been great up until now. I guess this has happened before? How was it resolved? |
|
machpost
join:2002-01-11
Washington, DC
| reply to jeff
Things have been slower for me since before the upload speeds were increased. I just ran three speed tests and got 1732/221 kbps, 1711/240 kbps, and 1832/238 kbps. I haven't seen over 2000 kpbs download in many months.
--
Adelphia Power Link. Blazing fast broadband while you sleep! |
|
cb4492
join:2002-10-09
Westminster, MD
3 edits | reply to wh1plash
Right up the road from you guys I've also been getting the same thing here. It all started right around Christmas. |
|
wh1plash
join:2001-07-31
Charles Town, WV
1 edit | reply to jeff
1 69-160-108-1.chvlva.adelphia.net (69.160.108.1) 20.122 ms 17.526 ms 19.666 ms
2 67.20.47.193 (67.20.47.193) 19.222 ms 17.860 ms 19.589 ms
3 68.66.31.174 (68.66.31.174) 19.323 ms 19.977 ms 18.990 ms
4 68.66.31.154 (68.66.31.154) 20.269 ms 20.093 ms 19.582 ms
5 68.168.17.53 (68.168.17.53) 123.389 ms 112.438 ms 110.654 ms
6 24.48.9.129 (24.48.9.129) 105.455 ms 110.828 ms 108.408 ms
7 unk-426d01a1.adelphiacom.net (66.109.1.161) 105.192 ms 96.658 ms 105.239 ms
8 p3-01-02-00.n0.dca91.adelphiacom.net (66.109.0.109) 117.368 ms 117.863 ms 120.434 m
*s
9 p3-00-03-00.n0.lax91.adelphiacom.net (66.109.0.201) 176.625 ms 176.202 ms 181.632 m
*s
10 p3-00-02-00.n0.sjc75.adelphiacom.net (66.109.0.21) 186.918 ms 189.382 ms 187.121 ms
11 p3-00-00-00.r0.sjc75.adelphiacom.net (66.109.0.134) 181.471 ms 191.545 ms 184.431 m
*s
12 p3-04-00-00.p0.sjc90.adelphiacom.net (66.109.3.197) 179.867 ms 185.627 ms 182.098 m
*s
13 unk-426d0d0a.adelphiacom.net (66.109.13.10) 193.833 ms 188.152 ms 179.374 ms
14 vlan27.bas2.scd.yahoo.com (216.115.101.46) 271.503 ms 355.896 ms vl28.bas1.scd.yahoo
*.com (216.115.101.42) 186.611 ms
15 alteon4.68.scd.yahoo.com (66.218.68.13) 184.140 ms 181.549 ms 186.271 ms
(*) WARNING 5 long line(s) split
I'm still seeing some logs in my firewall from nachi infected people. Thought that was suppose to die 1-1-2004 Guess maybe their clocks are set wrong :))) |
|
jeff
join:2002-05-05
Ashburn, VA | reply to jeff
I'm glad Adelphia is acquiring new customers in this area and whatnot, but let's see some network optimization/planning folks!
J |
|
jeff
join:2002-05-05
Ashburn, VA | reply to jeff
Adelphia blocks ICMP echo packets (windows tracert). I was running traceroute off my linux gateway (which uses udp packets).
J |
|
ShoFly
join:2002-12-18
Strasburg, VA | reply to jeff
same here in Front Royal |
|
Pale Horse
join:2002-07-26
Ashburn, VA
| reply to jeff
Yeah, It's getting bad again.
Pinging toast.net [206.244.186.245] with 32 bytes of data:
Reply from 206.244.186.245: bytes=32 time=166ms TTL=139
Reply from 206.244.186.245: bytes=32 time=173ms TTL=139
Reply from 206.244.186.245: bytes=32 time=209ms TTL=139
Reply from 206.244.186.245: bytes=32 time=181ms TTL=139
Ping statistics for 206.244.186.245:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 166ms, Maximum = 209ms, Average = 182ms
For some reason, I can't run a trace to any ip though......
Tracing route to toast.net [206.244.186.245]
over a maximum of 30 hops:
1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
It just times out the whole time... |
|
jhearn
join:2003-01-02
Leesburg, VA | reply to jeff
Same here in Leesburg. Speed tests since the first of the year have also shown a significant decline. The speed test archive for area codes 20175 and 20176 (Leesburg and Ashburn bear this out. |
|
jeff
join:2002-05-05
Ashburn, VA | 6 months great service! But looks like an interface on an Adelphia router is saturated. 3 nights in a row. Anyone else here in Loudoun feeling the pain as well?
J
 |
|
