I have no idea if this might be effecting you, or if something is going on at Verizon's own end. This is further compounded as I have FiOS, and gather you're connecting through their DSL service. In any case, today I have noticed some problems, and some of it has resulted in some timeouts getting to some websites.
Needless to say, by switching the DNS from using the defaults (Verizon's own DNS servers) to using Google's at 184.108.40.206 and 220.127.116.11 the problem seems to have been elliminated and things are back to normal. Before that, I had tried rebooting the router Verizon provided, resetting the PC's own ethernet interface, and Windows Update to no avail. That I got timeouts on a simple nslookup, but could ping the router, and even an outside IP address however was a bit of a give away.
You might try this, and see if it helps? But then again, we're also connecting to Verizon from different services they offer, from different locations, so not a given. Alternatively, perhaps a look at Verizon's own DNS services to see if something has happened? No idea, only their own people could check those. That said, with all these cyber attacks, a gang in Russia having captured 1.2 billion usernames and passwords from unspecified sites, and who the hell knows if this could have gone further?, I wouldn't rule anything out. If however, this goes away changing the DNS, and this shows up as a problem (Verizon's own DNS services) for multiple users, that would help nail down if something in fact is going on there, or not; regardless of whatever might or might not have caused this little issue.
Step one: Visit http://www.giganews.com/line_info.html and post up the Traceroute the page shows, if you wish. Be aware that your non-bogan public IP Address will show up. It might shown up as the final hop (bottom-most line of the trace) might contain a hop with your IP address in it. Either remove that line or show only the first two octets. What I'm looking for is a line that mentions "ERX" in it's name towards the end. If for some reason the trace does not complete (two lines full of Stars), keep the trace route intact.
For example this what I saw when I was using Verizon
traceroute to 71.242.*.* (71.242.*.*), 30 hops max, 60 byte packets
1 gw1-g-vlan201.dca.giganews.com (18.104.22.168) 13 ms 13 ms 13 ms
2 ash-bb1-link.telia.net (22.214.171.124) 39 ms 7 ms 7 ms
3 TenGigE0-2-0-0.GW1.IAD8.ALTER.NET (126.96.36.199) 4 ms 4 ms GigabitEthernet2-0-0.GW8.IAD8.ALTER.NET (188.8.131.52) 4 ms
4 so-7-1-0-0.PHIL-CORE-RTR1.verizon-gni.net (184.108.40.206) 6 ms 6 ms 6 ms
5 P3-0-0.PHIL-DSL-RTR11.verizon-gni.net (220.127.116.11) 6 ms 6 ms 6 ms
6 static-71-242-*-*.phlapa.east.verizon.net (71.242.*.*) 32 ms 32 ms 33 ms
Step two: Can you provide the Transceiver Statistics from your modem (if you are on DSL and not on FIOS) ?
#3 If you don't know how to get that info:
a) What is the brand and model of your modem?
b) If you have a RJ-45 WAN port router connected to it: What is the brand and model of the RJ-45 WAN port router?
#4 If you have a RJ-45 WAN port router connected to the modem, even if you know how to get the Transceiver Statistics from the modem: What is the brand and model of the RJ-45 WAN port router?
If you are the original poster (OP) and your issue is solved, please remember to click the "Solution?" button so that others can more easily find it. If anyone has been helpful to you, please show your appreciation by clicking the "Kudos" button.