DSL Connection Dropping Intermittently.

[MisterTechnical]

Verizon changed the front end router for my area. The problems seem to be gone at this point. Ill keep you posted. 

[smith6612]

Sounds great! The upstream statistics are improved but the margin is still a bit shoddy. If it's holding stabaly however, then it probably isn't an issue. Be awesome to see some additional speed added to your line once we've confirmed all issues are resolved.

[MisterTechnical]

Alllmost there. Connection is not dropping anymore, but there is packet loss that is causing lag.

Line Quality / Ping Test : Results

Anonymous test
 Tools page
 Test again
 Forum: Site Tools
 recent results from verizon.net

Test (From Central USA)	Loss	Min Latency	Avg Latency	Max Latency	Pass Fail
basic ping 10s of 40 byte packets, 2 per second	0%	45.8ms	46.4ms	48.1ms	pass
low bandwidth stream 10s of 512 byte packets at 56 kbit	10%	52.0ms	52.9ms	63.1ms	fail
medium bandwidth stream	was not performed
higher bandwidth stream	was not performed
your first hop ping stream of 40byte pings to 130.81.45.13	0% loss	39.2ms	You are 6ms to your first hop	pass
Jitter/loss with small packets tested from Central - USA:
Jitter/loss with small packets tested from West Coast - USA:

Sooooo close to normal. So close. 

Im going to see what I can do to fix this once and for all. (Another) modem coming tomorrow, maybe thatll be easier to handle data from on verizons end. 

[MisterTechnical]

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

^ My current packet loss. They said theyll fix it in 24-48 hours.

Its been three months since my net has been satisfactory.

[smith6612]

Unless your line is hitting a lot of errors and another modem is more tolerant to the noise, I doubt changing the modem is going to resolve the packet loss issue. I don't know why they keep sending you new ones when the DSLReports Line Quality Test simply relies on the modem/router itself to return packets. They always do unless there's something seriously wrong with the unit which would be noticed immediately. So, to sum it up, it's something on their end if there's packet loss. It always has been for every issue I've seen so far with the DSLReports Line Quality Test (granted, DSLReports might be having spasms but users don't report trouble that DSLReports shows if it's only DSLReports' servers having issues!)

[masho951]

Some lines will always test at 6.0db noise for the upstream. This happens when the line is served out of a remote DSLAM CATENA system. Could you post a new tracert log to verify that you actually got moved to a new router?

[smith6612]

---

@masho95 wrote:

Some lines will always test at 6.0db noise for the upstream. This happens when the line is served out of a remote DSLAM CATENA system. Could you post a new tracert log to verify that you actually got moved to a new router?

---

True. Just like the annoying 6dB bug with IKANOS systems as well. I guess we find out then if he's on a Catena just to confirm 🙂

[The_Toddler]

How do things look today, MisterTechnical?

I've been having what I think is the same problem. I called Verizon tech support on Wednesday and the rep could tell there was some trouble in my line, but it coincided with some other outage in Georgetown, so she said she would call back last night before escalating the situation just in case the two problems were related.

She did call back, but the DSL service was almost back to normal. I had a few dropouts, things seemed to be pretty stable. The verizon rep said she would call back again on Tuesday. This morning service is a little more spotty. Nowhere near as bad as what it was this past week, but not as stable as it was last night.

The rep wasn't all that helpful, and sounded like she was from a foreign call center. I said I had seen many posts such as yours on the forum, and asked if she knew anything about the front end router being replaced as you said. Of course her reply was "No, the router is your modem." OK.

[MisterTechnical]

No problem. I used pingplotter so I saw the exact moment when the modem was replaced. 

Also, Verizon has been irritating me to an almost intolerable extent when I call for tech support repair. I now frequently get connected to technicians who agressively pressure me to upgrade to Fios. 

If I -wanted- to upgrade to FIOS, believe me I would have.  A nice man named Stuart also portrayed it as the "solution to my problems" in a phrasing / demeanor that sounded suspiciously like extortion, before adding that "technology is evolving" and that I should upgrade to keep up. 

It is -not- the tech support's job to recommend I pay more money for a service I do not want, because the company I am paying "does not want" to address my issue. They are gladly accepting my monthly payments, but when it comes to making sure I recieve adequate service -for- that money, their stubborness is almost pitiful. '

It is also amusing. If they cannot repair tthis grade of connection, why should they expect me to pay them MORE? Usually, people upgrade when they are given -reliable- and -adequate- service, moreso than out of necessity (And the necessity usually does not stem from the previous item/service being poor.)

usually, when the  above situation happens, people switch companies. 

Still major packet loss. A  much-nicer rep I called last night gave me a ticket number regarding the repair that should fix the issue, Ill call in regarding its progress soon.

Test (From Central USA)	Loss	Min Latency	Avg Latency	Max Latency	Pass Fail
basic ping 10s of 40 byte packets, 2 per second	30%	52.6ms	53.7ms	55.4ms	fail
low bandwidth stream 10s of 512 byte packets at 56 kbit	25%	58.7ms	59.7ms	88.4ms	fail
medium bandwidth stream	was not performed
higher bandwidth stream	was not performed
your first hop ping stream of 40byte pings to 130.81.46.83	0% loss	44.4ms	You are 8ms to your first hop	pass
Jitter/loss with small packets tested from Central - USA:
Jitter/loss with small packets tested from West Coast - USA:
1 minute MTR (hop loss analysis) from Central - USA Hop Host LOSS Rcv Sent Best Avg Worst 0 ae-1.bb-c.slr.lxa.us.oneandone.net 0% 60 60 0.32 1.71 10.45 1 ae-10.bb-c.ms.mkc.us.oneandone.net 0% 60 60 0.78 0.88 1.08 2 64.209.105.233 0% 60 60 13.96 59.44 949.29 3 0.xe-8-2-0.BR3.CHI13.ALTER.NET 0% 60 60 14.14 17.84 102.95 4 0.ae3.CHI01-BB-RTR1.verizon-gni.NET 0% 60 60 14.48 21.07 111.17 5 P12-0.WASHDC-LCR-03.verizon-gni.net 0% 60 60 43.12 43.25 43.38 6 P4-0.WASHDC-CHCHMDBE-ERXG07.verizon-gni.net 0% 60 60 44.64 45.24 56.28 7 (TARGET IP ADDRESS) 37% 38 60 58.34 59.39 61.11 fail 1 minute MTR (hop loss analysis) from West Coast - USA Hop Host LOSS Rcv Sent Best Avg Worst 0 h-67-100-37-242.noclli.covad.net 0% 60 60 2.42 6.14 183.93 1 ge-6-14.car2.SanJose1.Level3.net 0% 60 60 2.52 26.36 383.09 2 ae-1-60.edge1.SanJose3.Level3.net 0% 60 60 3.10 5.07 48.55 3 MCI-level3-20G.SanJose3.Level3.net 0% 60 60 3.05 5.12 54.88 4 0.ge-2-0-0.SJC01-BB-RTR2.verizon-gni.net 0% 60 60 5.17 11.94 102.57 5 P12-0.WASHDC-LCR-04.verizon-gni.net 0% 60 60 89.09 89.22 89.47 6 P0-0.WASHDC-CHCHMDBE-ERXG07.verizon-gni.net 0% 60 60 92.37 92.54 93.53 7 (TARGET IP ADDRESS) 44% 34 60 103.91 104.51 105.44 fail

[MisterTechnical]

They gave me a follow up call regarding whether my internet was working properly. It was and is not.