Gotta love ISP's
|
Herpes |
Posted on 06-12-2012 19:49
|
Senior Member
Posts: 352
Joined: 04/09/2010 16:24
|
So, I noticed in the past few days my pings to the DoGz servers have suddenly risen. It used to be around 60-80, but lately it's been 90-110 constant with high end spikes at 150.
I did a tracert with Visualroute and am double checking the IP's with cqcounter.com but it looks that my connection is supposedly going from WI to NY to CA to IL to TX to NY to TX?
Fuuuck me, is this even possible?
Edited by Herpes on 06-12-2012 20:02
Provehito In Altum - Launch Forth Into the Deep!
"Maybe Steve Irwin should have worn sun screen. It would have protected him from harmful rays."
|
|
|
|
terrowrist |
Posted on 06-12-2012 20:07
|
Fusioneer
Posts: 1277
Joined: 30/06/2011 01:13
|
Well, some server(s) could have network loads which is causing those high pings. Not sure why its hopping so many times.
Who is your ISP?
"Nobody really knows what they're doing. We're all just trying to figure out what makes us happy."
|
|
|
|
Herpes |
Posted on 06-12-2012 20:18
|
Senior Member
Posts: 352
Joined: 04/09/2010 16:24
|
Verizon DSL. It's a consistent ping/tracert too, it doesn't vary much in terms of when I try during the day/night.
Provehito In Altum - Launch Forth Into the Deep!
"Maybe Steve Irwin should have worn sun screen. It would have protected him from harmful rays."
|
|
|
|
Sniper Jesus |
Posted on 06-12-2012 21:42
|
Senior Member
Posts: 226
Joined: 06/04/2011 20:48
|
The same thing is happening to me. It isnt constantly but it seems to do the same weird routing pattern , my ping randomly doubles and the trace sometimes has it going from FL to TN to GA then to TX... (Bright house networks) It seems to only add the Jump to TN after about 6 and only been doing so for a few days. Oh i forgot it sometimes jumps to Kansas.
Edited by Sniper Jesus on 06-12-2012 21:49
|
|
|
|
Blubber |
Posted on 06-12-2012 23:47
|
Veteran Member
Posts: 929
Joined: 24/11/2009 23:54
|
I use to have Qwest (Century Link) DSL and was pulling traceroutes worse than that. It'd bounce from colorado to japan to and then trickle across the country to go from the midwest to an east coast css server. When I contacted the isp and asked them WTF they simply had no understanding what I was talking about or what tace route and ping is which wasn't surprising, considering the tech help center was located half the world away... Hopefully you can get yours figured out though. Since I changed isp's I've never had a reason to trace route. I was told the verizon is pretty good with their fios internet, are you in an area that supports it?)
Don't touch me there.
|
|
|
|
Herpes |
Posted on 07-12-2012 00:32
|
Senior Member
Posts: 352
Joined: 04/09/2010 16:24
|
It's playable, but in a tease-ish sorta way. My connection is like "Oh hey, this is almost just right".... nope. Nuh uh.
Provehito In Altum - Launch Forth Into the Deep!
"Maybe Steve Irwin should have worn sun screen. It would have protected him from harmful rays."
|
|
|
|
TigerOx |
Posted on 07-12-2012 10:02
|
Admin
Posts: 2280
Joined: 07/02/2008 13:29
|
Herpes this is what Limestone said about your traceroute.
Have you contacted your ISP regarding this issue? They control the route from you to us and as the return route is running about 73ms it would be an issue with the route they have chosen.
...
Carl M.
Limestone Networks |
|
|
|
Herpes |
Posted on 07-12-2012 17:39
|
Senior Member
Posts: 352
Joined: 04/09/2010 16:24
|
I just got off the phone with Frontier (they now own all the lines in this area, originally it was Verizon when I was home 6 years ago... whoops).
I'm currently getting 3Mbps down speed, and I should be getting 7Mbps. My modem is old and outdated, should have been upgraded when Frontier took over, and when they had me ping websites I was averaging 607ms and had a high of 1000ms (1 second).
Soooooo yeah, I got a lot of apologies and that a tech should be at our door to check things out because things are definitely not as they should be. lmao
Sweet eebus I've been playing with it like this for how long, sorta can't wait to see how I play AFTER this gets fixed
Provehito In Altum - Launch Forth Into the Deep!
"Maybe Steve Irwin should have worn sun screen. It would have protected him from harmful rays."
|
|
|
|
M3GATRON |
Posted on 12-12-2012 14:43
|
Member
Posts: 132
Joined: 20/01/2010 17:36
|
I like how sometimes I have torrents running in background and my latency still stays the same
Thank you Verizon FiOS
|
|
|
|
Herpes |
Posted on 12-12-2012 17:14
|
Senior Member
Posts: 352
Joined: 04/09/2010 16:24
|
They came, swapped out the old modem and.... basically that's about it.
I'm really debating looking at cheap 3mbps cable at this point. This routing crap is annoying as heck.
Provehito In Altum - Launch Forth Into the Deep!
"Maybe Steve Irwin should have worn sun screen. It would have protected him from harmful rays."
|
|
|
|
Scooby |
Posted on 13-12-2012 12:54
|
Admin
Posts: 1636
Joined: 06/10/2007 14:37
|
ok... so is this a program you run to find this shit out? I'd be curious to see where my crap goes...lol |
|
|
|
Herpes |
Posted on 13-12-2012 15:28
|
Senior Member
Posts: 352
Joined: 04/09/2010 16:24
|
hit start, go to run, enter "command" (or just type command in the search box on Win 7). It'll bring up the command console, type "tracert <ip address of what you want to connect to>" without the "" and the <>.
Each line shows a node that you're connected to, and the times it takes, etc. to get to the destination. Usually you want lower numbers, but if you see one of the hops is ridiculously high, it's where you're getting slowed down. Here's what it looks like:
tracert 69.162.97.19
Tracing route to 19-97-162-69.static.reverse.lstn.net [69.162.97.19]
over a maximum of 30 hops:
1 5 ms 4 ms 3 ms 192.168.1.1
2 36 ms 31 ms 28 ms drr03.snpr.wi.frontiernet.net [74.42.148.70]
3 * * * Request timed out.
4 73 ms 71 ms 117 ms xe--10-1-0---0.cor01.asbn.va.frontiernet.net [74
.40.1.77]
5 72 ms 74 ms 71 ms ae1---0.cor02.chcg.il.frontiernet.net [74.40.2.1
93]
6 72 ms 71 ms 76 ms ae1---0.cbr01.chcg.il.frontiernet.net [74.40.4.1
42]
7 73 ms 71 ms 72 ms mpr1.ord7.us [206.223.119.86]
8 73 ms 73 ms 75 ms xe-1-3-0.cr1.ord2.us.above.net [64.125.30.142]
9 101 ms 102 ms 101 ms xe-2-0-0.cr1.dfw2.us.above.net [64.125.25.134]
10 103 ms 101 ms 100 ms xe-0-1-0.mpr1.dfw1.us.above.net [64.125.27.209]
11 93 ms 130 ms 96 ms 64.125.188.182.t00822-03.above.net [64.125.188.1
82]
12 100 ms 94 ms 93 ms te6-1.bdr2.core1.dllstx3.dallas-idc.com [208.115
.192.58]
13 94 ms 95 ms 94 ms 2-3-31-64.static.reverse.lstn.net [64.31.3.2]
14 93 ms 91 ms 93 ms 19-97-162-69.static.reverse.lstn.net [69.162.97.
19]
I got a call from Frontier today and got to talking with someone on the Help Desk and they had me run tests, along with theirs from their location and they were getting the same bad results and were going to look into it. His results over the phone was "wow, yeah that's definitely not a good routing solution" and he seemed much more concerned after I mentioned my thinking of changing ISP's if this wasn't resolved soon. So, hopefully it works sooooon
Edited by Herpes on 13-12-2012 15:59
Provehito In Altum - Launch Forth Into the Deep!
"Maybe Steve Irwin should have worn sun screen. It would have protected him from harmful rays."
|
|
|
|
Herpes |
Posted on 16-03-2013 14:23
|
Senior Member
Posts: 352
Joined: 04/09/2010 16:24
|
So, I sent a nastygram to Frontier awhile ago on a public review page, and I've been in contact with them several times. After basically being told there is nothing wrong, they called me back saying "Ooops! You were right, one of our partners in the above.net group's server your connection is passing through is causing the issues. We've put a support ticket in, and hopefully it gets resolved."
Can't blame my ISP's customer service on the whole ordeal, but damn. I'd really like the ability to have people die when I shoot them. I haven't played in how long... lol
Provehito In Altum - Launch Forth Into the Deep!
"Maybe Steve Irwin should have worn sun screen. It would have protected him from harmful rays."
|
|
|