Yes, I have been experiencing what you've mentioned. The other guy on here from MA mentioned DNS requests timing out or taking a long time for him to complete. I've reset my NIC and pfSense machine but doesn't help that much.
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
2 3 ms 1 ms 2 ms
3 4 ms 4 ms 3 ms G0-1-1-3.NYCMNY-LCR-21.verizon-gni.net [130.81.188.74]
4 4 ms 3 ms 4 ms so-5-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81.22.16]
5 5 ms 4 ms 3 ms 0.so-4-0-2.XT2.NYC4.ALTER.NET [152.63.1.57]
6 5 ms 4 ms 4 ms 0.ae4.BR3.NYC4.ALTER.NET [152.63.16.185]
7 * 110 ms 122 ms te-7-3-0.edge2.NewYork2.level3.net [4.68.111.137]
8 * 112 ms 116 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
9 122 ms * 126 ms ae-6-6.ebr2.NewYork1.Level3.net [4.69.141.21]
10 123 ms 108 ms 124 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66]
11 41 ms 58 ms 28 ms ae-14-60.car4.NewYork1.Level3.net [4.69.155.6]
12 110 ms * 110 ms SPLICE-COMM.car4.NewYork1.Level3.net [4.53.94.218]
13 116 ms 117 ms 115 ms resolver1.opendns.com [208.67.222.222]
This is happening every single night. My connection, my fiances, my cousins, etc. Tonight it just happened to have been worse.
I've noticed the same deal since Sandy hit NYC. The Alter.net hops haven't been performing too well. Perhaps aftermath storm damage or is there more to the picture that I'm missing?
C:\Users\>tracert resolver1.opendns.com
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.3.1
2 7 ms 6 ms 6 ms 10.41.15.1
3 6 ms 7 ms 6 ms P1-0.BFLONY-LCR-01.verizon-gni.net [130.81.195.144]
4 19 ms 19 ms 19 ms P11-0-0.BFLONY-LCR-02.verizon-gni.net [130.81.27.63]
5 19 ms 19 ms 19 ms so-3-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81.28.136]
6 19 ms 19 ms 18 ms so-7-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.19.48]
7 22 ms 21 ms 21 ms 0.so-0-0-0.XT1.NYC4.ALTER.NET [152.63.1.41]
8 20 ms 21 ms 21 ms 0.ae3.BR3.NYC4.ALTER.NET [152.63.16.181]
9 51 ms 52 ms 51 ms 204.255.173.54
10 50 ms 51 ms 52 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
11 54 ms 53 ms 53 ms ae-6-6.ebr2.NewYork1.Level3.net [4.69.141.21]
12 60 ms 55 ms 59 ms ae-92-92.csw4.NewYork1.Level3.net [4.69.148.46]
13 19 ms 19 ms 21 ms ae-44-90.car4.NewYork1.Level3.net [4.69.155.198]
14 54 ms 57 ms 56 ms SPLICE-COMM.car4.NewYork1.Level3.net [4.53.94.218]
15 45 ms 45 ms 44 ms resolver1.opendns.com [208.67.222.222]
Trace complete.
C:\Users\>tracert resolver1.opendns.com
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.3.1
2 7 ms 7 ms 6 ms 10.41.15.1
3 6 ms 7 ms 6 ms P1-0.BFLONY-LCR-01.verizon-gni.net [130.81.195.144]
4 19 ms 19 ms 19 ms P11-0-0.BFLONY-LCR-02.verizon-gni.net [130.81.27.63]
5 19 ms 19 ms 18 ms so-3-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81.28.136]
6 22 ms 23 ms 24 ms so-7-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.19.48]
7 74 ms 101 ms 21 ms 0.so-0-0-0.XT1.NYC4.ALTER.NET [152.63.1.41]
8 51 ms 25 ms 20 ms 0.ae3.BR3.NYC4.ALTER.NET [152.63.16.181]
9 47 ms 47 ms 47 ms te-7-3-0.edge2.NewYork2.level3.net [4.68.111.137]
10 47 ms 48 ms 49 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
11 45 ms 45 ms 44 ms ae-6-6.ebr2.NewYork1.Level3.net [4.69.141.21]
12 67 ms 53 ms 54 ms ae-72-72.csw2.NewYork1.Level3.net [4.69.148.38]
13 19 ms 21 ms 22 ms ae-44-90.car4.NewYork1.Level3.net [4.69.155.198]
14 67 ms 62 ms 62 ms SPLICE-COMM.car4.NewYork1.Level3.net [4.53.94.218]
15 45 ms 45 ms 45 ms resolver1.opendns.com [208.67.222.222]
Trace complete.
C:\Users\>
·