[outages] www.wunderground.com is down

Sat Jan 11 19:53:48 EST 2014

does everyone on the list really need to report in?

i think not.

On 01/09, Mark Kierzkowski wrote:
> Is up from the Chicago area
> 
> From: Outages [mailto:outages-bounces at outages.org] On Behalf Of Nathan Harris
> Sent: Thursday, January 09, 2014 12:39 PM
> To: 'Scott Martin'; outages at outages.org
> Subject: Re: [outages] www.wunderground.com is down
> 
> I live in Bozeman, MT and it is working just fine for me on Charter Cable.
> 
> Nate Harris
> Consultant
> (678) 297-0066
> nharris at xcentric.com<mailto:nharris at xcentric.com>
> 
> From: Outages [mailto:outages-bounces at outages.org] On Behalf Of Scott Martin
> 
> Not working from Sky Broadband in the Philippines -> Cogent
> 
>                                        My traceroute  [v0.85]
> MacBook-Pro.local (0.0.0.0)                                         Fri Jan 10 02:32:34 2014
> Keys:  Help   Display mode   Restart statistics   Order of fields   quit
>                                                            Packets               Pings
>  Host                                                    Loss%   Snt   Last   Avg  Best  Wrst StDev
>  1. 172.26.0.1                                            0.0%     5    6.4  18.3   6.0  63.6  25.3
>  2. 114.108.192.193                                       0.0%     5    7.9  13.0   7.9  23.7   6.4
>  3. 10GE1-1-0.GW.SJ.skybroadband.com.ph                   0.0%     5    9.6   9.6   7.9  14.6   2.8
>  4. tenge0-1-0-3.br03.hkg15.pccwbtn.net<http://br03.hkg15.pccwbtn.net>                   0.0%     5   23.9  26.1  23.9  27.6   1.2
>  5. TenGE12-1.br02.sjo01.pccwbtn.net<http://br02.sjo01.pccwbtn.net>                      0.0%     5  228.7 202.2 175.3 247.3  33.3
>  6. te0-0-0-33.ccr21.sjc03.atlas.cogentco.com<http://sjc03.atlas.cogentco.com>             0.0%     5  172.3 171.8 170.8 172.7   0.0
>  7. be2000.ccr21.sjc01.atlas.cogentco.com<http://sjc01.atlas.cogentco.com>                 0.0%     5  170.0 180.1 170.0 217.2  20.7
>  8. ???
> 
> MacBook-Pro:~$ ping www.wunderground.com<http://www.wunderground.com>
> PING www.wunderground.com<http://www.wunderground.com> (38.102.136.104): 56 data bytes
> Request timeout for icmp_seq 0
> Request timeout for icmp_seq 1
> ^C
> --- www.wunderground.com<http://www.wunderground.com> ping statistics ---
> 3 packets transmitted, 0 packets received, 100.0% packet loss
> Scotts-MacBook-Pro:~ swm$ telnet www.wunderground.com<http://www.wunderground.com> 80
> Trying 38.102.136.104...
> ^C
> 
> 
> On Jan 10, 2014, at 2:28 AM, Stephanie Chrisman <kalayna at gmail.com<mailto:kalayna at gmail.com>> wrote:
> 
> Works from Elkhart, IN.
> 
> On Thu, Jan 9, 2014 at 1:27 PM, Josh Luthman <josh at imaginenetworksllc.com<mailto:josh at imaginenetworksllc.com>> wrote:
> 
> Works for me in Dayton.  On vzw mobile.
> 
> On Jan 9, 2014 1:25 PM, "Nate Itkin" <outages at konadogs.net<mailto:outages at konadogs.net>> wrote:
> Good from San Diego, CA USA.
> 
> # traceroute -n 38.102.136.104
> traceroute to 38.102.136.104 (38.102.136.104), 30 hops max, 60 byte packets
>  1  10.1.2.1  3.965 ms  3.941 ms  3.932 ms
>  2  64.73.240.25  195.690 ms  195.700 ms  195.691 ms
>  3  208.57.10.66  7.161 ms  8.792 ms  8.806 ms
>  4  4.30.3.193  7.048 ms  8.617 ms  8.622 ms
>  5  4.69.133.206  25.354 ms  25.351 ms  26.964 ms
>  6  4.69.137.10  26.917 ms  23.247 ms 4.69.137.6  24.593 ms
>  7  4.69.137.25  25.074 ms 4.69.137.21  22.638 ms 4.69.137.29  25.870 ms
>  8  4.69.148.202  24.286 ms  24.248 ms  25.650 ms
>  9  4.69.148.109  25.630 ms  24.258 ms  25.189 ms
> 10  4.69.140.149  39.789 ms  39.772 ms  23.549 ms
> 11  4.53.128.234  23.232 ms  23.533 ms  23.523 ms
> 12  38.102.136.104  22.750 ms  23.826 ms  24.636 ms
> 
> 
> On Thu, Jan 09, 2014 at 06:19:02PM +0000, Daniel Green wrote:
> > Sites working from vegas and pings as well
> >
> > Z:\>ping www.wunderground.com<http://www.wunderground.com/>
> >
> > Pinging www.wunderground.com<http://www.wunderground.com/> [38.102.136.104] with 32 bytes of data:
> >
> > Reply from 38.102.136.104<http://38.102.136.104/>: bytes=32 time=199ms TTL=243
> > Reply from 38.102.136.104<http://38.102.136.104/>: bytes=32 time=38ms TTL=243
> > Reply from 38.102.136.104<http://38.102.136.104/>: bytes=32 time=22ms TTL=243
> > Reply from 38.102.136.104<http://38.102.136.104/>: bytes=32 time=22ms TTL=243
> >
> > Ping statistics for 38.102.136.104<http://38.102.136.104/>:
> >     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> > Approximate round trip times in milli-seconds:
> >     Minimum = 22ms, Maximum = 199ms, Average = 70ms
> >
> > Z:\>
> >
> >
> > From: Outages [mailto:outages-bounces at outages.org<mailto:outages-bounces at outages.org>] On Behalf Of John Barbieri
> >
> > Site works from Birmingham, AL off of Brighthouse Networks.
> >
> > Ping also succeeds:
> > ping www.wunderground.com<http://www.wunderground.com/>
> > PING www.wunderground.com<http://www.wunderground.com/> (38.102.136.104) 56(84) bytes of data.
> > 64 bytes from 38.102.136.104<http://38.102.136.104/>: icmp_seq=1 ttl=240 time=90.6 ms
> > 64 bytes from 38.102.136.104<http://38.102.136.104/>: icmp_seq=2 ttl=240 time=91.3 ms
> >
> > On 01/09/2014 12:12 PM, Network IPdog wrote:
> > > www.wunderground.com<http://www.wunderground.com/> is down from so. calif.
> > >
> > > ping www.wunderground.com<http://www.wunderground.com/>
> > >
> > > Pinging www.wunderground.com<http://www.wunderground.com/> [38.102.136.104] with 32 bytes of data:
> > >
> > > Request timed out.
> > > Request timed out.
> > > Request timed out.
> > > Request timed out.
> > >
> > > Ping statistics for 38.102.136.104<http://38.102.136.104/>:
> > >      Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),