Confirmed from here in the Midwest, too. nagios:/home/fbulk# tcptraceroute www.wunderground.com Selected device eth0.3, address 96.31.0.5, port 44816 for outgoing packets Tracing the path to www.wunderground.com (38.102.136.104) on TCP port 80 (www), 30 hops max 1 router-core-inside.mtcnet.net (96.31.0.254) 0.216 ms 0.181 ms 0.191 ms 2 sxct.movl.mtcnet.net (167.142.156.194) 0.184 ms 0.134 ms 0.125 ms 3 siouxcenter.movl.153.netins.net (167.142.180.153) 2.012 ms 1.926 ms 1.921 ms 4 ins-kb1-te-13-2-220.kmrr.netins.net (167.142.64.253) 6.533 ms 6.434 ms 6.456 ms 5 ins-kc2-et-8-3.kmrr.netins.net (167.142.67.37) 8.162 ms 8.098 ms 8.075 ms 6 ins-dc1-et-8-1.desm.netins.net (167.142.67.29) 8.142 ms 8.161 ms 8.075 ms 7 te-3-3.car2.KansasCity1.Level3.net (4.53.34.113) 14.285 ms 15.358 ms 14.361 ms 8 ae-4-4.ebr2.Denver1.Level3.net (4.69.135.238) 26.991 ms 26.923 ms 26.917 ms 9 ae-1-100.ebr1.Denver1.Level3.net (4.69.151.181) 27.013 ms 26.995 ms 26.902 ms 10 ae-3-3.ebr2.SanJose1.Level3.net (4.69.132.57) 52.141 ms 52.084 ms 52.083 ms 11 ae-1-6.bar2.SanFrancisco1.Level3.net (4.69.140.153) 53.251 ms 53.376 ms 53.244 ms 12 ae-0-11.bar1.SanFrancisco1.Level3.net (4.69.140.145) 53.143 ms 53.129 ms 53.079 ms 13 ae-4-4.car1.SanFrancisco1.Level3.net (4.69.133.149) 115.776 ms 88.438 ms 68.525 ms 14 GLOBAL-INTE.car1.SanFrancisco1.Level3.net (4.53.128.234) 54.070 ms 53.940 ms 53.996 ms 15 38.102.136.104 [open] 53.630 ms 53.629 ms 53.741 ms nagios:/home/fbulk# Frank From: Colleen Velo [mailto:cmvelo@gmail.com] Sent: Saturday, December 31, 2011 8:15 AM To: Frank Bulk Cc: outages@outages.org Subject: Re: [outages] Wunderground down for anyone else? fyi: Wunderground appears to be back online: $: /var/lib/tomcat6/logs/IB$ traceroute www.wunderground.com traceroute to www.wunderground.com (38.102.136.104), 30 hops max, 60 byte packets 1 173.192.157.225-static.reverse.softlayer.com (173.192.157.225) 0.400 ms 0.461 ms 0.511 ms 2 ae12.dar02.sr01.sea01.networklayer.com (67.228.118.226) 7.270 ms 7.245 ms 7.251 ms 3 ae9.bbr02.wb01.sea02.networklayer.com (173.192.18.184) 0.453 ms 0.433 ms 0.451 ms 4 te-3-2.car4.Seattle1.Level3.net (4.71.152.137) 0.622 ms 0.675 ms 0.712 ms 5 ae-31-51.ebr1.Seattle1.Level3.net (4.69.147.150) 3.827 ms 3.812 ms 3.923 ms 6 ae-7-7.ebr2.SanJose1.Level3.net (4.69.132.49) 17.959 ms 18.077 ms 18.068 ms 7 ae-1-6.bar2.SanFrancisco1.Level3.net (4.69.140.153) 18.864 ms 19.038 ms 18.770 ms 8 ae-0-11.bar1.SanFrancisco1.Level3.net (4.69.140.145) 18.995 ms 18.907 ms 18.778 ms 9 ae-4-4.car1.SanFrancisco1.Level3.net (4.69.133.149) 19.151 ms 19.201 ms 18.863 ms 10 GLOBAL-INTE.car1.SanFrancisco1.Level3.net (4.53.128.234) 19.775 ms 19.827 ms 19.906 ms 11 38.102.136.100 (38.102.136.100) 19.440 ms 19.447 ms 19.352 ms 12 38.102.136.100 (38.102.136.100) 19.479 ms 19.557 ms 19.503 ms On Sat, Dec 31, 2011 at 7:50 AM, Frank Bulk <frnkblk@iname.com> wrote: Same here: nagios:/home/fbulk# tcptraceroute www.wunderground.com Selected device eth0.3, address 96.31.0.5, port 49309 for outgoing packets Tracing the path to www.wunderground.com (38.102.136.104) on TCP port 80 (www), 30 hops max 1 router-core-inside.mtcnet.net (96.31.0.254) 0.220 ms 0.189 ms 0.193 ms 2 sxct.movl.mtcnet.net (167.142.156.194) 0.184 ms 0.137 ms 0.129 ms 3 siouxcenter.movl.153.netins.net (167.142.180.153) 2.032 ms 1.921 ms 1.932 ms 4 ins-kb1-te-13-2-220.kmrr.netins.net (167.142.64.253) 6.595 ms 6.929 ms 6.573 ms 5 ins-kc2-et-8-3.kmrr.netins.net (167.142.67.37) 8.077 ms 8.091 ms 8.062 ms 6 ins-dc1-et-8-1.desm.netins.net (167.142.67.29) 8.201 ms 8.152 ms 8.111 ms 7 te-3-3.car2.KansasCity1.Level3.net (4.53.34.113) 14.309 ms 14.305 ms 14.299 ms 8 ae-4-4.ebr2.Denver1.Level3.net (4.69.135.238) 26.934 ms 26.901 ms 26.881 ms 9 ae-1-100.ebr1.Denver1.Level3.net (4.69.151.181) 26.888 ms 26.962 ms 26.947 ms 10 ae-3-3.ebr2.SanJose1.Level3.net (4.69.132.57) 52.187 ms 52.168 ms 52.208 ms 11 ae-1-6.bar2.SanFrancisco1.Level3.net (4.69.140.153) 61.726 ms 53.280 ms 53.301 ms 12 ae-0-11.bar1.SanFrancisco1.Level3.net (4.69.140.145) 72.035 ms 53.173 ms 53.175 ms 13 ae-4-4.car1.SanFrancisco1.Level3.net (4.69.133.149) 53.598 ms 53.583 ms 53.595 ms 14 GLOBAL-INTE.car1.SanFrancisco1.Level3.net (4.53.128.234) 54.026 ms 54.121 ms 54.008 ms 15 * * From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Colleen Velo Sent: Saturday, December 31, 2011 1:04 AM To: outages@outages.org Subject: [outages] Wunderground down for anyone else? I have been unable to reach http://www.wunderground.com/ from Mpls, Mn as well as from my colos in the Washington, Dallas and Seattle locations. (http://www.downforeveryoneorjustme.com/www.wunderground.com also reports it down) Saw one mention on Twitter of Level3 in SF dropping packets: yeah, my route to <http://twitter.com/#!/wunderground> @wunderground is dropped by level3 in SF. great jorb Anyone else having issues? Thanks in advance, -- Colleen Velo email: cmvelo@gmail.com -- Colleen Velo email: cmvelo@gmail.com