Has anyone noticed issues reaching Qwest destinations around 4:05a-4:07a Mountain Time today? We received alerts that two of our sites that happened to have Qwest connectivity in common were unavailable during that period. Both sites being monitored were in different facilities but both in Boise. -J Traceroute #1 1 ip-67-205-112-66.static.privatedns.com (67.205.112.66) 0.842 ms 0.908 ms 0.936 ms 2 te8-4.v0707.cl-core04.mtl.iweb.com (67.205.127.121) 1.047 ms 1.068 ms 1.089 ms 3 if-9-1.icore1.MTT-Montreal.as6453.net (206.82.135.29) 7.737 ms 7.813 ms 7.837 ms 4 if-10-0-0-19.mcore3.MTT-Montreal.as6453.net (216.6.114.13) 0.907 ms 0.935 ms 0.955 ms 5 if-9-0-0-0.tcore2.NYY-NewYork.as6453.net (216.6.99.9) 7.871 ms 7.904 ms 7.926 ms 6 if-11-2.tcore1.NYY-NewYork.as6453.net (216.6.99.2) 7.815 ms 8.013 ms 8.032 ms 7 jfk-brdr-04.inet.qwest.net (63.146.27.41) 7.942 ms 7.827 ms 7.790 ms Traceroute #2 1 207.97.207.194 (207.97.207.194) 0.549 ms 0.578 ms 0.620 ms 2 core1-5.iad1.rackspace.com (69.20.2.18) 0.303 ms 0.354 ms 0.400 ms 3 vlan901.edge3.iad1.rackspace.com (69.20.1.3) 196.221 ms 196.284 ms 196.328 ms 4 dcx2-edge-01.inet.qwest.net (67.133.246.157) 0.368 ms 0.355 ms 0.349 ms ------------------- Jason J. W. Williams COO/CTO, DigiTar williamsjj@digitar.com V: 208.343.8520 M: 208.863.0727 F: 208.322.8522 IM: williamsjj@digitar.com