frontierwall..........

[MADe]

Me thinks frontiernet no worky so good in dallas?

I have check multiple times over a series of nights and find a definite choke point repeated again and again.

for what its worth
 

[Skuzzy]

Ping Plot?

My route, from home, takes me through Level3, which is always going to be a bad thing.  Level3 has, substantially, oversold their network.  Packet loss is horrific through that network.

It used to only be during prime time hours, but now it is occurring 24 hours a day.

[MADe]

[Skuzzy]

Sure.  The gateway at Level3 is the problem.

If you have Level3 in your path, it is almost always going to have some packet loss.  That is just how it is with Level3.  Not defending Frontier, but in this case, they are not the direct problem.  They are indirectly the problem as they seem to use Level3 for their Internet transport.

[MADe]

pics are posting odddly sorry.

I am not impressed with TWC ISP services either. Went from 3GB DL to 50GB DL, same price, I cannot really tell a difference, increased latency ta boot.

[MADe]

this was tonight. at log off the server gui was sport'in 450ms+\-

frontiernet is not the only BS, my provider TWC, rr, is as bad......
fyi

50/5 TWC extreme service, how fast should the Late MA load? tonight was 2:43m

I feel as if I am in a 3rd world country, S. Korea has faster internet than moi..................

[Skuzzy]

Has nothing to do with Frontier.  The problems are square in the middle of Level3 and RR in New York.

When problems show up on the last hop, it is due to packet loss on the return trip to your computer.  This is the short coming of any type of Ping Plot/traceroute utility.  They can only show the path to the destination.  They cannot show the path back to the source, unless they are the same, which they never are anymore.

[MADe]

sad part is,
I PAY for the cable service,
I pay to play AH,
I paid for equipment to access service and else in a timely manner.
It now appears no tools will properly inform me as well.

Yet when it comes to getting what I pay for, like a dog chasing its tail. Its always the other guy, its just so sad. I say this because when I approach the service peeps, on my end, I'll bet a pay check, that they will blame it on Frontier or AH servers.
 I realize as well that AH is in the same boat as I.
So sad. I wished I would never have got involved with pc's, the internet, freaking pc games........................ ...................ignorance is bliss.

I will say this Frontier has made a negative impact on my connection to AH servers.
I have been using/ping testing AH servers for years now, there is a marked difference. I cannot speak as to specifics, to much the uninformed, but just from years of basic ping plotter comparisons, things are different.

attach: pre FRontier, right when I switched service to TWC. at Xmas time.

I expect no answers here on this. But I am showing you what I see from my end cause what else can I do........I do not stream movies, or watch TV on pc. I only need a quality setup for AH. AH is the only realtime thing I want or need. It no worky well, I get cranky.

[MADe]

this was right now, best I seen lately and what I have come to expect.

I hate pc's............................ ..

[Skuzzy]

this was right now, best I seen lately and what I have come to expect.

I hate pc's............................ ..

Other than the wide variance at the gateway from RR to Level3, it is not too bad.  No packet loss.  Better than I would have expected.

Unfortunately, the trip back looks a lot worse.  Dropping packets like crazy at Level3 and in the RR network.

 1  71.252.137.1 (71.252.137.1)  0.504 ms  0.693 ms  0.450 ms
 2  172.102.50.176 (172.102.50.176)  3.131 ms 172.102.50.174 (172.102.50.174)  5.913 ms 172.102.52.52 (172.102.52.52)  5.122 ms
 3  ae7---0.scr01.dlls.tx.frontiernet.net (74.40.3.17)  1.989 ms  1.857 ms  1.749 ms
 4  ae0---0.cbr01.dlls.tx.frontiernet.net (74.40.4.14)  2.194 ms ae1---0.cbr01.dlls.tx.frontiernet.net (74.40.1.82)  2.302 ms ae0---0.cbr01.dlls.tx.frontiernet.net (74.40.4.14)  2.249 ms
 5  * lag-102.ear3.Dallas1.Level3.net (4.15.44.125)  2485.589 ms *
 6  * * *
 7  * 0.ae16.pr0.dfw10.tbone.rr.com (66.109.7.165)  11.120 ms  2.131 ms
 8  0.ae9.pr0.dfw10.tbone.rr.com (107.14.16.185)  2.783 ms  2.459 ms  3.016 ms
 9  bu-ether14.chctilwc00w-bcr00.tbone.rr.com (66.109.6.23)  47.713 ms  50.406 ms bu-ether11.dllstx976iw-bcr00.tbone.rr.com (66.109.6.178)  46.371 ms
10  bu-ether24.chctilwc00w-bcr00.tbone.rr.com (66.109.9.40)  48.915 ms bu-ether14.chctilwc00w-bcr00.tbone.rr.com (66.109.6.23)  47.788 ms bu-ether11.chcgildt87w-bcr00.tbone.rr.com (66.109.6.20)  49.682 ms
11  bu-ether11.chcgildt87w-bcr00.tbone.rr.com (66.109.6.20)  50.164 ms  51.367 ms bu-ether11.nycmny837aw-bcr00.tbone.rr.com (66.109.6.24)  46.264 ms
12  bu-ether11.nycmny837aw-bcr00.tbone.rr.com (66.109.6.24)  46.194 ms bu-ether11.nwrknjmd67w-bcr00.tbone.rr.com (66.109.6.26)  47.609 ms  48.431 ms
13  bu-ether11.nwrknjmd67w-bcr00.tbone.rr.com (66.109.6.26)  50.782 ms  50.645 ms  50.263 ms
14  agg2.nyclnyrg01r.nyc.rr.com (107.14.19.25)  45.831 ms agg3.nyclnyrg01r.nyc.rr.com (66.109.3.223)  49.436 ms agg1.nyclnyrg01r.nyc.rr.com (66.109.6.79)  47.704 ms
15  * * agg1.nyquny9101h.nyc.rr.com (68.173.198.121)  46.938 ms

Like you, we can only control the immediate connection to the Internet.  It is getting harder and harder to get around Level3.

[Hungry]

Seems like the same issue I have with Comcast - Dallas Level 3

[Skuzzy]

Would like to see more Ping Plots from different locations around the world.  It may be Frontier has cut the connections down to Lovel3.  When Verizon owned it, they had multiple paths.

[Bizman]

Here's mine.
BTW what is 71.252.137.158 MADe pinged to? Has there been changes in the addresses?

Target Name: static-71-252-137-154.dllstx.fios.frontiernet.net
         IP: 71.252.137.154
  Date/Time: 3.5.2016 18:25:43 to 3.5.2016 18:30:28

Hop Sent Err   PL% Min Max Avg  Host Name / [IP]
 1    58   0   0,0   0   2   0  P-661HNU-F1.P-661HNU-F1 [192.168.1.1]
 2    58   0   0,0  10  67  14  joeka1.fi.elisa.net [88.113.72.1]
 3    58   0   0,0  17  42  22  [139.97.10.215]
 4    58   0   0,0  16  23  17  AT5-0-241.jkyla261-gw.fi.elisa.net [139.97.0.13]
 5    58   0   0,0  17  34  18  [139.97.94.55]
 6    58   0   0,0  17  82  20  [213.192.186.77]
 7    58   0   0,0  22  31  22  [213.192.184.74]
 8    58  11  19,0  23  27  23  [212.73.250.181]
 9    57  57 100,0   0   0   0   [-]
10    58   0   0,0 169 182 170  [4.15.44.126]
11    58   0   0,0 169 171 170  ae3---0.scr02.dlls.tx.frontiernet.net [74.40.1.81]
12    58   0   0,0 171 181 175  be10---0.lcr22.dlls.tx.frontiernet.net [74.40.3.26]
13    58   0   0,0 172 175 172  [172.102.50.175]
14    58   0   0,0 171 173 172  static-71-252-137-154.dllstx.fios.frontiernet.net [71.252.137.154]

[MADe]

Biz I did mistakenly use the beta server ping plot once, but its basically an identical path to late war server .154.

The only job these providers have is to provide clear, uncongested, internet connections yet this breaks down whilest they try to steal content and pretend to be a content provider, which they are not. Content providers, AH, suffer as much as the client in their incompetence.

[MADe]

Been doing tests at different times and just watched for a week....

around 10pm est was when those really nasty plots were done
the good plot was done 1pm est

It appears that its network overload, 10pm est + 6pm pst = network overload. This time frame +/-, would be nationwide, internet connect, primetime. Looks like the internet infrastructure, during primetime hours is insufficient to handle the load, or streaming usage/throttling is affecting everything. Being a questioning type personality, I had wondered what pushing all the movies, mobile data was gonna do. Now I think I have the answer, kluge it up...........