dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
2362
share rss forum feed

serge87

join:2009-11-29
Reviews:
·Verizon FiOS
reply to okcookie

Re: [Northeast] Higher pings tonight?

said by okcookie:

My question is: will switching my ISP to, for example, Comcast, solve this problem? Is the problem related to Verizon's infrastructure, or is it a much larger problem with the Internet?

Give it another month or two. Hurricane Sandy($71 billion worth of damage) may have had something to do with wrecking a lot of routing paths and the remaining ones are being worked double.

okcookie

join:2012-11-26
Medford, NJ

said by serge87:

said by okcookie:

My question is: will switching my ISP to, for example, Comcast, solve this problem? Is the problem related to Verizon's infrastructure, or is it a much larger problem with the Internet?

Give it another month or two. Hurricane Sandy($71 billion worth of damage) may have had something to do with wrecking a lot of routing paths and the remaining ones are being worked double.

Interestingly, the slow speeds and high latency only began within the past 3 days. This leads me to believe that the problems are not related to hurricane Sandy, as the storm occurred some time ago and I had no internet speed problems immediately after it.

The truth is, I really don't want to wait another month. I'm open to waiting another week or so, but honestly during that time I will likely contact Comcast to arrange for the install.

okcookie

join:2012-11-26
Medford, NJ
reply to chrisb3127

I had a followup call with a Verizon tech today. The replacement router arrived today, and I installed it. My download speeds remain incredibly slow. I've even had download speeds below .75 mbps when testing using a server out of state. The tech brought a "network tech" into the call, and this tech remotely reset my ONT. Nothing. At this point, a field tech is scheduled to come out on Thursday to test the ONT. The problem is, I believe firmly that this is a problem with the larger infrastructure. If the tech visit on Thursday doesn't fix the problem, I'm planning to switch to a different ISP.


chrisb3127

join:2006-03-01
Manville, NJ
reply to chrisb3127

Higher pings are here again tonight. Seems like it only occurs from the afternoons to about midnight or so. I think the issue is internal to VZ's routers on their end, not the end user. They somehow need to address this, instead of blaming our equipment or something else.



RolteC
0h

join:2001-05-20
Fresh Meadows, NY
kudos:1
reply to okcookie

said by okcookie:

I had a followup call with a Verizon tech today. The replacement router arrived today, and I installed it. My download speeds remain incredibly slow. I've even had download speeds below .75 mbps when testing using a server out of state. The tech brought a "network tech" into the call, and this tech remotely reset my ONT. Nothing. At this point, a field tech is scheduled to come out on Thursday to test the ONT. The problem is, I believe firmly that this is a problem with the larger infrastructure. If the tech visit on Thursday doesn't fix the problem, I'm planning to switch to a different ISP.

It is my honest opinion that you are wasting Verizon's time and yours. Post some tracerts. I am 99% sure that the issue you are seeing, I am, as well as thousands of others. It is NOT an issue in the home.


HardwareGeek

join:2003-11-15
Brooklyn, NY
reply to chrisb3127

I had issues earlier but it seems to have been resolved


okcookie

join:2012-11-26
Medford, NJ
reply to RolteC

said by RolteC:

said by okcookie:

I had a followup call with a Verizon tech today. The replacement router arrived today, and I installed it. My download speeds remain incredibly slow. I've even had download speeds below .75 mbps when testing using a server out of state. The tech brought a "network tech" into the call, and this tech remotely reset my ONT. Nothing. At this point, a field tech is scheduled to come out on Thursday to test the ONT. The problem is, I believe firmly that this is a problem with the larger infrastructure. If the tech visit on Thursday doesn't fix the problem, I'm planning to switch to a different ISP.

It is my honest opinion that you are wasting Verizon's time and yours. Post some tracerts. I am 99% sure that the issue you are seeing, I am, as well as thousands of others. It is NOT an issue in the home.

Please explain to me in what way I am wasting Verizon's time? I had no choice but to accept and install the replacement router, as the tech I spoke with essentially forced me to try it. This is protocol. As for the tech that will be coming to my home to test the ONT, this is also protocol. I am fully aware that the issue is not in the home. If I had a choice, I would escalate this issue beyond a field tech coming to my home to test the ONT. I don't want to miss 3 hours of work so they can test equipment that I know is functional. The problem is not with me, but is rather with Verizon. The fact is, if we wish to escalate this issue, they will force us to jump through hoops as they follow protocol. I explicitly asked the tech if there was any way this matter could be escalated, to specifically avoid a field tech coming to my home when I am fully aware that this is unnecessary. I was told that they must follow protocol. As to trace routes, they are coming next.

I thank you for pacing judgment on me as I attempt to raise this issue to Verizon and I bid you good day.


RolteC
0h

join:2001-05-20
Fresh Meadows, NY
kudos:1
reply to chrisb3127

Click for full size
FiOS 150M to OpenDNS
Click for full size
FiOS 150M to Optonline
Here is a more detailed view from my connection to OpenDNS and to a friends server. My line, 150/65, was not in much use at all during this. This goes to show everyone what is actually happening between the Verizon ( I believe Alter is theirs as well) and Level 3. Unfortunately, almost everything is being shoved through them. This being said, it obviously affects those who game and it affects the speeds of those with the higher tier packages.

As for this happening ever since Sandy, I would say yes. Although I was away during that time, I RDP'd every night and noticed the ping/slowdowns. It just seems to be getting worse every day!

My thoughts do go out to everyone affected!

codydog

join:2001-11-29
Newport, RI
Reviews:
·Verizon FiOS

My speeds are ok, within acceptable boundries, but ping time is now higher than Cox. Verizon says its not them. Not sure why my speeds and ping times fluctuate on fios even at odd hours. Verizons ping times are higher than what I had with Cox.

So much for fios dominance over cable, in my opinion, of course.


okcookie

join:2012-11-26
Medford, NJ
reply to chrisb3127

Trace routes were requested by a previous poster:

2 8 ms 7 ms 9 ms L100.CMDNNJ-VFTTP-37.verizon-gni.net [173.71.94.1]
3 10 ms 9 ms 9 ms G3-0-6-337.CMDNNJ-LCR-03.verizon-gni.net [130.81.146.126]
4 15 ms 14 ms 14 ms so-7-3-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.29.36]
5 18 ms 19 ms 47 ms xe-1-0-2-0.NY5030-BB-RTR1.verizon-gni.net [130.81.23.184]
6 19 ms 19 ms 19 ms 0.ae5.BR3.NYC4.ALTER.NET [152.63.16.9]
7 68 ms 72 ms 66 ms te-7-3-0.edge2.NewYork2.level3.net [4.68.111.137]
8 75 ms 74 ms 72 ms vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
9 65 ms 64 ms 64 ms ae-4-4.ebr1.NewYork1.Level3.net [4.69.141.17]
10 78 ms 74 ms 74 ms ae-71-71.csw2.NewYork1.Level3.net [4.69.134.70]
11 21 ms 19 ms 19 ms ae-24-70.car4.NewYork1.Level3.net [4.69.155.70]
12 64 ms 64 ms 61 ms SPLICE-COMM.car4.NewYork1.Level3.net [4.53.94.28]
13 74 ms 74 ms 75 ms resolver1.opendns.com [208.67.222.222]

Trace complete.

---------------------

Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:

2 6 ms 7 ms 7 ms L100.CMDNNJ-VFTTP-37.verizon-gni.net [173.71.94.1]
3 8 ms 9 ms 9 ms G3-0-6-337.CMDNNJ-LCR-03.verizon-gni.net [130.81.146.126]
4 15 ms 14 ms 15 ms so-7-3-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.29.36]
5 16 ms 19 ms 19 ms xe-1-0-2-0.NY5030-BB-RTR1.verizon-gni.net [130.81.23.184]
6 19 ms 19 ms 19 ms 0.ae5.BR3.NYC4.ALTER.NET [152.63.16.9]
7 51 ms 51 ms 54 ms te-7-3-0.edge2.NewYork2.level3.net [4.68.111.137]
8 75 ms 72 ms 73 ms vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
9 65 ms 64 ms 64 ms ae-4-4.ebr1.NewYork1.Level3.net [4.69.141.17]
10 68 ms 74 ms 74 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66]
11 18 ms 19 ms 19 ms ae-24-70.car4.NewYork1.Level3.net [4.69.155.70]
12 50 ms 56 ms 54 ms SPLICE-COMM.car4.NewYork1.Level3.net [4.53.94.218]
13 76 ms 77 ms 76 ms resolver1.opendns.com [208.67.222.222]

Trace complete.

------------------------



-----------------------

My download speeds appear to depend on the server I use to test.



However, I cannot watch streaming videos or play online games due to very high latency spikes; I've had in-game latency spikes of 1800ms and higher.


serge87

join:2009-11-29
Reviews:
·Verizon FiOS

Looks like all the latency starts at Level3. I noticed months ago while using 4.2.2.x Level3 DNS servers that trace routes were taking too many high latency hops to reach their destination. After changing DNS servers I see this problem has finally caught up to the peering issues between VZ and Level3 regardless of which DNS server you use.



JeepMatt
C'mon the U
Premium
join:2001-12-28
Wilmington, DE
kudos:3
Reviews:
·Verizon FiOS
·Comcast

It's definitely a capacity issue between the handoff of Alter and L3. This used to happen quite often when I first got FIOS internet back in 2006.

Back then, I actually had a contact with Alter - she was unreal. I'd send her trace routes, she'd email them to the engineers, and usually in 3 days tops they'd have it rectified.

You guys are seeing the same thing. This does need to be escalated up through Verizon.
--
"ONE team - ONE city - ONE dream!!"


ScrawnyB

join:2004-05-18
Carlisle, PA
kudos:1
reply to chrisb3127

Here's a sample of how this escalates each evening...

5:15pm

  1    <1 ms    <1 ms    <1 ms  FIOSWAN [10.0.0.1]
  2     2 ms     2 ms     2 ms  L100.HRBGPA-VFTTP-12.verizon-gni.net [98.117.0.1]
  3     3 ms     3 ms     3 ms  G9-0-4-112.HRBGPA-LCR-01.verizon-gni.net [130.81.137.120]
  4    15 ms    15 ms    15 ms  P12-0-0.HRBGPA-LCR-02.verizon-gni.net [130.81.27.185]
  5    15 ms    15 ms    15 ms  so-12-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.28.254]
  6    17 ms    16 ms    17 ms  0.ae2.BR2.IAD8.ALTER.NET [152.63.34.73]
  7    16 ms    16 ms    16 ms  ae16.edge1.washingtondc12.level3.net [4.68.62.133]
  8    17 ms    17 ms    17 ms  d.resolvers.level3.net [4.2.2.4]
 

7:00pm
  1    <1 ms    <1 ms    <1 ms  FIOSWAN [10.0.0.1]
  2     2 ms     1 ms     2 ms  L100.HRBGPA-VFTTP-12.verizon-gni.net [98.117.0.1]
  3     3 ms     3 ms     3 ms  G9-0-4-112.HRBGPA-LCR-01.verizon-gni.net [130.81.137.120]
  4    15 ms    16 ms    15 ms  P12-0-0.HRBGPA-LCR-02.verizon-gni.net [130.81.27.185]
  5    16 ms    15 ms    16 ms  so-12-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.28.254]
  6    17 ms    16 ms    17 ms  0.ae2.BR2.IAD8.ALTER.NET [152.63.34.73]
  7    61 ms    61 ms    63 ms  ae16.edge1.washingtondc12.level3.net [4.68.62.133]
  8    64 ms    63 ms    63 ms  d.resolvers.level3.net [4.2.2.4]
 

8:15pm
  1    <1 ms    <1 ms    <1 ms  FIOSWAN [10.0.0.1]
  2     2 ms     1 ms     2 ms  L100.HRBGPA-VFTTP-12.verizon-gni.net [98.117.0.1]
  3     3 ms     3 ms     3 ms  G9-0-4-112.HRBGPA-LCR-01.verizon-gni.net [130.81.137.120]
  4    15 ms    15 ms    16 ms  P12-0-0.HRBGPA-LCR-02.verizon-gni.net [130.81.27.185]
  5    15 ms    16 ms    15 ms  so-12-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.28.254]
  6    16 ms    17 ms    17 ms  0.ae2.BR2.IAD8.ALTER.NET [152.63.34.73]
  7    66 ms    66 ms    68 ms  ae17.edge1.washingtondc12.level3.net [4.68.62.137]
  8     *       78 ms    79 ms  d.resolvers.level3.net [4.2.2.4]
 

serge87

join:2009-11-29
Reviews:
·Verizon FiOS
reply to JeepMatt

said by JeepMatt:

Back then, I actually had a contact with Alter - she was unreal. I'd send her trace routes, she'd email them to the engineers, and usually in 3 days tops they'd have it rectified.

You guys are seeing the same thing. This does need to be escalated up through Verizon.

Oh to have a contact like that, no 120-step automated phone process and verifying to tier 1 support that the router is in fact plugged in


RolteC
0h

join:2001-05-20
Fresh Meadows, NY
kudos:1

Click for full size
Another night...
Definitely has to be a capacity issue.

Also, I am pretty sure Verizon is aware of this. How could they not run MRTG graphs on their equipment to monitor usage? For that matter, I am sure their employees who monitor these forums and run the Direct portion of it have also read these complaints.

But I guarantee you all, none of them will chime in with this issue or give a resolution to it.

okcookie

join:2012-11-26
Medford, NJ
reply to chrisb3127

Has the issue been resolved? My speeds are back to normal and my latency is acceptable.


chrisb3127

join:2006-03-01
Manville, NJ
reply to chrisb3127

Pings are improved..hopefully it stays! As of 5pm my ping to the co-lo in Philly is 8-11ms vs in the 30+ ms a few days ago. It's going to NY Alter -- NY L3 -- PHL L3. What's interesting is sometimes it'll go through Qwest instead of L3, which has less hops.


okcookie

join:2012-11-26
Medford, NJ

Does Comcast somehow go directly to Level 3? Forgive my ignorance, but my understanding is that with Verizon the signal has to hop through Alter.net before reaching Level 3, whereas with Comcast the signal goes directly from their backbone to Level 3? I ask because I have a Comcast install scheduled, but with the speeds restored I'm considering cancelling and staying with VZ.



RolteC
0h

join:2001-05-20
Fresh Meadows, NY
kudos:1
reply to chrisb3127

Thats good. But not yet. Post some tracerts along with your finds.

 
 2     3 ms     3 ms     2 ms  
 3     3 ms     3 ms     2 ms  G0-1-1-3.NYCMNY-LCR-21.verizon-gni.net [130.81.188.74]
 4     4 ms     3 ms     4 ms  130.81.151.228
 5     5 ms     4 ms     4 ms  0.xe-2-0-8.XT2.NYC4.ALTER.NET [152.63.6.253]
 6     3 ms     5 ms     3 ms  0.ae4.BR2.NYC4.ALTER.NET [152.63.3.118]
 7    29 ms    26 ms    29 ms  te-7-3-0.edge2.NewYork2.level3.net [4.68.111.137]
 8    39 ms    28 ms    27 ms  vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
 9    27 ms    28 ms    32 ms  ae-6-6.ebr2.NewYork1.Level3.net [4.69.141.21]
10    27 ms    28 ms    27 ms  ae-72-72.csw2.NewYork1.Level3.net [4.69.148.38]
11    30 ms    29 ms    27 ms  ae-44-90.car4.NewYork1.Level3.net [4.69.155.198]
12    31 ms    30 ms    30 ms  SPLICE-COMM.car4.NewYork1.Level3.net [4.53.94.218]
13    30 ms    29 ms    30 ms  resolver3.opendns.com [208.67.222.220]
 

By the way, according to my very detailed graphs I have running, the problem seems to start around 7-8pm. So lets see what happens then!

okcookie

join:2012-11-26
Medford, NJ
reply to chrisb3127

Traceroute as of 7:43 EST:

Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:

2 8 ms 6 ms 7 ms L100.CMDNNJ-VFTTP-37.verizon-gni.net [173.71.94.1]
3 6 ms 7 ms 6 ms G3-0-6-337.CMDNNJ-LCR-03.verizon-gni.net [130.81.146.126]
4 15 ms 14 ms 14 ms so-7-3-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.29.36]
5 17 ms 19 ms 19 ms xe-1-0-2-0.NY5030-BB-RTR1.verizon-gni.net [130.81.23.184]
6 18 ms 19 ms 19 ms 0.ae5.BR3.NYC4.ALTER.NET [152.63.16.9]
7 28 ms 27 ms 26 ms te-7-3-0.edge2.NewYork2.level3.net [4.68.111.137]
8 40 ms 29 ms 31 ms vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
9 33 ms 29 ms 29 ms ae-4-4.ebr1.NewYork1.Level3.net [4.69.141.17]
10 34 ms 39 ms 34 ms ae-81-81.csw3.NewYork1.Level3.net [4.69.134.74]
11 20 ms 19 ms 19 ms ae-34-80.car4.NewYork1.Level3.net [4.69.155.134]
12 32 ms 31 ms 32 ms SPLICE-COMM.car4.NewYork1.Level3.net [4.53.94.218]
13 27 ms 27 ms 26 ms resolver1.opendns.com [208.67.222.222]

Trace complete.

What do you guys think? How are these numbers? In terms of user experience, my speeds are definitely better than they have been in the past 6 days.

I judge my speeds primary based on experience in-game online gaming in Diablo 3 (my current obsession). Over the past 6 days, playing was virtually impossible. The game displays latency, and I experienced spikes of 1800ms and higher. I have been running at about 100ms consistently since 4:30 PM today; sometimes it's been lower (about 90ms) sometimes higher (115ms).

Anyway, it looks like they found and fixed the problem. I will keep my eye on it over the next couple days, and continue to post trace routes.


okcookie

join:2012-11-26
Medford, NJ
reply to chrisb3127

And here we go again.

Trace route as of 10:13 PM:

Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:

2 6 ms 6 ms 7 ms L100.CMDNNJ-VFTTP-37.verizon-gni.net [173.71.94.1]
3 11 ms 7 ms 7 ms G3-0-6-337.CMDNNJ-LCR-03.verizon-gni.net [130.81.146.126]
4 15 ms 15 ms 14 ms so-7-3-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.29.36]
5 22 ms 18 ms 19 ms xe-1-0-2-0.NY5030-BB-RTR1.verizon-gni.net [130.81.23.184]
6 18 ms 19 ms 19 ms 0.ae5.BR3.NYC4.ALTER.NET [152.63.16.9]
7 103 ms 131 ms 107 ms te-7-3-0.edge2.NewYork2.level3.net [4.68.111.137]
8 101 ms 99 ms 102 ms vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
9 99 ms 99 ms 101 ms ae-4-4.ebr1.NewYork1.Level3.net [4.69.141.17]
10 105 ms 103 ms 117 ms ae-81-81.csw3.NewYork1.Level3.net [4.69.134.74]
11 20 ms 19 ms 19 ms ae-34-80.car4.NewYork1.Level3.net [4.69.155.134]
12 104 ms 101 ms 102 ms SPLICE-COMM.car4.NewYork1.Level3.net [4.53.94.218]
13 104 ms 101 ms 104 ms resolver1.opendns.com [208.67.222.222]

Trace complete.


okcookie

join:2012-11-26
Medford, NJ
reply to chrisb3127

Despite better user experience, something's still not right:



Speed tests using Verizon's speed tester (when I select out-of-state servers in neighboring states - i.e Maryland, DC) yield download speeds of about 1mbps.

Something is obviously still wrong.



RolteC
0h

join:2001-05-20
Fresh Meadows, NY
kudos:1

1 edit
reply to chrisb3127

Wow....

Downloading at 300 KB second. Started a few download at the same time, got to about 60Mbit/sec but with 400ms pings to my FIRST hop.

What in the world is going on tonight?

Tracing route to b.resolvers.Level3.net [4.2.2.2]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  
  2     2 ms     7 ms     5 ms  
  3     9 ms    15 ms     6 ms  G0-1-1-3.NYCMNY-LCR-22.verizon-gni.net [130.81.188.72]
  4    10 ms     9 ms     8 ms  so-5-0-0-0.NY5030-BB-RTR1.verizon-gni.net [130.81.22.18]
  5    12 ms    10 ms    16 ms  0.ae5.BR3.NYC4.ALTER.NET [152.63.16.9]
  6    77 ms     *       97 ms  te-7-3-0.edge2.NewYork2.level3.net [4.68.111.137]
  7    82 ms    98 ms    99 ms  vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
  8    81 ms    72 ms    75 ms  ae-4-4.ebr1.NewYork1.Level3.net [4.69.141.17]
  9   108 ms     *      108 ms  ae-71-71.csw2.NewYork1.Level3.net [4.69.134.70]
 10    98 ms    80 ms    80 ms  ae-2-70.edge2.NewYork1.Level3.net [4.69.155.80]
 11   104 ms     *      100 ms  b.resolvers.Level3.net [4.2.2.2]
 
Trace complete.
 

Downloading multiple files - hit 40-60Mbit/sec out of my 150..
Tracing route to b.resolvers.Level3.net [4.2.2.2]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  
  2     *      338 ms   355 ms  
  3   370 ms     *      406 ms  G0-1-1-3.NYCMNY-LCR-22.verizon-gni.net [130.81.188.72]
  4     *      316 ms   294 ms  so-5-0-0-0.NY5030-BB-RTR1.verizon-gni.net [130.81.22.18]
  5   256 ms     *      297 ms  0.ae5.BR3.NYC4.ALTER.NET [152.63.16.9]
  6     *      399 ms     *     te-7-3-0.edge2.NewYork2.level3.net [4.68.111.137]
  7     *      459 ms     *     vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
  8   425 ms     *      412 ms  ae-4-4.ebr1.NewYork1.Level3.net [4.69.141.17]
  9     *        *        *     Request timed out.
 10     *      464 ms     *     ae-2-70.edge2.NewYork1.Level3.net [4.69.155.80]
 11     *      329 ms     *     b.resolvers.Level3.net [4.2.2.2]
 12   344 ms   439 ms   405 ms  b.resolvers.Level3.net [4.2.2.2]
 
Trace complete.
 

mario44222

join:2003-11-22
Cliffside Park, NJ

Connection is going very slow here too. I think it started after 9:30 pm.


serge87

join:2009-11-29
reply to chrisb3127

Are any of you experiencing crappy latency using Level 3 DNS(4.2.2.x) or OpenDNS(which primarily uses Level3)? Can you try 151.202.0.84 or 141.155.0.68?


mario44222

join:2003-11-22
Cliffside Park, NJ
reply to chrisb3127

Tracing route to b.resolvers.Level3.net [4.2.2.2]
over a maximum of 30 hops:

1 1 ms 3 ms 3 ms static-71-187-25-126.nwrknj.fios.verizon.net [71
.187.25.126]
2 6 ms 3 ms 3 ms L100.NWRKNJ-VFTTP-78.verizon-gni.net [96.242.183
.1]
3 6 ms 7 ms 7 ms G0-3-3-4.NWRKNJ-LCR-22.verizon-gni.net [130.81.1
46.70]
4 27 ms 55 ms 28 ms ae0-0.NWRK-BB-RTR2.verizon-gni.net [130.81.209.1
62]
5 17 ms 26 ms 7 ms so-3-0-3-0.NY5030-BB-RTR2.verizon-gni.net [130.8
1.17.14]
6 10 ms 7 ms 8 ms 0.xe-3-1-0.BR3.NYC4.ALTER.NET [152.63.2.81]
7 14 ms 15 ms 12 ms te-7-3-0.edge2.NewYork2.level3.net [4.68.111.137
]
8 17 ms 9 ms 14 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
9 17 ms 16 ms 16 ms ae-6-6.ebr2.NewYork1.Level3.net [4.69.141.21]
10 25 ms 24 ms 24 ms ae-82-82.csw3.NewYork1.Level3.net [4.69.148.42]

11 30 ms 30 ms 33 ms ae-3-80.edge2.NewYork1.Level3.net [4.69.155.144]

12 19 ms 20 ms 20 ms b.resolvers.Level3.net [4.2.2.2]

4.2.2.2 looks ok, but it seems that my upload is sucking right now. Only get 19.375Mbps