CenturyLink → [CenturyTel] DSL Woes in E. NC

Over the past month a problem has crept into our connection. Internet connection will go away. My C1000A lights are all a-ok. My DSL line stats are A-Ok.
I will get a spinning wheel, or DNS server not found, or (more commonly) things just go away for 2-10 seconds and return.
Occasionally my actual connection goes out, but that is the exception.
What I do not understand is my DSL line stats (CRC errors) look good. Does this imply my local switch is ok, but the problem is upstream from it ?
Thanks for any help, Howie

We are served out of Rocky Mount NC:
traceroute to 76.0.181.113 (76.0.181.113), 30 hops max, 60 byte packets
1 10.10.0.1 (10.10.0.1) 3.611 ms 3.521 ms 3.615 ms
2 192.168.250.253 (192.168.250.253) 0.477 ms 0.392 ms 0.468 ms
3 Te8-1.br01.atl02.pccwbtn.net (63.218.69.89) 30.880 ms 30.851 ms 30.932 ms
4 TenGE0-0-0-10.br02.atl02.pccwbtn.net (63.218.68.98) 30.988 ms 31.143 ms 31.025 ms
5 atx-brdr-01.inet.qwest.net (63.146.26.165) 18.841 ms 18.806 ms 18.850 ms
6 rcmt-agw2.inet.qwest.net (67.14.59.50) 18.077 ms * 18.065 ms
7 71-32-28-214.rcmt.qwest.net (71.32.28.214) 18.034 ms 18.036 ms 18.073 ms
8 * * *
Maybe this ping helps ? We should get something like 13ms to rcmt (above)
Reply from 71.32.28.214: bytes=32 time=13ms TTL=254
Reply from 71.32.28.214: bytes=32 time=13ms TTL=254
Reply from 71.32.28.214: bytes=32 time=13ms TTL=254
Reply from 71.32.28.214: bytes=32 time=13ms TTL=254
Reply from 71.32.28.214: bytes=32 time=13ms TTL=254
Reply from 71.32.28.214: bytes=32 time=43ms TTL=254
Reply from 71.32.28.214: bytes=32 time=62ms TTL=254
Reply from 71.32.28.214: bytes=32 time=86ms TTL=254
Reply from 71.32.28.214: bytes=32 time=159ms TTL=254
Reply from 71.32.28.214: bytes=32 time=104ms TTL=254
Reply from 71.32.28.214: bytes=32 time=108ms TTL=254
Reply from 71.32.28.214: bytes=32 time=13ms TTL=254
Reply from 71.32.28.214: bytes=32 time=14ms TTL=254
Reply from 71.32.28.214: bytes=32 time=17ms TTL=254
Reply from 71.32.28.214: bytes=32 time=13ms TTL=254
Reply from 71.32.28.214: bytes=32 time=13ms TTL=254
Reply from 71.32.28.214: bytes=32 time=39ms TTL=254
Reply from 71.32.28.214: bytes=32 time=13ms TTL=254
Reply from 71.32.28.214: bytes=32 time=22ms TTL=254
Reply from 71.32.28.214: bytes=32 time=13ms TTL=254
Reply from 71.32.28.214: bytes=32 time=125ms TTL=254
Reply from 71.32.28.214: bytes=32 time=135ms TTL=254
Reply from 71.32.28.214: bytes=32 time=13ms TTL=254

We are served out of Rocky Mount NC:
traceroute to 76.0.181.113 (76.0.181.113), 30 hops max, 60 byte packets
1 10.10.0.1 (10.10.0.1) 3.611 ms 3.521 ms 3.615 ms
2 192.168.250.253 (192.168.250.253) 0.477 ms 0.392 ms 0.468 ms
3 Te8-1.br01.atl02.pccwbtn.net (63.218.69.89) 30.880 ms 30.851 ms 30.932 ms
4 TenGE0-0-0-10.br02.atl02.pccwbtn.net (63.218.68.98) 30.988 ms 31.143 ms 31.025 ms
5 atx-brdr-01.inet.qwest.net (63.146.26.165) 18.841 ms 18.806 ms 18.850 ms
6 rcmt-agw2.inet.qwest.net (67.14.59.50) 18.077 ms * 18.065 ms
7 71-32-28-214.rcmt.qwest.net (71.32.28.214) 18.034 ms 18.036 ms 18.073 ms
8 * * *
Maybe this ping helps ? We should get something like 13ms to rcmt (above)
Reply from 71.32.28.214: bytes=32 time=13ms TTL=254
Reply from 71.32.28.214: bytes=32 time=13ms TTL=254
Reply from 71.32.28.214: bytes=32 time=13ms TTL=254
Reply from 71.32.28.214: bytes=32 time=13ms TTL=254
Reply from 71.32.28.214: bytes=32 time=13ms TTL=254
Reply from 71.32.28.214: bytes=32 time=43ms TTL=254
Reply from 71.32.28.214: bytes=32 time=62ms TTL=254
Reply from 71.32.28.214: bytes=32 time=86ms TTL=254
Reply from 71.32.28.214: bytes=32 time=159ms TTL=254
Reply from 71.32.28.214: bytes=32 time=104ms TTL=254
Reply from 71.32.28.214: bytes=32 time=108ms TTL=254
Reply from 71.32.28.214: bytes=32 time=13ms TTL=254
Reply from 71.32.28.214: bytes=32 time=14ms TTL=254
Reply from 71.32.28.214: bytes=32 time=17ms TTL=254
Reply from 71.32.28.214: bytes=32 time=13ms TTL=254
Reply from 71.32.28.214: bytes=32 time=13ms TTL=254
Reply from 71.32.28.214: bytes=32 time=39ms TTL=254
Reply from 71.32.28.214: bytes=32 time=13ms TTL=254
Reply from 71.32.28.214: bytes=32 time=22ms TTL=254
Reply from 71.32.28.214: bytes=32 time=13ms TTL=254
Reply from 71.32.28.214: bytes=32 time=125ms TTL=254
Reply from 71.32.28.214: bytes=32 time=135ms TTL=254
Reply from 71.32.28.214: bytes=32 time=13ms TTL=254

Hops #1 and 2 makes it look like you might be in a double NAT situation. ie, running your own router behind centurylink's provided modem/router combo that hasn't been bridged. this can cause issues at times, not sure it would be your problem.

You mention DNS server not found, have you tried some alternative DNS servers instead of centurylink's DNS? When this issue is happening, can you still ping the address you did below? (IP directly, not by name)

Thanks for your reply.
Yes, I am running a gigabit router bridged off C1000a to make the NAS happy.
Yep, tried alternatives to CL & opendns w/ same results.
CL had me change the IP, but it still happens-- very intermittent tho.
It seems to me if the problem is my modem or router, that the pings to my IP (from remote server) should not change- but they dramatically do. I am assuming the ping response is from somewhere upstream of my local DSLAM switch?

so you have the c1000a connected to centurylink network and then you have your own router connected to the c1000a? If that's right, do you have anything else connecting to c1000a? If not, have you tried bridging the c1000a?

Yes, the C1000A is bridged. Nothing else to the C1000A.
The DLink dir-859 drives a Synology NAS and the WAN.
The CL line is internet only 11.7Mb connect that looks pretty clean to me.
Channel Type:
Fastpath
CRC Errors:
215
203
30 Minute CRC:
1
13
32
(0 FEC)
Thanks, Howie

but if the c1000a is bridged. why are hops one and two privet IPv4 address spaces?
1 10.10.0.1 (10.10.0.1) 3.611 ms 3.521 ms 3.615 ms
2 192.168.250.253 (192.168.250.253) 0.477 ms 0.392 ms 0.468 ms

the pings are really low as well which makes me think they're internal and hop one was from a wireless connected device. Is your D-Link router setup to hand out addresses in the range of 10.10.0.x?

n4af I am just west of you in little Washington and my DSL Speed between the hours of about 8:00pm-12:00am from from 4meg down to 2meg and comes back to normal sometime after midnight.

Wow, that is terrible. As long as your line stats look ok, my guess is a problem back at your DSLAM.
Best of luck, Howie