Gaming Latency - Questions for Black Ops 2

In_Domine · ‎07-29-2013

First, I'd like to say that I am a resident of Buffalo, NY. Prior to the new MI424WR-GEN3I firmware, 40.20.7, online gaming, specifically Black Ops 2, was unbearable. Now, with the new firmware, there is a noticeable difference in the connection. However, the latency for gaming in general is still incredibly sluggish and I constantly find myself looking like I have the reaction time of a snail and barely get off 2-3 shots in the killcams - this is especially frustrating when I could've sworn I emptied half my clip into that very same person. This issue is not "once in a blue moon". It is literally plagueing my online gaming experience and FPS games are near impossible to play. Customer service never has any answers, and I'm constantly told to just reset my router and the problem should be fixed.

I've been sent a new router twice, I've changed out the coax cables that were poor quality, and I have even tried to run a 3rd party router on a LAN-LAN with the Actiontec (I would use my own, but I subscribe to FiOS TV). Part of me wants to blame the high latency on the coax lines and FiOS TV, but a friend of mine has the exact same plan in NYC and has never seen a ping above 3ms. This surprised me, since I can't speedtest below 30ms ping... ever.

Any ideas on why I struggle with the ping on FiOS? I know a lot of you might not think 30-60ms ping is a lot, but I've played on connections that have near 0 pings and the connection was absolutely stunning. In no way am I trying to complain about it, if there isn't a way to "fix" it, then I'll have to make do with it and throw out FPS games, but if any help can be provided, it'd be greatly appreciated.

Speedtest, pingtest, and tracerts are below:

Toronto:

http://www.pingtest.net/result/84380146.png

http://www.pingtest.net/result/84380625.png

http://www.speedtest.net/result/2868907331.png

Buffalo:

http://www.speedtest.net/result/2868909311.png

NY:

http://www.pingtest.net/result/84380656.png

http://www.speedtest.net/result/2868910699.png

Tracerts:

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

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 5 ms 5 ms L100.BFLONY-VFTTP-17.verizon-gni.net [108.17.5.1]
3 10 ms 10 ms 7 ms G0-1-1-6.BFLONY-LCR-21.verizon-gni.net [130.81.97.246]
4 80 ms 29 ms 19 ms xe-1-1-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.209.34]
5 20 ms 21 ms 20 ms 0.xe-10-1-0.BR1.NYC1.ALTER.NET [152.63.18.225]
6 22 ms 20 ms 20 ms ae11.edge2.NewYork.Level3.net [4.68.62.41]
7 21 ms 21 ms 21 ms vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
8 22 ms 35 ms 20 ms ae-4-4.ebr1.NewYork1.Level3.net [4.69.141.17]
9 23 ms 31 ms 22 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66]
10 21 ms 21 ms 20 ms ae-1-60.edge2.NewYork1.Level3.net [4.69.155.16]
11 22 ms 21 ms 21 ms b.resolvers.Level3.net [4.2.2.2]

Trace complete.

C:\Users\The Kurtis>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 4 ms 4 ms L100.BFLONY-VFTTP-17.verizon-gni.net [108.17.5.1]
3 8 ms 7 ms 7 ms G0-1-1-6.BFLONY-LCR-21.verizon-gni.net [130.81.97.246]
4 16 ms 17 ms 22 ms xe-4-1-6-0.NWRK-BB-RTR1.verizon-gni.net [130.81.209.8]
5 20 ms 22 ms 20 ms 0.so-0-0-0.XT1.NYC4.ALTER.NET [152.63.1.41]
6 22 ms 22 ms 23 ms TenGigE0-4-0-0.GW8.NYC4.ALTER.NET [152.63.21.61]
7 20 ms 21 ms 20 ms Internet-gw.customer.alter.net [152.179.72.66]
8 19 ms 54 ms 23 ms 72.14.238.232
9 20 ms 19 ms 20 ms 72.14.236.206
10 26 ms 26 ms 26 ms 209.85.249.11
11 36 ms 35 ms 33 ms 72.14.235.10
12 33 ms 32 ms 33 ms 72.14.234.55
13 * * * Request timed out.
14 35 ms 33 ms 34 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

ibamars · ‎07-31-2013

HMMM, Im no expert by any means. I myself play FPS shooters as well. I stopped playing COD just because the peer to peer is terrible. I am a BF3 guy myself. Dedicated servers just seem better to me. Although the client side hit detection can be crazy at times.

I just did a tracert with those same DNS servers, same results as you but I am in Albany NY. I remember doing this a few weeks ago to see what DNS server would be the best. I found the 208.67.222.222 and 208.67.220.220 provided the best results for me. Im going to assume you have opened your ports and maybe done some QOS stuff? BTW, did you change the DNS servers in the router or are you still using the ones Fios provides?

I just experienced a PS3 error for the longest time which I never got with Time Warner, 80029564. Turned out I had to open ports and some advanced networking and the problem went away except for 1 dreaded game. I play on XBOX, PS3 and PC BTW. If yoo want to know my configuration settings let me know.

Scott

http://www.speedtest.net/my-result/2872122772

C:\Users\Scott>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms My IP

2     6 ms     8 ms     6 ms L100.ALBYNY-VFTTP-06.verizon-gni.net [96.236.43.
1]
3     8 ms     6 ms     6 ms G3-0-4-106.ALBYNY-LCR-01.verizon-gni.net [130.81
.177.120]
4    18 ms    19 ms    19 ms so-2-0-0-0.NY5030-BB-RTR1.verizon-gni.net [130.8
1.22.44]
5    20 ms    22 ms    21 ms 0.xe-6-1-1.XT1.NYC4.ALTER.NET [152.63.10.57]
6    21 ms    24 ms    24 ms TenGigE0-6-4-0.GW8.NYC4.ALTER.NET [152.63.21.121
]
7    33 ms    31 ms    34 ms Internet-gw.customer.alter.net [152.179.72.66]
8    18 ms    19 ms    22 ms 209.85.255.68
9    91 ms    87 ms    86 ms 209.85.252.242
10    91 ms    91 ms    91 ms 209.85.249.11
11    86 ms    86 ms    86 ms 72.14.235.10
12    29 ms    29 ms    31 ms 72.14.234.53
13     *        *        *     Request timed out.
14    33 ms    31 ms    31 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

C:\Users\Scott>tracert 208.67.222.222

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

1    <1 ms    <1 ms     1 ms  MY IP
2     9 ms     6 ms     7 ms L100.ALBYNY-VFTTP-06.verizon-gni.net [96.236.43.
1]
3     6 ms     6 ms     6 ms G3-0-4-106.ALBYNY-LCR-01.verizon-gni.net [130.81
.177.120]
4    38 ms    19 ms    19 ms so-2-0-0-0.NY5030-BB-RTR1.verizon-gni.net [130.8
1.22.44]
5    19 ms    19 ms    19 ms 0.xe-3-3-0.BR2.NYC4.ALTER.NET [152.63.23.133]
6    14 ms    16 ms    14 ms 204.255.173.54
7    18 ms    19 ms    19 ms vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
8    21 ms    19 ms    19 ms ae-4-4.ebr1.NewYork1.Level3.net [4.69.141.17]
9    19 ms    19 ms    19 ms ae-81-81.csw3.NewYork1.Level3.net [4.69.134.74]

10 17 ms 15 ms 17 ms ae-3-80.edge1.NewYork1.Level3.net [4.69.155.142]

11 19 ms 19 ms 21 ms OPEN-DNS-IN.edge1.NewYork1.Level3.net [4.78.132.
22]
12 16 ms 16 ms 16 ms resolver1.opendns.com [208.67.222.222]

Trace complete.

C:\Users\Scott>tracert 4.2.2.2

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

1     3 ms    <1 ms    <1 ms  MY IP
2     7 ms     6 ms     6 ms L100.ALBYNY-VFTTP-06.verizon-gni.net [96.236.43.
1]
3     7 ms     6 ms     6 ms G3-0-4-106.ALBYNY-LCR-01.verizon-gni.net [130.81
.177.120]
4    20 ms    18 ms    19 ms so-2-0-0-0.NY5030-BB-RTR1.verizon-gni.net [130.8
1.22.44]
5    24 ms    19 ms    22 ms 0.xe-11-0-0.BR3.NYC4.ALTER.NET [152.63.26.113]
6    17 ms    17 ms    16 ms te-7-3-0.edge2.NewYork2.level3.net [4.68.111.137
]
7    22 ms    24 ms    21 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
8    20 ms    19 ms    19 ms ae-45-45.ebr2.NewYork1.Level3.net [4.69.141.21]

9 17 ms 17 ms 24 ms ae-72-72.csw2.NewYork1.Level3.net [4.69.148.38]

10 17 ms 17 ms 16 ms ae-2-70.edge2.NewYork1.Level3.net [4.69.155.80]

11 22 ms 21 ms 22 ms b.resolvers.Level3.net [4.2.2.2]

Trace complete.

C:\Users\Scott>

smith6612 · ‎08-01-2013

Buffalonian here,

When speed testing, use the FortressITX server in Clifton, New Jersey. The servers local to us tend to be hit or miss since Verizon does not peer with anyone in Buffalo from what I have seen.

Are you playing Call of Duty on a console or a PC? Stupid question. I'd also like to know if other games give you issues as well.

In_Domine · ‎08-01-2013

Yes, I have changed my DNS servers, namebench came up with Google's as the best bet over 4 separate tests. QoS was always hit or miss... And I figure it's immensely pointless if you have FiOS TV because DHCP Option 60 gives STBs some obscure "hidden priority". I've messed with IGMP Proxy, UPnP, tried wired and wireless, I've had new routers sent to my residence; etc... You name it and I can probably tell you I've done it. I really hate knowing that the MI424WR-GEN3i is the only router I have ever used that I HAD to become familiar with and constantly tinker to even get a playable connection. (and I'm subscribed to the 75/35 plan)

The main problem is that when FiOS first moved to my area I was filled with joy -- no more DSL! And now... it feels like I am on DSL, and not even an ethernet cord changes my ping times or download/upload. And I don't even want to do a speedtest or pingtest around 5:00pm. Heck, I wince everytime I have to use the internet at peak times... It's dreadful. And what's even more dreadful is my buddy who plays this game doesn't even subscribe to XBL anymore because, "It's pointless to, not even Verizon FiOS could solve crappy P2P". And I use to play BF3, I loved the game to death, I could tolerate people eating half a clip because it was probably the exact same on their screen; but the player owned servers and premium membership made me toss it. 😕

Aside from this, I wholeheartedly believe it is a bad routing problem with Verizon themselves in the WNY area. My brother doesn't have this problem in NYC, and nor do any of my distant friends. I guess I'm just severely irked at poor customer service on the phone, and I guess I'm just sick of being told to "reset my router and we'll run a speedtest on OUR website, from the NY, NY server". Which I can ping less than 20 to, and with any of Verizon's speedtest servers.

Moral of the story: I should never be speedtesting to my own area and coming back with these results from a wired computer at 5:00PM:

http://www.speedtest.net/result/2875092403.png

And I really do appreciate the replies, especially seeing someone from the Albany region getting a weird hop spike similar to mine. And to the fellow Buffalonian: is it at all possible for you to do a tracert and post on this page as well, if you could, many thanks! And I play on the 360, I only use my PC for RPG games, but I don't play the GOW series because it's impossible to do anything on FiOS(I remember running through everyone and holding an 8.00KDR, now I have like a .60KDR, it's pitiful, and I don't want to come off as a stat whore, I never was, I just happened to be good at the FPS genre and now I question if I'm just generally bad at FPS now). I'm just stuck between a rock and a hard place, go back to TWC or rough it out and stick with FiOS.

In_Domine · ‎08-01-2013

@ibamars:

And if you could, I would very much like your configuration settings. Even after all this time I've spent familiarizing myself with this router, I still feel like I'm missing something immensely important. Because I know a good host from a bad one, and not even a good host, let alone myself as host, is even remotely worthy of the title, "good". Much thanks if you get around to it!

smith6612 · ‎08-01-2013

Here's some traceroutes. Note, I am on DSL! Still anxiously waiting to get FiOS.

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

1    <1 ms    <1 ms    <1 ms 192.168.3.1
2     6 ms     6 ms     7 ms 10.41.15.1
3     7 ms     7 ms     7 ms P0-0-1-2.BFLONY-LCR-21.verizon-gni.net [130.81.44.232]
4    18 ms    19 ms    35 ms xe-1-1-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.209.34]
5     *       23 ms    22 ms 0.xe-3-0-1.BR1.NYC1.ALTER.NET [152.63.5.149]
6     *        *        *     Request timed out.
7    24 ms    23 ms    23 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
8    24 ms    23 ms    23 ms ae-45-45.ebr2.NewYork1.Level3.net [4.69.141.21]
9    23 ms    23 ms    23 ms ae-72-72.csw2.NewYork1.Level3.net [4.69.148.38]
10    23 ms    23 ms    23 ms ae-2-70.edge2.NewYork1.Level3.net [4.69.155.80]
11    23 ms    23 ms    23 ms b.resolvers.Level3.net [4.2.2.2]

Trace complete.

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms 192.168.3.1
2     7 ms     6 ms     7 ms 10.41.15.1
3    11 ms     7 ms     7 ms P0-0-0-2.BFLONY-LCR-21.verizon-gni.net [130.81.195.144]
4    19 ms    18 ms    19 ms xe-1-1-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.209.34]
5    23 ms    23 ms    22 ms 0.so-0-0-0.XT1.NYC4.ALTER.NET [152.63.1.41]
6    26 ms    24 ms    26 ms TenGigE0-4-0-0.GW8.NYC4.ALTER.NET [152.63.21.61]
7    23 ms    23 ms    23 ms Internet-gw.customer.alter.net [152.179.72.66]
8    24 ms    22 ms    23 ms 72.14.238.232
9    23 ms    24 ms    23 ms 209.85.252.250
10    34 ms    31 ms    30 ms 72.14.239.93
11    37 ms    37 ms    37 ms 72.14.235.12
12    39 ms    38 ms    37 ms 72.14.234.65
13     *        *        *     Request timed out.
14    38 ms    39 ms    38 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

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

1    <1 ms    <1 ms    <1 ms 192.168.3.1
2     7 ms     7 ms     7 ms 10.41.15.1
3     8 ms     7 ms     7 ms P0-0-1-2.BFLONY-LCR-21.verizon-gni.net [130.81.44.232]
4    39 ms    59 ms    19 ms xe-1-1-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.209.34]
5    21 ms    21 ms    21 ms 0.xe-10-1-0.BR1.NYC1.ALTER.NET [152.63.18.225]
6     *        *        *     Request timed out.
7    21 ms    26 ms    24 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
8    22 ms    21 ms    22 ms 4.69.201.37
9    21 ms    21 ms    22 ms ae-92-92.csw4.NewYork1.Level3.net [4.69.148.46]
10    21 ms    21 ms    22 ms ae-4-90.edge1.NewYork1.Level3.net [4.69.155.206]
11    22 ms    22 ms    22 ms OPEN-DNS-IN.edge1.NewYork1.Level3.net [4.78.132.22]
12    22 ms    21 ms    22 ms resolver1.opendns.com [208.67.222.222]

Trace complete.

NPAD Test:

Speed tests:

Traceroute to Buffalo, NY speedtest server.

Tracing route to makaiwell.com [199.195.253.102]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms 192.168.3.1
2     7 ms     7 ms     7 ms 10.41.15.1
3     7 ms     7 ms     7 ms P0-0-1-2.BFLONY-LCR-21.verizon-gni.net [130.81.44.232]
4    56 ms    19 ms    19 ms xe-1-1-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.209.34]
5    23 ms    23 ms    23 ms 0.xe-6-1-1.XT1.NYC4.ALTER.NET [152.63.10.57]
6    24 ms    23 ms    23 ms GigabitEthernet6-0-0.GW1.NYC4.ALTER.NET [152.63.20.49]
7    24 ms    23 ms    23 ms teliasonera-test.customer.alter.net [157.130.255.206]
8    25 ms    24 ms    81 ms nyk-bb1-link.telia.net [213.155.131.136]
9    33 ms    33 ms    33 ms buf-b1-link.telia.net [80.91.246.36]
10    33 ms    45 ms    33 ms giglinx-ic-155660-buf-b1.c.telia.net [213.248.96.42]
11    34 ms    33 ms    33 ms . [172.245.12.226]
12     *        *        *     Request timed out.
13    50 ms    51 ms    50 ms 199.195.255.107
14    65 ms    65 ms    67 ms cambria.makacdn.com [199.195.253.102]

Trace complete.

Ping tests (back to back, same server, with lowest latency):

smith6612 · ‎08-01-2013

Making this a separate post. In short, the tests above were done from an idle connection. Definitely looks like the networks are hurting, although they have been getting worse pretty quickly in the past year, especially after Sandy. Verizon's been having problems with Cogent, and TeliaSonera as well to put some notes down on things. Connectivity between Level3 seems fine although it has been a bit iffy on and off. That's not too much of a surprise since Level3 has their own problems.

Verizon sends all of the traffic from Buffalo, NY through New York City (even if initial termination goes to Newark, NJ).

Honestly though, stick with FiOS. You may use your own router with FiOS if the ActionTec is giving you a hard time. You may need the ActionTec around for FiOS TV if you have that service, but that can be set up behind your own router without an issue. Folks I know with FiOS and their own routers don't see problems with lag, granted they are all PC gamers like I am. The only real requirement I'd say is, get a router with Gigabit ports and Wireless N. That should ensure there's plenty of power under the hood to handle your connection.

The single thought of moving to Time Warner alone gives me the chills. They are really beefing up their network as of late, but they're already trialing 5GB and 30GB Caps an hour away in Rochester, NY which doesn't mean good things for the future. Plus, I work with folks who put up with Time Warner and even used to work for Time Warner, and they have the same problems. Sluggishness, buffering, the whole lot. Gaming performance is hit or miss, but as they say, your mileage may vary.

It's still hard to say what the deal is, though. I do play lag sensitive games like Minecraft and Source games such as TF2, Left 4 Dead, etc which eat data like no tomorrow, and I don't have issues unless my connection is saturated. Maybe, one or two servers will seem like there's a delay in registering a shot, although that could be a problem with the return path, which we cannot see.

In_Domine · ‎08-03-2013

Well, thanks for the information. Unfortunately, none of that is going to stop me from being disconnected 4+ times every day, having my router reset itself constantly, and have awful ping times...

...Alas, the waiting game continues. Thanks, again!

ibamars · ‎08-03-2013

Hey man, sorry took so long to get back. I no longer have my interent throught the Moca. Switched to ethernet and am using my own router.

Still have the issue with that 8.8.8.8 but heres my new tracert with my own router. Netgear WNDR3700. But heres my new results with this router using the 208.67.222.222

C:\Users\Scott>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms 192.168.1.1
2     3 ms     4 ms     4 ms L100.ALBYNY-VFTTP-06.verizon-gni.net {edited for privacy}
3     4 ms     4 ms     4 ms G3-0-4-206.ALBYNY-LCR-02.verizon-gni.net [130.81
.179.120]
4   106 ms    44 ms     9 ms so-5-1-1-0.NY325-BB-RTR2.verizon-gni.net [130.81
.22.46]
5     8 ms     9 ms     9 ms 0.so-4-0-2.XT2.NYC4.ALTER.NET [152.63.1.57]
6    15 ms    16 ms    14 ms TenGigE0-5-0-0.GW8.NYC4.ALTER.NET [152.63.21.65]

7    30 ms    31 ms    31 ms Internet-gw.customer.alter.net [152.179.72.66]
8    13 ms    16 ms    16 ms 72.14.238.232
9    76 ms    76 ms    76 ms 72.14.236.206
10    81 ms    81 ms    81 ms 209.85.249.11
11    81 ms    81 ms    81 ms 66.249.95.229
12    23 ms    24 ms    24 ms 72.14.234.55
13     *        *        *     Request timed out.
14    30 ms    29 ms    29 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

C:\Users\Scott>tracert 208.67.222.222

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

1    <1 ms    <1 ms    <1 ms 192.168.1.1
2     4 ms     4 ms     4 ms L100.ALBYNY-VFTTP-06.verizon-gni.net {edited for privacy}
3     3 ms     4 ms     4 ms G3-0-4-206.ALBYNY-LCR-02.verizon-gni.net [130.81
.179.120]
4     9 ms     9 ms     9 ms so-5-1-1-0.NY325-BB-RTR2.verizon-gni.net [130.81
.22.46]
5     9 ms     9 ms     9 ms 0.xe-9-1-0.BR1.NYC1.ALTER.NET [152.63.4.241]
6     *        *        *     Request timed out.
7     9 ms     9 ms     9 ms vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
8    14 ms    14 ms    14 ms ae-4-4.ebr1.NewYork1.Level3.net [4.69.141.17]
9     9 ms     9 ms    11 ms ae-91-91.csw4.NewYork1.Level3.net [4.69.134.78]

10 15 ms 14 ms 14 ms ae-4-90.edge1.NewYork1.Level3.net [4.69.155.206]

11 9 ms 9 ms 9 ms OPEN-DNS-IN.edge1.NewYork1.Level3.net [4.78.132.
22]
12 15 ms 14 ms 14 ms resolver1.opendns.com [208.67.222.222]

Trace complete.

C:\Users\Scott>

Im going to run some tests to see what may be better. Last night I was downloading from PSN using the verizon dns servers and kept getting dropped connections. As soon as I switched to the 208.67.222.222 server problem went away. I find it weird cause I thought all DNS did was do like an address thing, not sure why the drops.

ibamars · ‎08-03-2013

More results with the new set up. the 68 and 71 dns servers are the one Fios assigned to me. HMMMM

C:\Users\Scott>tracert 4.2.2.2

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

1    <1 ms    <1 ms    <1 ms 192.168.1.1
2     4 ms     4 ms     4 ms L100.ALBYNY-VFTTP-06.verizon-gni.net [96.236.43.
1]
3     3 ms     4 ms     4 ms G3-0-4-206.ALBYNY-LCR-02.verizon-gni.net [130.81
.179.120]
4     9 ms     9 ms     9 ms so-5-1-1-0.NY325-BB-RTR2.verizon-gni.net [130.81
.22.46]
5    10 ms     9 ms     9 ms 0.xe-8-0-0.BR3.NYC4.ALTER.NET [152.63.23.241]
6     8 ms     9 ms     9 ms te-7-3-0.edge2.NewYork2.level3.net [4.68.111.137
]
7    11 ms     9 ms     9 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
8     8 ms     9 ms     9 ms ae-45-45.ebr2.NewYork1.Level3.net [4.69.141.21]

9 9 ms 9 ms 9 ms ae-72-72.csw2.NewYork1.Level3.net [4.69.148.38]

10 14 ms 14 ms 14 ms ae-2-70.edge2.NewYork1.Level3.net [4.69.155.80]

11 14 ms 14 ms 14 ms b.resolvers.Level3.net [4.2.2.2]

Trace complete.

C:\Users\Scott>tracert 67.237.161.12

Tracing route to va-67-237-161-12.dhcp.embarqhsd.net [67.237.161.12]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms 192.168.1.1
2     4 ms     4 ms     4 ms L100.ALBYNY-VFTTP-06.verizon-gni.net [96.236.43.
1]
3     2 ms     4 ms     4 ms G3-0-4-206.ALBYNY-LCR-02.verizon-gni.net [130.81
.179.120]
4     8 ms     9 ms     9 ms so-5-1-1-0.NY325-BB-RTR2.verizon-gni.net [130.81
.22.46]
5     9 ms     9 ms     9 ms 0.xe-9-1-0.BR1.NYC1.ALTER.NET [152.63.4.241]
6    17 ms    14 ms    14 ms 63-235-40-53.dia.static.qwest.net [63.235.40.53]

7    19 ms    19 ms    19 ms dcx2-edge-01.inet.qwest.net [67.14.28.70]
8    16 ms    16 ms    16 ms 65.113.64.198
9    31 ms    31 ms    31 ms 208-110-248-238.centurylink.net [208.110.248.238
]
10    29 ms    29 ms    29 ms va-71-0-83-70.sta.embarqhsd.net [71.0.83.70]
11    71 ms    74 ms    74 ms va-67-237-161-12.dhcp.embarqhsd.net [67.237.161.
12]

Trace complete.

C:\Users\Scott>tracert 71.243.0.12

Tracing route to nsbost01.verizon.net [71.243.0.12]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms 192.168.1.1
2     5 ms     4 ms     4 ms L100.ALBYNY-VFTTP-06.verizon-gni.net [96.236.43.
1]
3     3 ms     4 ms     4 ms G3-0-4-106.ALBYNY-LCR-01.verizon-gni.net [130.81
.177.120]
4    15 ms    16 ms    16 ms so-2-0-0-0.NY5030-BB-RTR1.verizon-gni.net [130.8
1.22.44]
5    34 ms    24 ms    21 ms xe-0-1-0-0.BOS-BB-RTR1.verizon-gni.net [130.81.1
7.53]
6    21 ms    24 ms    21 ms so-7-1-0-0.BOS-CORE-RTR1.verizon-gni.net [130.81
.20.85]
7     *        *        *     Request timed out.
8    22 ms    21 ms    24 ms nsbost01.verizon.net [71.243.0.12]

Trace complete.

Categories

Mobile

Home

Accessories

Entertainment

Participate

Help

Self-Help Topics

Information Hub