dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
56935
share rss forum feed


Smith6612
Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:24
Reviews:
·Verizon Online DSL
·Frontier Communi..
reply to Harleysatt

Re: [Internet] For anyone seeing speed issues...

No need for the 800ms screenshot. I believe you.

Looks like you're another one of those individuals seeing a slowdown in the old Epix network. Distance from town shouldn't make a difference as to how well or how poorly your service performs if you have it, or should the copper matter as long as it's in good shape and up to typical telco specs. What does make a difference is the kind of backhaul going from the DSLAM to the rest of the network. If what is in your area happens to be bonded T1s, maybe a T3/DS3 or an OC3 and it's being overloaded when everyone arrives home from school and work, it is a matter of the ISP bringing additional capacity to the equipment to ease up on the issue. Getting 1ms latency on DSL is pretty hard to achieve due to ATM and Error Checking, but I know with DSL you can certainly get down to 4-5ms to the first ISP hop!


Dr_Fubar

join:2012-03-07
reply to Smith6612

Sorry for the late response. Nice to see DSLReports back online.

They actually fixed our internet on around May 5th, 2012; a month after it went down. We were up from 1Mbit to our provisioned speed of 3Mbit. It was amazing!

This is in the Hampshire County, WV (Capon Bridge) area.

Up until May 26, 2012, now it looks like a DNS server went down somewhere:

quote:
/bin/bash:~ Dr_Fubar$ traceroute frontier.com
traceroute to frontier.com (66.133.172.205), 64 hops max, 52 byte packets
1 192.168.254.254 (192.168.254.254) 7.808 ms 1.349 ms 0.995 ms
2 74-47-212-1.dr02.rmny.wv.frontiernet.net (74.47.212.1) 15.927 ms 18.024 ms 16.563 ms
3 70.100.31.185 (70.100.31.185) 13.389 ms 13.556 ms 14.624 ms
4 184.19.145.65 (184.19.145.65) 17.968 ms 16.734 ms 16.458 ms
5 ae5--2--ge.cor02.asbn.va.frontiernet.net (74.40.1.237) 26.539 ms 28.604 ms 25.894 ms
6 ae3---0.cor01.roch.ny.frontiernet.net (74.40.5.17) 35.419 ms 37.544 ms 99.612 ms
7 ge--0-1-0---0.car02.roch.ny.frontiernet.net (74.40.5.186) 37.537 ms 37.257 ms 37.678 ms
8 74.45.102.10 (74.45.102.10) 38.316 ms 37.943 ms 38.702 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *

And so forth... Not sure what the issue is here yet. I doubted it will be fixed on the weekend and it certainly isn't going to be fixed today (Memorial Day).

jtlightner

join:2012-05-30
reply to Smith6612

Fort Wayne FiOS Issues (5/30/12)

I am on Frontier FiOS in Fort Wayne and I am having issues. I pay for 35/35 and this last four days have been horrendous for me.

Anyone else in the Fort Wayne area having issues?



alexciarlil

@ohiou.edu
reply to Smith6612

Re: [Internet] For anyone seeing speed issues...

New Frontier customer in the Southern Ohio area. Extremely disappointed and frustrated so far with my service, especially since I work in IT and frequently log into remote machines from home.

So I started doing some digging and the general pattern is that anytime I am using a good bit of bandwidth my latency skyrockets. This means I can play a video game and have decent latency, but as soon as I try to stream music and play a video game, everything goes to hell. I can watch Netflix, but if I try to browse at the same time same problems. Here is the data I have collected...

Ping while inactive to google (no downloads, streaming, etc...)

500 packets transmitted, 500 received, 0% packet loss, time 499623ms
rtt min/avg/max/mdev = 37.210/57.820/293.664/27.645 ms
 

Ping while downloading 100mb file:
500 packets transmitted, 381 received, 23% packet loss, time 499699ms
rtt min/avg/max/mdev = 108.544/406.395/864.156/147.719 ms
 

Modem Stats:
Transceiver Information Down Stream Path    Up Stream Path
DSL Speed (Kbits/Sec)   3318    95
Margin (dB) 7.0 6.1
Line Attenuation (dB)   53.2    54.3
Transmit Power (dBm)    19.4    11.7
FEC Errors  21724741    0
HEC Errors  391496  1815
CRC Errors  39703   0
 

Traceroute 1:
 1  dslrouter.netgear.com (192.168.254.254)  2.919 ms  2.554 ms  2.572 ms
 2  drr03.athn.oh.frontiernet.net (74.42.148.83)  33.705 ms  35.945 ms  36.088 ms
 3  * * *
 4  xe--9-0-0---0.cor02.chcg.il.frontiernet.net (74.40.1.125)  47.401 ms  48.658 ms  111.662 ms
 5  ae1---0.cbr01.chcg.il.frontiernet.net (74.40.4.142)  43.827 ms  45.284 ms  49.840 ms
 6  72.14.212.143 (72.14.212.143)  52.028 ms  41.780 ms  49.008 ms
 7  209.85.254.120 (209.85.254.120)  74.164 ms  54.141 ms  45.439 ms
 8  209.85.242.215 (209.85.242.215)  63.949 ms  64.715 ms  81.509 ms
 9  209.85.249.45 (209.85.249.45)  82.263 ms  69.791 ms  70.785 ms
10  216.239.48.157 (216.239.48.157)  72.391 ms 216.239.48.59 (216.239.48.59)  70.302 ms  69.723 ms
11  * * *
12  ve-in-f105.1e100.net (173.194.75.105)  105.075 ms  92.943 ms  97.068 ms
 

Traceroute 2:
 1  dslrouter.netgear.com (192.168.254.254)  2.640 ms  2.601 ms  2.539 ms
 2  drr03.athn.oh.frontiernet.net (74.42.148.83)  36.213 ms  43.746 ms  39.590 ms
 3  * * *
 4  xe--9-0-0---0.cor02.chcg.il.frontiernet.net (74.40.1.125)  46.763 ms  71.590 ms  95.259 ms
 5  ae1---0.cbr01.chcg.il.frontiernet.net (74.40.4.142)  53.271 ms  52.037 ms  43.603 ms
 6  72.14.212.143 (72.14.212.143)  42.027 ms  45.716 ms  57.612 ms
 7  209.85.254.120 (209.85.254.120)  48.717 ms  43.098 ms  50.373 ms
 8  209.85.242.215 (209.85.242.215)  74.895 ms  102.210 ms  107.488 ms
 9  209.85.249.45 (209.85.249.45)  93.753 ms  108.448 ms  108.240 ms
10  216.239.48.59 (216.239.48.59)  89.591 ms 216.239.48.157 (216.239.48.157)  113.430 ms  73.584 ms
11  * * *
12  ve-in-f103.1e100.net (173.194.75.103)  97.495 ms  75.183 ms  75.324 ms
 

ATM Stats (sorry for poor formatting):
	
ATM Statistics
 
Stats
Packet Information for:
MTU
VPI / VCI
 
In Errors
In Discard Packets
In Non-Unicast Packets
In Unicast Packets
In Octets
 
Out Errors
Out Discard Packets
Out Non-Unicast Packets
Out Unicast Packets
Out Octets
 
Interface Description
------------------------------------
ATM
PVC1
1492
0/35
 
79422
43460966
0
181871
104220412
 
0
0
0
142290
18932213
 
PPP
 

I am signed up for 7mbit service. I called tech support 10 days ago, got a very nice guy on the phone who seemed knowledgeable and appalled at the figures I was giving him. He said I would be contacted soon to further resolve the issue. He said there should be no reason for me to be seeing so many errors, and my upload speeds were completely out of line with what I was paying for. So far I have had no further communication from them and will be calling again this evening. Just looking for any advice/comments/knowledge from those of you who know what this all means. I came from TWC which was not the best but OH MY GOD worlds better than this crap.

thanks

SuperSpy

join:2012-06-15
Coldwater, MI
reply to Smith6612

Frontier just came and installed DSL this morning and I was curious about the result.

Following the instructions in the OP I got.

34 packets transmitted, 34 packets received, 0% packet loss
round-trip min/avg/max = 45.322/66.508/310.375 ms

while the connection was mostly idle, and
36 packets transmitted, 30 packets received, 16% packet loss
round-trip min/avg/max = 45.908/86.272/304.378 ms

while downloading the 100mb test file linked in the OP.

Router stats page:
DSL Speed (Kbits/Sec) 1788 172
Margin (dB) 15.9 9.8
Line Attenuation (dB) 41.7 56.1
Transmit Power (dBm) 17.1 12.4
FEC Errors 11094 2
HEC Errors 0 0
CRC Errors 0 0

The latency seems high, especially loaded, but also the upload is abysmally slow. My line is pretty long (~3km according to the attenuation calculators), so I was curious if this is normal or if something is amiss.

EDIT: another oddity: the first hop (from my router to the netgear 7550 router/modem) reports between 3 and 6 ms instead of sub-1 ms like one would expect from ethernet.



Smith6612
Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:24
Reviews:
·Verizon Online DSL
·Frontier Communi..

said by SuperSpy:

Frontier just came and installed DSL this morning and I was curious about the result.

Following the instructions in the OP I got.

34 packets transmitted, 34 packets received, 0% packet loss
round-trip min/avg/max = 45.322/66.508/310.375 ms

while the connection was mostly idle, and
36 packets transmitted, 30 packets received, 16% packet loss
round-trip min/avg/max = 45.908/86.272/304.378 ms

while downloading the 100mb test file linked in the OP.

Router stats page:
DSL Speed (Kbits/Sec) 1788 172
Margin (dB) 15.9 9.8
Line Attenuation (dB) 41.7 56.1
Transmit Power (dBm) 17.1 12.4
FEC Errors 11094 2
HEC Errors 0 0
CRC Errors 0 0

The latency seems high, especially loaded, but also the upload is abysmally slow. My line is pretty long (~3km according to the attenuation calculators), so I was curious if this is normal or if something is amiss.

EDIT: another oddity: the first hop (from my router to the netgear 7550 router/modem) reports between 3 and 6 ms instead of sub-1 ms like one would expect from ethernet.

Looks like you've got some sort of Line Problem there anyways. If the problem isn't due to congestion, your upstream is certainly poor and you seem to be having some noise issues on your line. Get a tech out to correct those issues and we'll see if the problem is further down the line in the backbone/CO (I wouldn't doubt it if it was anyways).

jwild

join:2008-12-25
Parkersburg, WV
reply to SuperSpy

What speed are you suppose to have?? Your noise margin is not bad @ 15.9db, just wondering what the speed you should be at(1.5 or 3.0 mb)



Chameleon
Premium
join:2004-11-24
Virden, IL

2 edits
reply to Smith6612

downloadae0---0.cbr0···.pp2.zip 12,568 bytes
pingplotter test 10-14-12
Please help. I don't have time to sit and talk customer service thru this. Get better results thru here.!!!

I have 3meg/1meg package with home-run from NID to modem then into DD-WRT WRT54GL. I have been having issues with computer's connections when playing Netflix. Not necessarily speeds.

I have Ping-Plotter »www.pingplotter.com/ to do the work. The last hop is Frontier's last before hitting Level3 networks.

Also I have DSLR monitoring my IP. It's been showing packet loss, and that's what I'm seeing with Ping-Plotter.

At 7:34 I started the test without load/traffic.

7:35 started load from FCC site 688MB download (345KB/sec steady at 50% downloaded) ended at 7:56

7:58 started PS3 with Netflix.

8:03 continuing Netflix and added download from above. (roughly 55-120KB/sec at 15-20% downloaded - jumping around often).

8:24 stopped FCC download left Netflix going.

Can someone explain what is going on?


Max Allowed Speed (kbps) 3360 864
SN Margin (dB) 31.0
Line Attenuation (dB) 20.0

To modem To internet
Loss of Signal 0 -
Loss of Frame 0 0
CRC Errors 1 137


edit: added signal info

Thanks in advance.

Mark
--
I used to have super human powers.....

But my therapist took them away.

richardf

join:2011-01-29
Las Vegas, NV

Click for full size
DSL Speed (Kbits/Sec) 2624 316
Margin (dB) 18.7 24.0
Line Attenuation (dB) 56.0 32.8
Transmit Power (dBm) 0.5 12.2
FEC Errors 0 0
HEC Errors 204 90
CRC Errors 363 0

Errored Seconds 324
LOS Errors 0

»speedtest.net/result/2286409891.png

From Fort Mohave, Arizona
6Mbps/769k Plan

gonewthedsm

join:2009-12-07
Bruceton Mills, WV
reply to Smith6612

Smith,

These were completed on 1:00pm 11/11/12. (Connection is not bad at this time)
Please let me know your thoughts. I hope there is help for me yet because I am more that frustrated with Frontier. Over 4 years have I suffered with their so call high speed internet. With no hope in sight.

Set at 2624/640 but I believe my area is provisioned for 1mbps.

Normal Run

C:\Windows\system32>ping -t 74.42.149.41

Pinging 74.42.149.41 with 32 bytes of data:
Reply from 74.42.149.41: bytes=32 time=91ms TTL=62
Reply from 74.42.149.41: bytes=32 time=71ms TTL=62
Reply from 74.42.149.41: bytes=32 time=42ms TTL=62
Reply from 74.42.149.41: bytes=32 time=19ms TTL=62
Reply from 74.42.149.41: bytes=32 time=20ms TTL=62
Reply from 74.42.149.41: bytes=32 time=33ms TTL=62
Reply from 74.42.149.41: bytes=32 time=36ms TTL=62
Reply from 74.42.149.41: bytes=32 time=35ms TTL=62
Reply from 74.42.149.41: bytes=32 time=22ms TTL=62
Reply from 74.42.149.41: bytes=32 time=18ms TTL=62
Reply from 74.42.149.41: bytes=32 time=42ms TTL=62
Reply from 74.42.149.41: bytes=32 time=16ms TTL=62
Reply from 74.42.149.41: bytes=32 time=16ms TTL=62
Reply from 74.42.149.41: bytes=32 time=21ms TTL=62
Reply from 74.42.149.41: bytes=32 time=16ms TTL=62
Reply from 74.42.149.41: bytes=32 time=20ms TTL=62
Reply from 74.42.149.41: bytes=32 time=17ms TTL=62
Reply from 74.42.149.41: bytes=32 time=16ms TTL=62
Reply from 74.42.149.41: bytes=32 time=16ms TTL=62
Reply from 74.42.149.41: bytes=32 time=19ms TTL=62
Reply from 74.42.149.41: bytes=32 time=16ms TTL=62
Reply from 74.42.149.41: bytes=32 time=16ms TTL=62
Reply from 74.42.149.41: bytes=32 time=29ms TTL=62

Ping statistics for 74.42.149.41:
Packets: Sent = 23, Received = 23, Lost = 0 (0% los
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 91ms, Average = 28ms
Control-C
^C
Load Run

C:\Windows\system32>ping -t 74.42.149.41

Pinging 74.42.149.41 with 32 bytes of data:
Reply from 74.42.149.41: bytes=32 time=441ms TTL=62
Reply from 74.42.149.41:
Reply from 74.42.149.41: Enter char to copy up to:
Reply from 74.42.149.41:
Reply from 74.42.149.41: bytes=32 time=462ms TTL=62
Reply from 74.42.149.41: bytes=32 time=479ms TTL=62
Reply from 74.42.149.41: bytes=32 time=465ms TTL=62
Reply from 74.42.149.41: bytes=32 time=398ms TTL=62
Reply from 74.42.149.41: bytes=32 time=396ms TTL=62
Reply from 74.42.149.41: bytes=32 time=444ms TTL=62
Reply from 74.42.149.41: bytes=32 time=392ms TTL=62
Reply from 74.42.149.41: bytes=32 time=386ms TTL=62
Reply from 74.42.149.41: bytes=32 time=400ms TTL=62
Reply from 74.42.149.41: bytes=32 time=395ms TTL=62
Reply from 74.42.149.41: bytes=32 time=426ms TTL=62
Reply from 74.42.149.41: bytes=32 time=425ms TTL=62
Reply from 74.42.149.41: bytes=32 time=390ms TTL=62
Reply from 74.42.149.41: bytes=32 time=368ms TTL=62
Reply from 74.42.149.41: bytes=32 time=463ms TTL=62
Reply from 74.42.149.41: bytes=32 time=373ms TTL=62
Reply from 74.42.149.41: bytes=32 time=372ms TTL=62

Ping statistics for 74.42.149.41:
Packets: Sent = 21, Received = 21, Lost = 0 (0% los
Approximate round trip times in milli-seconds:
Minimum = 368ms, Maximum = 479ms, Average = 418ms

http://www.dslreports.com/testhistory/1694608/8addb






whenthepawn

join:2012-06-22
Martin, TN

I've been experiencing terrible speed today (download/upload).

I called the Tech support line to see if there was a network status message, but nope.

Here is what Fronter's speed test said a few minutes ago (I'm about 3 hours away from Cookeville, TN):

Download Speed: 377 kbps (47.1 KB/sec transfer rate)
Upload Speed: 56 kbps (7 KB/sec transfer rate)
Latency: 252 ms
Tuesday, February 05, 2013 2:36:55 PM

Anyone else near me having issues?

Expand your moderator at work

atigerman

join:2002-01-19
Tigerton, WI

1 edit
reply to Smith6612

Re: [Internet] For anyone seeing speed issues...

Click for full size
Let me post up my stats once. I have dsl max

This is a check with no load
Tracing route to google.com [74.125.225.131]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms dslrouter.netgear.com [192.168.254.254]
2 15 ms 15 ms 16 ms 74-33-176-1.br1.civl.wi.frontiernet.net [74.33.176.1]
3 16 ms 15 ms 16 ms 184.9.115.17
4 18 ms 17 ms 17 ms ge--7-0-3---0.arr01.waus.wi.frontiernet.net [74.42.150.81]
5 18 ms 17 ms 18 ms xe--5-2-0---0.car01.waus.wi.frontiernet.net [74.40.4.25]
6 61 ms 30 ms 31 ms xe--10-1-0---0.cor02.chcg.il.frontiernet.net [74.40.4.29]
7 29 ms 28 ms 29 ms ae1---0.cbr01.chcg.il.frontiernet.net [74.40.4.142]
8 28 ms 28 ms 28 ms 72.14.212.143
9 29 ms 28 ms 28 ms 209.85.254.128
10 28 ms 29 ms 29 ms 209.85.240.152
11 28 ms 29 ms 28 ms ord08s09-in-f3.1e100.net [74.125.225.131]
Trace complete.

This is a check with load
Tracing route to google.com [74.125.225.64]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms dslrouter.netgear.com [192.168.254.254]
2 526 ms 502 ms 445 ms 74-33-176-1.br1.civl.wi.frontiernet.net [74.33.176.1]
3 489 ms 514 ms 538 ms 184.9.115.17
4 531 ms 542 ms 591 ms ge--7-0-3---0.arr01.waus.wi.frontiernet.net [74.42.150.81]
5 582 ms 576 ms 559 ms xe--5-2-0---0.car01.waus.wi.frontiernet.net [74.40.4.25]
6 601 ms 582 ms 582 ms xe--10-1-0---0.cor02.chcg.il.frontiernet.net [74.40.4.29]
7 514 ms 546 ms 603 ms ae1---0.cbr01.chcg.il.frontiernet.net [74.40.4.142]
8 536 ms 45 ms 552 ms 72.14.212.143
9 625 ms * 602 ms 209.85.254.128
10 551 ms 541 ms 548 ms 209.85.250.30
11 574 ms 572 ms 553 ms ord08s07-in-f0.1e100.net [74.125.225.64]
Trace complete.

Ping check with no load

Pinging 74.33.176.1 with 32 bytes of data:
Reply from 74.33.176.1: bytes=32 time=17ms TTL=254
Reply from 74.33.176.1: bytes=32 time=29ms TTL=254
Reply from 74.33.176.1: bytes=32 time=16ms TTL=254
Reply from 74.33.176.1: bytes=32 time=16ms TTL=254
Reply from 74.33.176.1: bytes=32 time=16ms TTL=254
Reply from 74.33.176.1: bytes=32 time=16ms TTL=254
Reply from 74.33.176.1: bytes=32 time=16ms TTL=254
Reply from 74.33.176.1: bytes=32 time=15ms TTL=254
Reply from 74.33.176.1: bytes=32 time=17ms TTL=254
Reply from 74.33.176.1: bytes=32 time=17ms TTL=254
Reply from 74.33.176.1: bytes=32 time=17ms TTL=254
Reply from 74.33.176.1: bytes=32 time=16ms TTL=254
Reply from 74.33.176.1: bytes=32 time=17ms TTL=254
Reply from 74.33.176.1: bytes=32 time=16ms TTL=254
Reply from 74.33.176.1: bytes=32 time=19ms TTL=254
Reply from 74.33.176.1: bytes=32 time=16ms TTL=254
Reply from 74.33.176.1: bytes=32 time=16ms TTL=254
Reply from 74.33.176.1: bytes=32 time=18ms TTL=254
Reply from 74.33.176.1: bytes=32 time=16ms TTL=254
Reply from 74.33.176.1: bytes=32 time=17ms TTL=254
Reply from 74.33.176.1: bytes=32 time=18ms TTL=254
Reply from 74.33.176.1: bytes=32 time=17ms TTL=254
Reply from 74.33.176.1: bytes=32 time=16ms TTL=254
Reply from 74.33.176.1: bytes=32 time=16ms TTL=254
Reply from 74.33.176.1: bytes=32 time=16ms TTL=254
Reply from 74.33.176.1: bytes=32 time=16ms TTL=254
Reply from 74.33.176.1: bytes=32 time=16ms TTL=254
Reply from 74.33.176.1: bytes=32 time=17ms TTL=254
Reply from 74.33.176.1: bytes=32 time=17ms TTL=254
Reply from 74.33.176.1: bytes=32 time=16ms TTL=254
Reply from 74.33.176.1: bytes=32 time=17ms TTL=254
Reply from 74.33.176.1: bytes=32 time=16ms TTL=254
Reply from 74.33.176.1: bytes=32 time=16ms TTL=254
Reply from 74.33.176.1: bytes=32 time=16ms TTL=254
Reply from 74.33.176.1: bytes=32 time=17ms TTL=254
Reply from 74.33.176.1: bytes=32 time=19ms TTL=254
Reply from 74.33.176.1: bytes=32 time=16ms TTL=254
Reply from 74.33.176.1: bytes=32 time=18ms TTL=254
Reply from 74.33.176.1: bytes=32 time=21ms TTL=254
Reply from 74.33.176.1: bytes=32 time=18ms TTL=254
Reply from 74.33.176.1: bytes=32 time=19ms TTL=254
Reply from 74.33.176.1: bytes=32 time=16ms TTL=254
Reply from 74.33.176.1: bytes=32 time=16ms TTL=254
Reply from 74.33.176.1: bytes=32 time=15ms TTL=254
Reply from 74.33.176.1: bytes=32 time=16ms TTL=254
Reply from 74.33.176.1: bytes=32 time=16ms TTL=254
Reply from 74.33.176.1: bytes=32 time=16ms TTL=254
Reply from 74.33.176.1: bytes=32 time=16ms TTL=254
Reply from 74.33.176.1: bytes=32 time=16ms TTL=254
Reply from 74.33.176.1: bytes=32 time=16ms TTL=254

Ping statistics for 74.33.176.1:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 29ms, Average = 16ms

Ping check with load

Pinging 74.33.176.1 with 32 bytes of data:
Reply from 74.33.176.1: bytes=32 time=456ms TTL=254
Reply from 74.33.176.1: bytes=32 time=427ms TTL=254
Reply from 74.33.176.1: bytes=32 time=446ms TTL=254
Reply from 74.33.176.1: bytes=32 time=456ms TTL=254
Reply from 74.33.176.1: bytes=32 time=455ms TTL=254
Reply from 74.33.176.1: bytes=32 time=477ms TTL=254
Reply from 74.33.176.1: bytes=32 time=437ms TTL=254
Reply from 74.33.176.1: bytes=32 time=461ms TTL=254
Reply from 74.33.176.1: bytes=32 time=459ms TTL=254
Reply from 74.33.176.1: bytes=32 time=438ms TTL=254
Reply from 74.33.176.1: bytes=32 time=458ms TTL=254
Reply from 74.33.176.1: bytes=32 time=428ms TTL=254
Reply from 74.33.176.1: bytes=32 time=395ms TTL=254
Reply from 74.33.176.1: bytes=32 time=459ms TTL=254
Reply from 74.33.176.1: bytes=32 time=455ms TTL=254
Reply from 74.33.176.1: bytes=32 time=127ms TTL=254
Reply from 74.33.176.1: bytes=32 time=486ms TTL=254
Reply from 74.33.176.1: bytes=32 time=478ms TTL=254
Reply from 74.33.176.1: bytes=32 time=449ms TTL=254
Reply from 74.33.176.1: bytes=32 time=441ms TTL=254
Reply from 74.33.176.1: bytes=32 time=468ms TTL=254
Reply from 74.33.176.1: bytes=32 time=465ms TTL=254
Reply from 74.33.176.1: bytes=32 time=475ms TTL=254
Reply from 74.33.176.1: bytes=32 time=480ms TTL=254
Reply from 74.33.176.1: bytes=32 time=457ms TTL=254
Reply from 74.33.176.1: bytes=32 time=443ms TTL=254
Reply from 74.33.176.1: bytes=32 time=454ms TTL=254
Reply from 74.33.176.1: bytes=32 time=502ms TTL=254
Reply from 74.33.176.1: bytes=32 time=484ms TTL=254
Reply from 74.33.176.1: bytes=32 time=478ms TTL=254
Reply from 74.33.176.1: bytes=32 time=497ms TTL=254
Reply from 74.33.176.1: bytes=32 time=497ms TTL=254
Reply from 74.33.176.1: bytes=32 time=473ms TTL=254
Reply from 74.33.176.1: bytes=32 time=486ms TTL=254
Reply from 74.33.176.1: bytes=32 time=461ms TTL=254
Reply from 74.33.176.1: bytes=32 time=444ms TTL=254
Reply from 74.33.176.1: bytes=32 time=462ms TTL=254
Reply from 74.33.176.1: bytes=32 time=476ms TTL=254
Reply from 74.33.176.1: bytes=32 time=477ms TTL=254
Reply from 74.33.176.1: bytes=32 time=461ms TTL=254
Reply from 74.33.176.1: bytes=32 time=481ms TTL=254
Reply from 74.33.176.1: bytes=32 time=464ms TTL=254
Reply from 74.33.176.1: bytes=32 time=442ms TTL=254
Reply from 74.33.176.1: bytes=32 time=453ms TTL=254
Reply from 74.33.176.1: bytes=32 time=440ms TTL=254
Reply from 74.33.176.1: bytes=32 time=424ms TTL=254
Reply from 74.33.176.1: bytes=32 time=444ms TTL=254
Reply from 74.33.176.1: bytes=32 time=401ms TTL=254
Reply from 74.33.176.1: bytes=32 time=409ms TTL=254
Reply from 74.33.176.1: bytes=32 time=388ms TTL=254

Ping statistics for 74.33.176.1:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 127ms, Maximum = 502ms, Average = 449ms

atigerman

join:2002-01-19
Tigerton, WI

Here is a test sample for tonight. A few speed tests i took came back good, it looked like my connection returned to normal. But when i put a ping load on....

Pinging 74.33.176.1 with 32 bytes of data:
Request timed out.
Reply from 74.33.176.1: bytes=32 time=15ms TTL=254
Request timed out.
Request timed out.
Reply from 74.33.176.1: bytes=32 time=15ms TTL=254
Reply from 74.33.176.1: bytes=32 time=70ms TTL=254
Reply from 74.33.176.1: bytes=32 time=15ms TTL=254
Reply from 74.33.176.1: bytes=32 time=68ms TTL=254
Request timed out.
Request timed out.
Reply from 74.33.176.1: bytes=32 time=77ms TTL=254
Reply from 74.33.176.1: bytes=32 time=15ms TTL=254
Reply from 74.33.176.1: bytes=32 time=64ms TTL=254
Request timed out.
Reply from 74.33.176.1: bytes=32 time=66ms TTL=254
Reply from 74.33.176.1: bytes=32 time=61ms TTL=254
Reply from 74.33.176.1: bytes=32 time=23ms TTL=254
Reply from 74.33.176.1: bytes=32 time=15ms TTL=254
Reply from 74.33.176.1: bytes=32 time=74ms TTL=254
Reply from 74.33.176.1: bytes=32 time=15ms TTL=254
Reply from 74.33.176.1: bytes=32 time=63ms TTL=254
Reply from 74.33.176.1: bytes=32 time=63ms TTL=254
Reply from 74.33.176.1: bytes=32 time=41ms TTL=254
Reply from 74.33.176.1: bytes=32 time=15ms TTL=254
Reply from 74.33.176.1: bytes=32 time=60ms TTL=254
Reply from 74.33.176.1: bytes=32 time=63ms TTL=254
Reply from 74.33.176.1: bytes=32 time=48ms TTL=254
Reply from 74.33.176.1: bytes=32 time=43ms TTL=254
Reply from 74.33.176.1: bytes=32 time=15ms TTL=254
Request timed out.
Reply from 74.33.176.1: bytes=32 time=19ms TTL=254
Reply from 74.33.176.1: bytes=32 time=15ms TTL=254
Reply from 74.33.176.1: bytes=32 time=14ms TTL=254
Request timed out.
Reply from 74.33.176.1: bytes=32 time=15ms TTL=254
Reply from 74.33.176.1: bytes=32 time=16ms TTL=254
Reply from 74.33.176.1: bytes=32 time=84ms TTL=254
Reply from 74.33.176.1: bytes=32 time=35ms TTL=254
Reply from 74.33.176.1: bytes=32 time=15ms TTL=254
Reply from 74.33.176.1: bytes=32 time=96ms TTL=254
Reply from 74.33.176.1: bytes=32 time=15ms TTL=254
Reply from 74.33.176.1: bytes=32 time=29ms TTL=254
Request timed out.
Reply from 74.33.176.1: bytes=32 time=54ms TTL=254
Reply from 74.33.176.1: bytes=32 time=56ms TTL=254
Reply from 74.33.176.1: bytes=32 time=82ms TTL=254
Reply from 74.33.176.1: bytes=32 time=15ms TTL=254
Request timed out.
Reply from 74.33.176.1: bytes=32 time=68ms TTL=254
Request timed out.

Ping statistics for 74.33.176.1:
Packets: Sent = 50, Received = 39, Lost = 11 (22% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 96ms, Average = 41ms



bigalby01

@frontiernet.net

My roomate switched us from RR to frontier dsl (Rochester NY)
BAD decision. He thought it was a better deal with sat tv.

My best speed test is 1.91 down and 0.33 up

My traceroute

Tracing route to dslreports.com [64.91.255.98]
over a maximum of 30 hops:

1 11 ms 8 ms 7 ms dslrouter.netgear.com [192.168.254.254]
2 40 ms 38 ms 39 ms 173.87.124.1
3 66 ms 38 ms 38 ms 50.48.10.129
4 52 ms 49 ms 69 ms ae2---0.cor01.roch.ny.frontiernet.net [74.40.1.2
05]
5 56 ms 49 ms 49 ms ae3---0.cor02.asbn.va.frontiernet.net [74.40.5.1
8]
6 54 ms 48 ms 49 ms ae0---0.cbr01.asbn.va.frontiernet.net [74.40.2.1
78]
7 76 ms 69 ms 67 ms p11-2.core01.ord03.atlas.cogentco.com [74.40.26.
150]
8 61 ms 109 ms 82 ms GIGLINX.TenGigabitEthernet3-1.ar5.CHI2.gblx.net
[208.49.135.162]
9 67 ms 68 ms 111 ms lw-dc2-core3-te9-1.rtr.liquidweb.com [209.59.157
.224]
10 68 ms 67 ms 70 ms lw-core6.rtr.liquidweb.com [209.59.157.109]
11 71 ms 159 ms 70 ms lw-dc3-dist15.rtr.liquidweb.com [69.167.128.205]

12 73 ms 68 ms 69 ms www.dslreports.com [64.91.255.98]

Trace complete.

My Ping times

Under no load

Reply from 173.87.124.1: bytes=32 time=37ms TTL=254
Reply from 173.87.124.1: bytes=32 time=43ms TTL=254
Reply from 173.87.124.1: bytes=32 time=44ms TTL=254
Reply from 173.87.124.1: bytes=32 time=38ms TTL=254
Reply from 173.87.124.1: bytes=32 time=43ms TTL=254
Reply from 173.87.124.1: bytes=32 time=39ms TTL=254

Under 100MB file test

Reply from 173.87.124.1: bytes=32 time=445ms TTL=254
Reply from 173.87.124.1: bytes=32 time=381ms TTL=254
Reply from 173.87.124.1: bytes=32 time=430ms TTL=254
Reply from 173.87.124.1: bytes=32 time=420ms TTL=254
Reply from 173.87.124.1: bytes=32 time=382ms TTL=254
Reply from 173.87.124.1: bytes=32 time=392ms TTL=254

I have tried "hard wired ethernet" as well and see no difference. I currently use wireless and am located 5ft from the modem/router

Any help or suggestions are GREATLY appreciated

thank you

alby



do re mi

@frontiernet.net
reply to Smith6612

This incredibly PAINFULLY slow internet has been getting worse each day for a week, what IS the problem??
»www.speedtest.net/my-result/2979502024


System
reply to Smith6612

This topic has been un-stickied by grobinette See Profile