Reviews:
 ·Charter
| reply to MyTechLife
7:30am 3/12 Packet Loss test here:
»/quality/nil/351130
Even though I passed, we're still seeing high Max Latency beginning at 63.200.232.* (Williams Communications).
I also sometimes check »visualroute.datametrics.com/ to me. Interestingly, from what I recall, about a month ago from the east coast we used to be routed through LA (LSAN) before Reno. Today's tests show me being routed through Dallas and Tulsa first. All of these are part of Williams Communications network. I think ASI's mentioning of our MAJOR problems last week being related to a Prodigy merger and Dallas have some merit.
I think last month's peak hour problem that I was having has gone away. I would lose PPPoE almost daily, and I would get a new IP address afterwards. Now, my IP address hasn't changed since Wednesday night.
In summary, last month I would get consistent speeds around 640, and low latency & packet loss along the entire route to me. The only problem was my DSL was totally unusable from 6-9pm ish. Now I have DSL service during all hours, but have medium latency & packet loss during all hours - and speeds around 620.
Still not perfect, but I imagine that they are working on the problem at 63.200.232.* - unfortunately, that's about the only hop that I can't seem to figure out where it's located at (Tulsa? Reno?) |
|
|
|
| reply to Anon
Re: ALMOST Fixed ??? 6:20pm 3/12 LQ TEST, not very good
»/quality/nil/351635
However, speeds at around the time of this LQ test are 620 - better than what I expected. |
|
| reply to Anon
7am 3/13 test:
»/quality/nil/352192
Speed 350 from the West Coast, 612 from the East. It shows in the LQ test. |
|
Anon | Geez..here we go again OH yeah was not to bad there for awhile.
Not the latency monster is back again.
I'm in line for another LQ test. Will post when its done.
I havw also noticed that on some pages, I can't download
any files. Particular those ones where the download starts
automatically. Can't even download from those even if there is a direct "if your download does not start automatically, click here" link.
Sigh...can't they get it right. Looks like its back to the phone again. |
|
Anon | Here we go :
http://www.dslreports.com/quality/nil/352728
http://www.dslreports.com/quality/nil/352449 |
|
Reviews:
·Charter
| Wanna see an @Home LQ check? I was at my mother's house in Sparks today and did a LQ test from her @Home internet connection. Here is a comparison on the average of the 2nd to last hop...
From East Coast
Hers 79.47, Mine 122.97
From West Coast
Hers 11.34, Mine 117.38
Our west coast LQ is suffering BIG TIME!
@Home changes your IP address a lot (I don't know if it's on a 5 minute timer or what), so by the time the test ran, she had a new IP, and I guess it hadn't been assigned to someone else by the time the test actually ran - so some of the tests were canceled, but it still shows the hops, loss, best, avg and worst. Interesting to compare. Here's her @Home test »/quality/nil/353622
Comapre to mine 2 hours later with NBI »/quality/nil/353716
[text was edited by author 2001-03-14 19:34:28] |
|
Anon | reply to MyTechLife
Re: Nevada Bell Latency Problem since March 2 Here is a tracert I did about 10 minutes ago (@ 5:10 PM PST):
C:\>tracert www.nvbell.net
Tracing route to www.nvbell.net [151.164.129.5]
over a maximum of 30 hops:
1 30 ms 30 ms 40 ms adsl-63-201-27-254.dsl.renocs.nvbell.net [63.201.27.254]
2 10 ms 20 ms 20 ms core1-fe-5-0-0.renocs.nvbell.net [63.201.16.129]
3 20 ms 20 ms 20 ms edge1-fe-0-0-0.renocs.nvbell.net [206.13.6.194]
4 40 ms 50 ms 50 ms lsanca1wct1.sbc-reno.10meg.ipcc.wcg.net [151.142.220.205]
5 40 ms 40 ms 50 ms 64.200.232.17
6 70 ms 81 ms 70 ms dllstx1wcx3-oc48.ipcc.wcg.net [64.200.240.5]
7 70 ms 80 ms 70 ms 64.200.232.182
8 70 ms 81 ms 70 ms 64.200.226.74
9 70 ms 81 ms 70 ms srvr2-vlan10.rcsntx.swbell.net [151.164.1.171]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 70 ms 80 ms 80 ms www.nvbell.net [151.164.129.5]
Trace complete.
while my speeds as tested here on DSLR, latency has been horrible.
Here is an LQ I did this morning. This is actually one of the better ones I have had this week.
http://www.dslreports.com/quality/nil/354210
Although this is certainly better than what I was getting about 2 weeks ago, latency is still bad.
I am going to be running PingPlotter tonight when I go to bed and upload the results tomorrow night. |
|
Anon | reply to MyTechLife
Ok...this one sucks http://www.dslreports.com/quality/nil/355599 |
|
Anon | reply to MyTechLife
Re: Nevada Bell Latency Problem since March 2 Well...was doing ok last night...today not looking to good
right now:
http://www.dslreports.com/quality/nil/359287
When the hell are they going to fix this crap?
I was going to run PingPlotter the other day, but kinda forgot. But I ran it for a few hours last night. Traced to
pacbell.net. PingPlotter showed that at about 7pm or so, the trace only went to the first 2 hops, the rest timed out!
This lasted about 3 hours or so. After I re-connected things went back to normal. I have no idea why though.
I am downloading some updates right now, but after that is done, I will be doing some more PingPlotter and LQ tests. |
|
 doctop
join:2001-06-06
Buffalo, NY | reply to MyTechLife
Leave ASI and go to GBIS. They never have any problems. I have been getting between 800k and 1.2 meg d/l for over a year. |
|
| Hey, I'm just curious if they have fixed any problems they may have had in the past. I haven't seen any really recent complaints about nevbell, so I'm curious if they have gotten better at providing their ADSL. |
|
