Durham ain't doing so hot either, and Ashburn has always seemed finicky for me.
Been erratic since I got on at 5:00 PM, trying to play some games.
Here's a trace route at about 11:03 PM:
Tracing route to 208.78.165.230 over a maximum of 12 hops
1 1 ms 1 ms 1 ms dslrouter.netgear.com [192.168.254.254]
2 33 ms 32 ms 33 ms adr02.drhm.nc.frontiernet.net [74.42.148.232]
3 33 ms 32 ms 32 ms ae1---1.car02.drhm.nc.frontiernet.net [74.40.71.69]
4 51 ms 69 ms 50 ms ae6---0.cor02.atln.ga.frontiernet.net [74.40.1.73]
5 49 ms 58 ms 48 ms ae1---0.cor02.asbn.va.frontiernet.net [74.40.2.198]
6 * * * Request timed out.
7 91 ms 70 ms 65 ms ge-4-1-0.mpr1.iad10.us.mfnx.net [206.126.236.86]
8 48 ms 48 ms 51 ms ae8.er4.iad10.us.zip.zayo.com [64.125.31.138]
9 49 ms 49 ms 51 ms 128.177.117.126.IPYX-094067-001-ZYO.zip.zayo.com [128.177.117.126]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
Trace complete.
Looks decent!
Then again just seconds later:
Tracing route to 208.78.165.230 over a maximum of 10 hops
1 1 ms 1 ms 1 ms dslrouter.netgear.com [192.168.254.254]
2 149 ms 149 ms 188 ms adr02.drhm.nc.frontiernet.net [74.42.148.232]
3 124 ms 120 ms 107 ms ae1---1.car02.drhm.nc.frontiernet.net [74.40.71.69]
4 176 ms 171 ms 175 ms ae6---0.cor02.atln.ga.frontiernet.net [74.40.1.73]
5 118 ms 111 ms 106 ms ae1---0.cor02.asbn.va.frontiernet.net [74.40.2.198]
6 * 76 ms 83 ms ae0---0.cbr01.asbn.va.frontiernet.net [74.40.2.174]
7 49 ms 48 ms 53 ms ge-4-1-0.mpr1.iad10.us.mfnx.net [206.126.236.86]
8 49 ms 51 ms 51 ms ae8.er4.iad10.us.zip.zayo.com [64.125.31.138]
9 49 ms 52 ms 49 ms 128.177.117.126.IPYX-094067-001-ZYO.zip.zayo.com [128.177.117.126]
10 * * * Request timed out.
Trace complete.
:(