Topic 'Re: [Northeast] High pings / bad routing...' in forum 'Verizon Fiber Optics' - dslreports.com

Re: [Northeast] High pings / bad routing...

Fri, 22 Feb 2013 09:45:33 EDT

nycdave posted : rebus9,

Great post. Hopefully some people will actually read it and understand what those of us 'in the know' have understood for years....

ICMP is lowest priority, and a standard outbound trace route can never tell the entire story.

Re: [Northeast] High pings / bad routing...

Thu, 21 Feb 2013 21:52:44 EDT

rebus9 posted :

said by serge87:

@Xtreme2 and serith: I also live outside of Syracuse and am having terrible timing out problems the last week or two. I'd say 1 out of 5 requests to almost any website time out :(

My trace routes to Google, Craigslist and Reddit(notice the timeouts in hops 3-6):

Long post.... and on page 8 it's late in the game, but I really want to stop and shed some light on traceroutes and how they can be misinterpreted.

Timeouts at intermediate hops mean... pay attention... NOTHING. ICMP is low priority and there are many reasons a router might ignore ICMP if it's busy doing something more meaningful, like crunching BGP table updates. Same goes for high latency at INTERMEDIATE hops.

What matters is DESTINATION results. Is there packet loss to the destination? And is there abnormally high latency? Those are the questions that matter.

Something you cannot see, unless you control both endpoints, is REVERSE PATH. If you ride inbound on Verizon to a particular destination, there is no guarantee the return path will be symmetric-- i.e, that the response will come back to you on the same route. Quite often traffic will take another physical path-- or other carriers altogether.

Why? Traffic engineering at the other end. For example, datacenters often use route selection tools that route based on lowest economic cost, not necessarily lowest latency or best path. Many will balance traffic loads across their circuits. If they see too much traffic outbound on their (for example) Level3 transit, they may shift some of it to (example) Cogent or Telia or whatever carriers they have. OR-- they could route based on lowest cost, meaning they'll send the bulk of their OUTBOUND traffic via (for example) Cogent, while still announcing their prefixes (for inbound traffic) through their premium carriers. So never... NEVER, NEVER... assume to know the reverse path unless you can do a traceroute from the host at the other end.

Now, let's discuss the screenshot you posted. You're near Syracuse so we'll consider that in determining expected latency.

Your trace to google-- best guess on where that server is, is NYC. This one is tough to judge because there are so many possibilities for physical path (the actual fiber route), reverse path, etc. At mid-40 ms latency at hops 4-10, if nothing else it's consistent. Given your physical geography, I would not be entirely surprised if upstate NY Verizon fiber faced Boston (Syracuse -> BOS -> NYC) but without a fiber map it's anybody's guess.

Your trace to craigslit-- note that the servers are in Palo Alto. Assuming your physical path is similar to the google trace, meaning in the vicinity of 45 ms to hit NYC, then onto long-haul fiber across country, latency in the 120 ms range is not unreasonable.

Your trace to reddit-- destination server is in the Washington, D.C., area. Given 45 ms from you to NYC, another 10 ms from NYC->DC is not out of line.

Long post, yes. But so many people mis-interpret traceroutes and/or put too much emphasis on them, I felt it appropriate to pass it through a sanity filter.

Re: [Northeast] High pings / bad routing...

Thu, 21 Feb 2013 20:54:47 EDT

Xtreme2damax posted : Can you please be a bit less vague? Earlier in the thread I did provide numerous trace routes, ping test and speed test results. So what do I need to provide to Verizon for them to look into and fix this issue? I understand the lag spikes are due to congestion either through some peering provider or the Verizon routers. It's still unacceptable regardless and should be resolved. It's been a month this issue has been ongoing, other folks here have reported the issue to Verizon and still nothing is being done about it. I've been trying to get a route that isn't congested or less congested but every new route so far exhibits the same issues or similar issues.

Gaming is a hobby I do in my free time and is not my life. I live a very stressful life and gaming is my release at the end of the day.
--
My Website: »www.xtemu.com
My Speedtest: »www.speedtest.net/result/1218984197.png

Re: [Northeast] High pings / bad routing...

Thu, 21 Feb 2013 17:19:58 EDT

RolteC posted : Just noticed my problematic second hop just changed in my traceroutes. Now I get 3-4ms not 8ms to the second hop/most going forward. Lets see what this means tonight and going forward....

Re: [Northeast] High pings / bad routing...

Thu, 21 Feb 2013 07:16:08 EDT

KillABrew posted : Just doing recon, sir. Right now I know more about you than your issue.
I am just asking that you do some research, understand it, and adjust if needed. I provided you a starting point a few comments back and you have not posted anything back since regarding your issue. Do your research, provide your facts, and we maybe able to help you out.

Re: [Northeast] High pings / bad routing...

Wed, 20 Feb 2013 18:25:42 EDT

Xtreme2damax posted : Do I know you from somewhere? Just asking since you posted my name and the initial of my last name. Then again probably not since I nearly forgot my website is in my signature and my whois details are in view for the whole world to see.

I would contact Verizon if I didn't feel it was such a waste and would actually lead to a solution. Plus it's hard for me to get on the phone since I have symptoms of autism which makes it hard for me to verbalize, have productive conversations and socialize in general. The prime reason why I never ever use voice chat in game. If contacting Verizon online was sufficient enough I'd go that route since I have no issues expressing anything in text form.
--
My Website: »www.xtemu.com
My Speedtest: »www.speedtest.net/result/1218984197.png

Re: [Northeast] High pings / bad routing...

Wed, 20 Feb 2013 11:24:42 EDT

RolteC posted : guppy, that is finally a much more clear and concise explanation of what is really going on.

A few people might be right, including myself when we said that out own PON card or something in the CO has going bad or has become oversubscribed.

I say the above not only because of pings and tracerts, but because I couldn't download a few times in the last two months over 10Mbit/sec, VOD was not perfect, VOD menu's took 5 seconds or more to respond, Verizon said they couldn't figure it out and that there was loss at the OLT..... Downloading made my pings to my first hop and on go from 25 to 300 with packet loss during those few nights. Mind you it wasn't for hours on end, just in spurts. Still ruins everything. Some people like myself have users playing games, parents watching VOD and myself trying to dropbox/remote desktop and share files with the fiance. Everything experiences lag/cut outs and just plain annoyances. But once again, my specific example is rare. That is why I started MRTG graphing to a few hops plus outside peers to graph when things happen.

Edit:
Come to think of it, I haven't checked my graphs in a while. Busy with work/family. But looking at my charts towards 4 different FiOS connections, they all have the same spikes around the same time every single night. My first hop graph looks normal, my second hop ping chart is showing the same spikes.

Re: [Northeast] High pings / bad routing...

Wed, 20 Feb 2013 08:34:08 EDT

guppy_fish posted :

said by serge87:

Verizon unleashed potentially 2-4X more bandwidth demand by their 4 million or so FIOS customers, the content sources can't handle the demand at peak times, yes its IS the content source or their ISP and up chain that's the limit, nothing in the FIOS network

You also have things like Netflix, its reported that by the end of the year video streaming ( primarily Nextflix and YouTube ) will by over 50% of the peak traffic, every one comes home and starts watching some sort of video content, this has been increasing at a rate that WILL break the internet as we know it

We have passed a tipping point, its not Verizon in anyway, their network is the single largest network in the US by capacity, the internet and the peering arrangements are not keeping up with demand, which is primarily caused by NetFlix, YouTube and Skype, which has supplanted about 20% of the voice minutes ( measured in billions )

The Internet model was everyone shared in the cost, now you have a few content sources that are disproportionally only pushing bits, its isn't going to work forever and your seeing first hand a global issue that peering is failing as the economic model to keep the internet functional.

Its been is discussion for a decade by people that know about how all this works, the consensus is we are going to have to start having a QOS model, where voice / gaming and other applications get low-latency access and video, which can be buffered and is only one way get the left-over bits

Verizon network is NOT the issue, I have no issues, even at peak times, but I'm not using consumer NetFlix/Gaming/Youtube, which are over-subscribed at the source, not the destination

Oh an there are maybe 5 people moaning about this, out of a couple thousand BBR members that have FIOS

Re: [Northeast] High pings / bad routing...

Tue, 19 Feb 2013 20:42:44 EDT

jk111 posted : Like you said, these issues I'm having with Verizon were non-existant until about a month ago.

Re: [Northeast] High pings / bad routing...

Tue, 19 Feb 2013 20:08:25 EDT

serge87 posted :

said by guppy_fish:

Less traffic on Comcast -to- Google peering, mostly due to much lower average last mile connections speeds

Verizon users, now with the slowest tier of 50mbs can suck the Google peering point dry ...

So now it IS Verizon's fault(due in part to the "Quantum" tiers)? I thought it was 100% the cheap peering partners that weren't meeting their end of the peering agreement in every single case?

All these complaints about horrible latency and packet loss didn't exist on this forum 90 days ago(roughly Nov-Dec 2012)! If the new mantra is that the 'Internet is growing and we must accept it' I'd like to know how could it have changed so drastically in a matter of weeks? :scratches head: It's like someone flipped a switch and here we are a few months later...

Re: [Northeast] High pings / bad routing...

Tue, 19 Feb 2013 19:19:29 EDT

KillABrew posted : So Ken I., if I was VZ I would I wouldnt do anything either. To me you have not built a case about the issue. Put the emulation game stuff down for a bit and really research it to understand it and build your case. Yelling Fix It wont get it done.

»www.youtube.com/watch?v=sKFRSL4wpcY

Re: [Northeast] High pings / bad routing...

Tue, 19 Feb 2013 17:15:07 EDT

Xtreme2damax posted : My complaints with Time Warner were due to having around 30ms - 50ms pings to a local server, that was the only issue. With Fios as long as there are no ping spikes my ping is half of what I was getting with Time Warner. My issue with Time Warner was not ping spikes, nothing like what I am currently experiencing with Fios. I am getting lag spikes so severe with Fios that my ping will shoot up to 75ms - 100ms+ and stay there for a while, lag spikes that completely freeze me ingame when they occur. Makes gaming online frustrating, when my ping decides to spike I usually decide to wait until the next day to play, making sure I get online earlier in the day.
--
My Website: »www.xtemu.com
My Speedtest: »www.speedtest.net/result/1218984197.png

Re: [Northeast] High pings / bad routing...

Tue, 19 Feb 2013 15:34:04 EDT

hubrisnxs posted : dead link for me

Re: [Northeast] High pings / bad routing...

Tue, 19 Feb 2013 15:08:36 EDT

guppy_fish posted : What are you tracing / ping to/from?

Re: [Northeast] High pings / bad routing...

Tue, 19 Feb 2013 15:05:36 EDT

anon posted : Here is a traffic graph I noticed in a router I just installed that is on FiOS...

»www.dropbox.com/s/epgozqopr7e2vt···.php.png

Interesting +100ms spike that never left one random day last week. Not sure what is going on.

Re: [Northeast] High pings / bad routing...

Tue, 19 Feb 2013 14:58:32 EDT

guppy_fish posted :

said by KillABrew:

Hulk Smash!!!!
While guppy_fish may be dealing with some anger issues right now

No anger here :) , I'll just keep posting facts, maybe one day someone will listen ;)

Re: [Northeast] High pings / bad routing...

Tue, 19 Feb 2013 14:57:12 EDT

guppy_fish posted : Less traffic on Comcast -to- Google peering, mostly due to much lower average last mile connections speeds

Verizon users, now with the slowest tier of 50mbs can suck the Google peering point dry ...

Re: [Northeast] High pings / bad routing...

Tue, 19 Feb 2013 14:56:07 EDT

KillABrew posted : Hulk Smash!!!!
While guppy_fish may be dealing with some anger issues right now, I do agree with some of his statements.

Xtreme2damax, you were complaining about TW a while back on the same issue. What are you expecting?

Re: [Northeast] High pings / bad routing...

Tue, 19 Feb 2013 14:52:37 EDT

jk111 posted : I have a Comcast connection as well and never experience the issues im having with Verizon, specifically horrible Youtube streaming. And yes, I check at the same time during the day.

Re: [Northeast] High pings / bad routing...

Tue, 19 Feb 2013 14:40:36 EDT

guppy_fish posted :

said by jk111:

I don't know how you can say it's not a Verizon issue. Earlier traceroutes I've posted show timeouts at verizon peering points, as well as alter peering points, and alter (MCI) is owned by Verizon now. This is a Verizon issue.

I've tried to explain you can't use ping for diagnostics, no one listens
I've tried to explain peering, people don't get it

Verizon isn't the issue, its the paths outside of the network which continually show up at the peering points, meaning your going from Verizons network, which is vastly larger in capacity to any other network ( in capacity ) in the US, to smaller networks, that can't handle the traffic

YouTube/Google is all messed up with the volume of traffic they don't have the peering to support the requests, HD support only makes things worse

Gaming sites are low budget and are constantly getting hosed by over subscription

The bottom line is, the internet has now matches our highway system for performance, when everyone get on it, there are area's that get traffic jams

There are intermittent times within Verizon do have slowdowns, usually a failed router or router table opps maybe a fiber line got cut, but almost all the time it's out Verizon's network.

The issue isn't Verizon, its the expectation that you can get low latency connections to anywhere, anytime .. that is gone forever, well until they implement for pay QOS, so your "important" traffic get priority for a hefty fee .. coming to a bill near you sometime this decade.

If you still believe I'm wrong, I encourage you to switch to you favorite alternative internet provider .. you then will realize its a much bigger issue then Verizon

Re: [Northeast] High pings / bad routing...

Tue, 19 Feb 2013 14:18:47 EDT

KillABrew posted : For just the sake of comparing things, do a search for "looking glass server" and compare their results to yours. At least you will get an idea if it is an issue localized to VZ or seen by other carriers as well. It may also help you set your expectations.

Re: [Northeast] High pings / bad routing...

Tue, 19 Feb 2013 14:13:35 EDT

hubrisnxs posted : I found this email, maybe try shooting them an email with all your traceroutes, and see what course of action they can take or what direction they point you in. This is more for the folks with latency and time outs to TINET's 'tinet-gw.customer' peering point

peering@tinet.net.--

»drpeering.net/workshops/presos/1···uses.pdf

This looks like an SLA for Peering points between several providers including verizon and TINET

It also shows verizon is using OC192's which is just a MAMMOTH connection.

Re: [Northeast] High pings / bad routing...

Tue, 19 Feb 2013 12:34:54 EDT

jk111 posted : I don't know how you can say it's not a Verizon issue. Earlier traceroutes I've posted show timeouts at verizon peering points, as well as alter peering points, and alter (MCI) is owned by Verizon now. This is a Verizon issue.

Re: [Northeast] High pings / bad routing...

Tue, 19 Feb 2013 12:27:41 EDT

McBane posted : This happens (and was predicted on this forum here when Verizon first announced their "Quantum" tiers) any time Verizon ups the FiOS network speeds. Their backbone capacity is never up to par for the FiOS speed upgrades and it takes them 4 to 6 months to fix all their capacity and peering issues.

Re: [Northeast] High pings / bad routing...

Tue, 19 Feb 2013 09:58:10 EDT

guppy_fish posted : Nothing wrong in the trace router to Google except to show the Google peering point in nyc is a choke point ( Googles issue, not Verizon )

And using an Non-Verizon DNS will hammer routing as it bypasses Verizon's preferred routing

Re: [Northeast] High pings / bad routing...

Tue, 19 Feb 2013 09:54:16 EDT

guppy_fish posted : You can vent all you like, its not a Verizon's issue, its the peering points with is the down stream network limitation

Looks like the days of lag free internet are over when all the kiddies go to play their games

Re: [Northeast] High pings / bad routing...

Tue, 19 Feb 2013 00:09:29 EDT

Xtreme2damax posted : I'm still experiencing major lag and lag spikes. I was just playing my game online and a huge lag spike completely froze me for around a minute or two.

Seriously Verizon, you need to look into this and fix your shoddy network, it's been a damn month already with no resolution.

Re: [Northeast] High pings / bad routing...

Sat, 09 Feb 2013 17:48:44 EDT

jk111 posted : 5:47 PM today, same issues. Here's a traceroute to google

Re: [Northeast] High pings / bad routing...

Fri, 08 Feb 2013 22:19:32 EDT

Xtreme2damax posted : Really slow tonight. Using Google public dns helps somewhat but still is slow overall. Online gaming, streaming video out of the question for tonight.

Re: [Northeast] High pings / bad routing...

Fri, 08 Feb 2013 21:49:20 EDT

Smith6612 posted : Is the routing the exact same to the dot? If your IP changed you're likely going down different circuits/ports while going through essentially the same route. Try looking at the beginning of the names in the traces, they sometimes clue into this.

Also, might want to consider checking reverse traceroutes/pings to see what the return path is like too.

Re: [Northeast] High pings / bad routing...

Fri, 08 Feb 2013 21:46:35 EDT

RolteC posted : I just changed IP's and instantly both ways to opt online and light path, my ping went from 90's to high 20's.

Same routing.

What the hell?

Re: [Northeast] High pings / bad routing...

Fri, 08 Feb 2013 21:43:47 EDT

Smith6612 posted : That is a pretty awful smokeping to Optimum Lightpath.

I'm still waiting to hear what's going on. It seems like no one I've asked has a clue as to why or what is doing this.

Re: [Northeast] High pings / bad routing...

Fri, 08 Feb 2013 19:10:24 EDT

RolteC posted : All different types of networks. Congestion at different levels at almost all the same time spread across almost all of Verizon, internal and their peers.

How much worse can it get?

Re: [Northeast] High pings / bad routing...

Fri, 08 Feb 2013 19:05:09 EDT

RolteC posted : Oh yeah, its bad tonight, and going to get worse with EVERYONE being on the internet. Most likely the same deal all day tomorrow.

Its not just inside Verizon's network, its also their routers connecting to other locations. Especially Alter.net which is their main provider for serving their network.

The trace route is to a friend just across the Hudson. Double the normal ping, speeds also nothing between us. So what is the excuse here??????????

Tracing route to pool-108-50-226-22.nwrknj.fios.verizon.net [108.50.226.22]over a maximum of 30 hops:   1    <1 ms    <1 ms    <1 ms  [192.168.1.1]  2     3 ms     1 ms     1 ms  L.NYCMNY-VFTTP-.verizon-gni.net [71]  3    11 ms     9 ms    11 ms  G0-1-1-3.NYCMNY-LCR-22.verizon-gni.net [130.81.188.72]  4     7 ms     6 ms     5 ms  so-5-0-0-0.NY5030-BB-RTR1.verizon-gni.net [130.81.22.18]  5    43 ms    22 ms    14 ms  xe-3-0-6-0.NWRK-BB-RTR1.verizon-gni.net [130.81.23.187]  6    27 ms    18 ms    21 ms  B100.NWRKNJ-LCR-21.verizon-gni.net [130.81.209.155]  7     *        *        *     Request timed out.  8    32 ms    24 ms    31 ms  pool-108-50-226-.nwrknj.fios.verizon.net [108.50.226.] Trace complete.

Re: [Northeast] High pings / bad routing...

Fri, 08 Feb 2013 18:29:55 EDT

Xtreme2damax posted : Can't even load MyVerizon to pay my bill. Of course they don't care and won't hesitate to shut my service off if I can't pay my bill even if it's the fault of their network preventing me from doing so.

Re: [Northeast] High pings / bad routing...

Fri, 08 Feb 2013 18:26:03 EDT

Xtreme2damax posted : Same bull**** again tonight. High latency and slow browsing around 6PM instead of the usual 8PM it has been the past week.

Re: [Northeast] High pings / bad routing...

Fri, 08 Feb 2013 02:22:08 EDT

jk111 posted : I tweeted to Verizon support tonight with links to this thread and one on Verizon.com forums. I will continue to do so every day until this issue is fixed. Worth a shot I guess....

Re: [Northeast] High pings / bad routing...

Thu, 07 Feb 2013 20:14:37 EDT

Xtreme2damax posted : Like clockwork, after 8PM every night now. Talked to the tech today and he mentioned something about there being a fire somewhere and due to that customers were assigned another route, overloading whatever router/gateway everyone was switched to.

Re: [Northeast] High pings / bad routing...

Wed, 06 Feb 2013 20:24:40 EDT

Xtreme2damax posted : For some reason, the last two days have been fine during the day. Suddenly after 8PM ping spikes up like everyone decides, "Hey let's all go online now", either that or Verizon's network is just derpy.

I wouldn't mind if the spikes were mild such as spikes up to 10ms - 15ms but it is spiking from sub 20ms ping up to 80ms+.

Re: [Northeast] High pings / bad routing...

Wed, 06 Feb 2013 11:29:38 EDT

zippoboy7 posted : Just figured I would chime in, I am in Maryland and thus far seem to be escaping theses issues. One thing to note, the drop off for a few hours last night had nothing to do with Verizon, the switch hooked to my server decided to lock up and stop processing traffic on my load balanced nics taking down all my virtual servers for a few hours.

In a few days I will post updated charts, I just added the ones that only go for 30 hours 3 days ago so the 10 day charts are mostly worthless on those so far.

ISOC Workshop Resource Centre (Eugene, Oregon, USA)
Indiana University
heise.de
l.root-servers.net

Re: [Northeast] High pings / bad routing...

Wed, 06 Feb 2013 11:01:48 EDT

sydnius posted : Delaware reporting in, see this issue too. It comes and goes with the hours, varies from the normal ~20ms up to ~120ms.
Same routes, distinctly different pings over hops 5-6 depending on the mood. Sure hope someone fixes it soon, scout is hard to play with 120ms ping.

~120ms route:

traceroute to 208.78.165.46 (208.78.165.46), 64 hops max, 72 byte packets
 1  192.168.3.1 (192.168.3.1)  0.619 ms  0.366 ms  0.430 ms
 2  l100.phlapa-vfttp-90.verizon-gni.net (71.244.110.1)  8.243 ms  9.050 ms  7.227 ms
 3  g0-10-4-4.phlapa-lcr-22.verizon-gni.net (130.81.188.186)  12.755 ms  11.333 ms  13.222 ms
 4  so-3-1-0-0.phil-bb-rtr2.verizon-gni.net (130.81.22.60)  11.971 ms  12.120 ms  12.737 ms
 5  0.xe-4-1-0.br3.iad8.alter.net (152.63.33.21)  19.968 ms  17.358 ms  19.980 ms
 6  63-235-40-49.dia.static.qwest.net (63.235.40.49)  131.893 ms  104.213 ms  103.161 ms
 7  stn3-edge-01.inet.qwest.net (67.14.28.50)  112.676 ms  114.603 ms  115.393 ms
 8  65.126.30.62 (65.126.30.62)  104.660 ms  106.904 ms  109.651 ms
 9  208.78.167.3 (208.78.167.3)  100.145 ms  98.196 ms  100.175 ms

~20ms route:

traceroute to 208.78.165.46 (208.78.165.46), 64 hops max, 72 byte packets
 1  192.168.3.1 (192.168.3.1)  0.761 ms  0.321 ms  0.511 ms
 2  l100.phlapa-vfttp-90.verizon-gni.net (71.244.110.1)  6.489 ms  8.003 ms  7.007 ms
 3  g0-10-4-4.phlapa-lcr-22.verizon-gni.net (130.81.188.186)  12.959 ms  11.354 ms  13.226 ms
 4  so-3-1-0-0.phil-bb-rtr2.verizon-gni.net (130.81.22.60)  11.716 ms  12.681 ms  12.229 ms
 5  0.xe-4-1-0.br3.iad8.alter.net (152.63.33.21)  20.263 ms  19.627 ms  19.989 ms
 6  63-235-40-49.dia.static.qwest.net (63.235.40.49)  19.995 ms  19.632 ms  19.962 ms
 7  stn3-edge-01.inet.qwest.net (67.14.28.50)  19.975 ms  19.625 ms  19.987 ms
 8  65.126.30.62 (65.126.30.62)  42.713 ms  19.588 ms  20.213 ms
 9  208.78.167.3 (208.78.167.3)  19.955 ms  21.647 ms  19.999 ms

Re: [Northeast] High pings / bad routing...

Tue, 05 Feb 2013 21:21:56 EDT

Xtreme2damax posted : Anyone got anywhere with Verizon yet? Still no improvement on my end, severe lag spikes everyday later in the day. Even when my ping is lower I am lagging in the online game I play.

Re: [Northeast] High pings / bad routing...

Mon, 04 Feb 2013 21:24:55 EDT

Xtreme2damax posted : Well I have an installation appointment for TV this Thursday. I will be telling them to relay the message to Verizon to fix their damn network.

Re: [Northeast] High pings / bad routing...

Mon, 04 Feb 2013 20:14:35 EDT

Xtreme2damax posted : Well that's a big fat nope. Spikes around 7PM - 8PM EST. >_<

Re: [Northeast] High pings / bad routing...

Mon, 04 Feb 2013 17:53:46 EDT

Xtreme2damax posted : Maybe Verizon fixed the issue? Seeing low ping all around and no spikes today as of yet.

Re: [Northeast] High pings / bad routing...

Sat, 02 Feb 2013 20:53:25 EDT

Xtreme2damax posted : That's ridiculous. They really need to look into it or they risk losing customers. The proof is there that it's within the Verizon network, either some router or poor routing decisions.

Any way to get them to take their heads out from their behinds to have someone that can do something look into it and resolve the issue? For an issue this widespread it's just bad business for them to continue ignoring complaints. I wouldn't mind so much if the spikes were short lived and were mild fluctuations but when it's spiking up to 80ms+ it is plainly unacceptable.

I'm not sure what good the direct sections are if they won't respond to such issues. I just don't fancy being kept on the phone for over an hour, run through the motions, a tech to come out only for them to realize it's not an issue on my end and deny any sort of responsibility with their network. When I first signed up for Fios I was on the phone for over an hour over something ridiculous, an incompetent representative kept claiming I couldn't sign up for internet service without bundling voice due to some unheard of law (to me) in New York. Never again.
--
My Website: »www.xtemu.com
My Speedtest: »www.speedtest.net/result/1218984197.png

Re: [Northeast] High pings / bad routing...

Sat, 02 Feb 2013 20:30:07 EDT

RolteC posted : I am pretty sure that it is safe to say: no one from Verizon will agree to bad routing within Verizon nor will anyone every respond to those types of posts in the direct forum. I haven't seen that before, so it probably won't change. I also do not expect a direct response to anything you ask of any current Verizon employee. Its not allowed/they are not going to risk their jobs.

But to show something weird. I am seeing horrific ping times to almost everything - but NOT all at the exact same times tonight.

Here is a tracert to myself from a road runner connection, and at the exact same time, a tracert back to the road runner connection. Very weird results:

Tracing route to cpe-142-255.nyc.res.rr.com [142.255.]over a maximum of 30 hops:   1    <1 ms    <1 ms    <1 ms  [192.168.1.1]  2     4 ms     1 ms     1 ms  L.NYCMNY-VFTTP.verizon-gni.net [71  3     8 ms     8 ms     7 ms  G0-1-1-3.NYCMNY-LCR-22.verizon-gni.net [130.81.188.72]  4     5 ms     6 ms     6 ms  so-6-1-0-0.NY5030-BB-RTR2.verizon-gni.net [130.81.151.224]  5     6 ms     6 ms     7 ms  0.xe-9-1-0.BR2.NYC4.ALTER.NET [152.63.23.141]  6     *        *        *     Request timed out.  7     7 ms     *        *     Vlan2135.icore2.NTO-NewYork.as6453.net [216.6.81.37]  8    92 ms    95 ms    99 ms  Vlan576.icore2.NTO-NewYork.as6453.net [209.58.26.34]  9    33 ms    30 ms    31 ms  107.14.19.146 10    20 ms    23 ms    22 ms  107.14.19.23 11    45 ms    47 ms     *     bun6-nyquny91-rtr001.nyc.rr.com [24.29.148.253] 12   104 ms   103 ms   106 ms  bun110.nycmnyl-rtr01.nyc.rr.com [184.152.112.76] 13   120 ms   115 ms     *     tenge18-10-nycmnyl-c404.nyc.rr.com [24.168.134.222] 14   106 ms   107 ms   120 ms  cpe-142-255-.nyc.res.rr.com [142.255.] Trace complete.Tracing route to  [100.]over a maximum of 30 hops:   1     1 ms     1 ms     1 ms  Router [192.168.1.1]  2    34 ms    27 ms    28 ms  cpe-142-255-0-1.nyc.res.rr.com [142.255.0.1]  3    29 ms    12 ms    11 ms  tenge-0-2-0-3-nycmnyl-rtr2.nyc.rr.com [24.168.134.221]  4    16 ms    15 ms    15 ms  bun110.nycmnytg-rtr001.nyc.rr.com [184.152.112.129]  5     *       17 ms    16 ms  bun6-nycmnytg-rtr002.nyc.rr.com [24.29.148.250]  6    21 ms    13 ms    15 ms  ae-4-0.cr0.nyc30.tbone.rr.com [66.109.6.78]  7    12 ms    15 ms    11 ms  107.14.19.153  8    22 ms    22 ms    19 ms  216.55.0.65  9    32 ms    23 ms    31 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9] 10    31 ms    23 ms    36 ms  vb1010.rar3.nyc-ny.us.xo.net [216.156.0.17] 11    18 ms    21 ms    35 ms  207.88.14.178.ptr.us.xo.net [207.88.14.178] 12    34 ms    34 ms    34 ms  206.111.13.126.ptr.us.xo.net [206.111.13.126] 13     *      110 ms   113 ms  0.xe-1-1-2.NY325-BB-RTR2.verizon-gni.NET [152.63.20.214] 14     *        *        *     Request timed out. 15   116 ms   136 ms   123 ms  pool-100nycmny.fios.verizon.net [100] Trace complete.

Re: [Northeast] High pings / bad routing...

Sat, 02 Feb 2013 20:02:16 EDT

Xtreme2damax posted : Edit: Nevermind. Misread the trace route. It is indeed still spiking within the Verizon network. :/

Not spiking as bad as before though. Ping will spike up briefly for a bit and go back down. This still needs to be sorted out though as I should be seeing much lower ping to local servers.

Re: [Northeast] High pings / bad routing...

Sat, 02 Feb 2013 19:53:25 EDT

Xtreme2damax posted : It's back again. Seriously Verizon, fix your crappy routing/routers.