Very high latency with Verizon in Philadelphia

[zram]

Called Verizon already, they determined it was not their issue and I need to see manufacturer support(for a network issue?).

The high latency started about 3-4 days ago with random hiccups in internet possibly 1-2 weeks prior.

C:\>tracert www.google.com

Tracing route to www.l.google.com [64.233.169.103]
over a maximum of 30 hops:

1 3 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 394 ms 404 ms 401 ms 10.7.94.1
3 403 ms 412 ms 419 ms at-1-1-0-1714.CORE-RTR1.PHIL.verizon-gni.net [130.81.10.1]
4 410 ms 413 ms 414 ms so-7-1-0-0.BB-RTR1.PHIL.verizon-gni.net [130.81.20.136]
5 420 ms 426 ms * 0.so-6-0-0.XL1.PHL6.ALTER.NET [152.63.3.77]
6 450 ms 438 ms 426 ms 0.so-0-0-0.XL3.IAD8.ALTER.NET [152.63.36.25]
7 426 ms 429 ms 437 ms 0.ge-6-0-0.BR2.IAD8.ALTER.NET [152.63.41.149]
8 449 ms 526 ms 483 ms 4.68.63.165
9 * 434 ms 435 ms ae-4-99.edge1.Washington1.Level3.net [4.68.17.208]
10 416 ms 417 ms 419 ms GOOGLE-INC.edge1.Washington1.Level3.net [4.79.231.6]
11 446 ms 454 ms 461 ms 64.233.175.171
12 465 ms 456 ms 452 ms 72.14.232.21
13 468 ms 472 ms 471 ms yo-in-f103.google.com [64.233.169.103]

Trace complete.


It seems to jump after getting out passed my modem. I have tried connecting my modem directly to the PC with the same issue. I have even taken a 50 ft telephone cable and went from my modem to the Bell Atlantic box on the back of my house and connected that way with no change. This to me, screams verizon's problem. I cannot see how this could be anything other then a failing modem/faulty telephone wire on my end.


I did ask if this could be an issue with the modem, he ran multiple tests and received back that the modem is working fine apparently. I think I am going to try and test the modem at another house wired for DSL tomorrow to see if it is my location or my modem.



I also ran a trace route online through MIT(http://bs.mit.edu:8001/cgi-bin/traceroute)...


1 W92-RTR-1-W92SRV21.MIT.EDU (18.7.21.1) 0.445 ms 0.283 ms 0.752 ms
2 EXTERNAL-RTR-2-BACKBONE-2.MIT.EDU (18.168.1.27) 0.331 ms 0.332 ms 0.325 ms
3 gi0-7.na21.b002250-1.bos01.atlas.cogentco.com (38.112.2.213) 1.058 ms 1.154 ms 1.201 ms
4 gi9-2.102.core01.bos01.atlas.cogentco.com (66.250.14.209) 1.249 ms 1.206 ms 1.101 ms
5 te3-3.mpd01.bos01.atlas.cogentco.com (154.54.5.22) 1.290 ms 1.170 ms 0.996 ms
6 te2-3.ccr02.dca01.atlas.cogentco.com (154.54.6.138) 12.717 ms 12.772 ms 18.854 ms
7 te4-3.mpd01.dca02.atlas.cogentco.com (154.54.7.2) 12.716 ms 13.150 ms 12.998 ms
8 te8-2.ccr02.iad01.atlas.cogentco.com (154.54.2.50) 13.342 ms 13.273 ms 15.211 ms
9 gi2-0-0.core01.iad01.atlas.cogentco.com (154.54.5.33) 13.246 ms 13.292 ms 13.418 ms
10 so-2-3-0-0.PEER-RTR1.ASH.verizon-gni.net (130.81.15.73) 40.102 ms 12.590 ms 12.627 ms
11 so-7-3-0-0.BB-RTR1.RES.verizon-gni.net (130.81.10.89) 13.070 ms 12.544 ms 12.437 ms
12 130.81.19.119 (130.81.19.119) 21.588 ms 130.81.19.77 (130.81.19.77) 26.151 ms 17.439 ms
13 so-7-1-0-0.CORE-RTR1.PHIL.verizon-gni.net (130.81.20.137) 21.469 ms 21.446 ms 17.492 ms
14 A3-0-0-1714.DSL-RTR3.PHIL.verizon-gni.net (130.81.10.2) 17.811 ms 21.457 ms 18.009 ms
15 pool-###-###-###-###.phil.east.verizon.net (###.###.###.###) 403.288 ms 413.352 ms 415.651 ms
16 pool-###-###-###-###.phil.east.verizon.net (###.###.###.###) 435.555 ms 432.220 ms 432.950 ms

(Edited out my IP with #'s, 15 and 16 are the same)


Again, to me it shows me that something is wrong with the service. Any suggestions?

[trogers]

Hop 2 is where high ping times start. It is the signals between the comp and the modem. Thus, you can safely assume it is not your ISP's fault.

As to why ping times at hop 2 are so high, common cause(s) are:

- malware in the comp
- software firewall
- electromagnetic interference on the modem