If you're have issues this evening, it's probably due to reasons like below. I'm impressed with how high the latency is at the last ALTER.NET hop given that it's within Verizon's network.
WinMTR Statistics
| Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
| 192.168.0.1 | 0 | 275 | 275 | 0 | 0 | 1 | 0 |
| L100.PITBPA-VFTTP-33.verizon-gni.net | 0 | 275 | 275 | 2 | 4 | 31 | 4 |
| G0-1-0-5.PITBPA-LCR-21.verizon-gni.net | 0 | 275 | 275 | 2 | 5 | 12 | 5 |
| xe-15-1-0-0.RES-BB-RTR1.verizon-gni.net | 0 | 275 | 275 | 7 | 11 | 65 | 8 |
| 0.xe-5-3-0.BR1.IAD8.ALTER.NET | 1 | 267 | 265 | 35 | 46 | 135 | 47 |
| ae16.edge1.washingtondc12.level3.net | 13 | 178 | 155 | 55 | 66 | 97 | 66 |
| vl-3601-ve-225.ebr2.Washington12.Level3.net | 0 | 275 | 275 | 53 | 62 | 75 | 65 |
| ae-2-52.edge2.Washington12.Level3.net | 1 | 271 | 270 | 251 | 300 | 354 | 298 |
| 4.26.6.198 | 5 | 235 | 225 | 110 | 118 | 127 | 115 |
| ipv4_1.lagg0.c050.iad001.ix.nflxvideo.net | 6 | 225 | 213 | 111 | 117 | 126 | 121 |