- « Previous
-
- 1
- 2
- Next »
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I had this issue for months now and they wanted to send a tech over and charge me.
There are alot more people with these problems than you think!
http://www.dslreports.com/forum/r24380841-northeast-SpeedLatency-issues-every-night-at-2am
I'll tolerate it until october when my contract expires and if its not fixed by then I'm going to switch back to comcast
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
well with high latency's to the very first hop like that, I Would call them when the problem is happening and have the front line guy acknowledge that 200+ ms to the first hop is excessive and see if he can talk with his NT about it. it sounds like it would be a problem in the local CO or something, but I would have their network tech's make that call.
you can also go the round about way and email their admins but that might take a while. do a who is look up on that ip - it will give an admin email address.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the ideas.
I did do a whois look up and emailed the associated address on Friday (7/24).
Today, I received a followup call from Verizon Tech Support which was useless, because they weren't a NT or responsible for 74.108.26.1 in any way. In fact, they tried to claim Verizon didn't own 74.108.26.1 (go whois it and laugh)... I think because it doesn't resolve under the Verizon domain. Wow!
Anyway, I had him keep the ticket open and he rebooted the ONT and I guess I'll call back when it happens again (if it does) between 8 and 5pm when a NT is around on a weekday. As of right now, things have been largely better, so perhaps they addressed the issue Friday while I was away.
We'll see.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just checked my connection again... here are the results as of 12:20am on Sunday, July 25th...
Tracing route to shacknews.com [68.142.120.133]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 42 ms 279 ms 240 ms 74.108.26.1
3 118 ms 237 ms 100 ms G5-0-8-1977.NYCMNY-LCR-09.verizon-gni.net [130.8
1.140.240]
4 26 ms 74 ms 196 ms so-6-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81
.29.236]
5 190 ms 81 ms 127 ms 0.so-4-0-1.XL4.NYC4.ALTER.NET [152.63.10.29]
6 129 ms 208 ms 233 ms TenGigE0-7-0-0.GW8.NYC4.ALTER.NET [152.63.22.45]
7 147 ms 227 ms 240 ms limelightnetworks.customer.alter.net [65.206.122
.182]
8 319 ms 314 ms 247 ms tge1-2.fr4.ord.llnw.net [69.28.171.193]
9 283 ms 392 ms 259 ms tge10-1.fr4.dal.llnw.net [69.28.171.241]
10 218 ms 335 ms 185 ms 68.142.120.133
Trace complete.
As you can see, the problem has not been resolved and pings starting at 74.108.26.1degrad to unacceptable levels for modern broadband.
Bandwidth is typically unaffected, clocking in at around 15/5. Regardless, streaming, games, and anything interactive on the web are relatively useless with this level of latency in play.
Verizon, fix it.
I've called over 5 times now, I've emailed, I've provided documentation, I've posted it here as well. Ball is in your court. Get it right.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
1:30 am EST Sunday, July 25 2010
Tracing route to shacknews.com [68.142.120.133]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 380 ms 173 ms 172 ms 74.108.26.1
3 202 ms 168 ms 258 ms G5-0-8-1977.NYCMNY-LCR-09.verizon-gni.net [130.8
1.140.240]
4 260 ms 279 ms 37 ms so-6-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81
.29.236]
5 258 ms 225 ms 203 ms 0.so-4-0-1.XL4.NYC4.ALTER.NET [152.63.10.29]
6 168 ms 266 ms 277 ms TenGigE0-5-4-0.GW8.NYC4.ALTER.NET [152.63.18.206
]
7 272 ms 295 ms 225 ms limelightnetworks.customer.alter.net [65.206.122
.182]
8 380 ms 390 ms 360 ms tge1-2.fr4.ord.llnw.net [69.28.171.193]
9 430 ms 430 ms 341 ms tge10-1.fr4.dal.llnw.net [69.28.171.241]
10 301 ms 385 ms 348 ms 68.142.120.133
Trace complete.
Pinging 74.108.26.1 with 32 bytes of data:
Reply from 74.108.26.1: bytes=32 time=307ms TTL=126
Reply from 74.108.26.1: bytes=32 time=325ms TTL=126
Reply from 74.108.26.1: bytes=32 time=398ms TTL=126
Reply from 74.108.26.1: bytes=32 time=138ms TTL=126
Ping statistics for 74.108.26.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 138ms, Maximum = 398ms, Average = 292ms
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As of 6:20am Sunday, July 25, 2010...
Tracing route to shacknews.com [68.142.120.133]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 929 ms 413 ms 99 ms 74.108.26.1
3 506 ms 931 ms 209 ms G5-0-8-1977.NYCMNY-LCR-09.verizon-gni.net [130.81.140.240]
4 546 ms 29 ms 341 ms so-6-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81.29.236]
5 2182 ms 45 ms 799 ms 0.so-4-0-1.XL4.NYC4.ALTER.NET [152.63.10.29]
6 593 ms 147 ms 314 ms TenGigE0-5-4-0.GW8.NYC4.ALTER.NET [152.63.18.206]
7 83 ms 511 ms 924 ms limelightnetworks.customer.alter.net [65.206.122.182]
8 720 ms 426 ms 680 ms tge1-2.fr4.ord.llnw.net [69.28.171.193]
9 615 ms 930 ms 213 ms tge10-1.fr4.dal.llnw.net [69.28.171.241]
10 819 ms 1394 ms 1004 ms 68.142.120.133
Trace complete.
Pinging 74.108.26.1 with 32 bytes of data:
Reply from 74.108.26.1: bytes=32 time=160ms TTL=126
Reply from 74.108.26.1: bytes=32 time=517ms TTL=126
Reply from 74.108.26.1: bytes=32 time=714ms TTL=126
Reply from 74.108.26.1: bytes=32 time=824ms TTL=126
Ping statistics for 74.108.26.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 160ms, Maximum = 824ms, Average = 553ms
Hoping to get in touch with a network technician or someone that can actually look at this device today. Customer Service told me to call back today after 6am EST. 2182ms ping clearly indicates a problem.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
8:40am Sunday, July 25th 2010
Tracing route to shacknews.com [68.142.120.133]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 1266 ms 50 ms 93 ms 74.108.26.1
3 124 ms 108 ms 278 ms G5-0-8-1977.NYCMNY-LCR-09.verizon-gni.net [130.81.140.240]
4 16 ms 228 ms 174 ms so-6-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81.29.236]
5 251 ms 311 ms 259 ms 0.so-4-0-1.XL4.NYC4.ALTER.NET [152.63.10.29]
6 738 ms 696 ms 15 ms TenGigE0-5-1-0.GW8.NYC4.ALTER.NET [152.63.21.73]
7 126 ms 177 ms 225 ms limelightnetworks.customer.alter.net [65.206.122.182]
8 146 ms 123 ms 231 ms tge1-2.fr4.ord.llnw.net [69.28.171.193]
9 151 ms 108 ms 177 ms tge10-1.fr4.dal.llnw.net [69.28.171.241]
10 297 ms 106 ms 252 ms 68.142.120.133
Trace complete.
Pinging 74.108.26.1 with 32 bytes of data:
Reply from 74.108.26.1: bytes=32 time=494ms TTL=126
Reply from 74.108.26.1: bytes=32 time=125ms TTL=126
Reply from 74.108.26.1: bytes=32 time=176ms TTL=126
Reply from 74.108.26.1: bytes=32 time=707ms TTL=126
Ping statistics for 74.108.26.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 125ms, Maximum = 707ms, Average = 375ms
Spoke with customer services this morning, who spoke ot a NT, who suggested they schedule a service tech to come out and look at things on Monday. Unfortunately, they only have 8-5 appointment windows so its not necessarily 100% that they'll see the high latency which occurs between 6pm and 6am most commonly.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
well at least they have a tech looking at it, I think it's more in the central office than you're place, but what do I know.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Technician stopped by today. As expected, in the middle of the day, the connection was well within exceptable limits. Just woke up and I see this...
Tracing route to shacknews.com [68.142.120.133]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 312 ms 350 ms 445 ms 74.108.26.1
3 218 ms 246 ms 354 ms G5-0-8-1977.NYCMNY-LCR-09.verizon-gni.net [130.81.140.240]
4 257 ms 333 ms 243 ms so-6-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81.29.236]
5 370 ms 252 ms 301 ms 0.so-4-0-1.XL4.NYC4.ALTER.NET [152.63.10.29]
6 304 ms 252 ms 368 ms TenGigE0-7-0-0.GW8.NYC4.ALTER.NET [152.63.22.45]
7 280 ms 411 ms 616 ms limelightnetworks.customer.alter.net [65.206.122.182]
8 511 ms 469 ms 258 ms tge1-2.fr4.ord.llnw.net [69.28.171.193]
9 368 ms 368 ms 360 ms tge10-1.fr4.dal.llnw.net [69.28.171.241]
10 327 ms 207 ms 188 ms 68.142.120.133
Trace complete.
Pinging 74.108.26.1 with 32 bytes of data:
Reply from 74.108.26.1: bytes=32 time=355ms TTL=126
Reply from 74.108.26.1: bytes=32 time=292ms TTL=126
Reply from 74.108.26.1: bytes=32 time=232ms TTL=126
Reply from 74.108.26.1: bytes=32 time=280ms TTL=126
Ping statistics for 74.108.26.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 232ms, Maximum = 355ms, Average = 289ms
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Nothing is ever Verizon's fault.
They want your money but they don't want to provide reliable service.
- « Previous
-
- 1
- 2
- Next »