[Outages-discussion] [outages] yahoo.com down?

[frnkblk at iname.com]

This is what I saw overnight (all times U.S. Central):

 

*	HTTPv6 checks to

*	dstest.yahoo.com (both hosts) intermittently time out from ~1:10 to ~4:15 am
*	www.frontier.com <http://www.frontier.com>  timeout from ~3:02 to ~3:06 am

*	Email to yahoo.com backed up from ~2:18 to ~3:17 am

*	“DNS lookup failed (dns=127.0.0.1 dom=yahoo.com) blank response”

 

Frank

 

From: Outages <outages-bounces at outages.org> On Behalf Of Charles D'Aoust via Outages
Sent: Thursday, September 5, 2019 2:49 AM
To: Stephane Bortzmeyer <bortzmeyer at nic.fr>
Cc: outages at outages.org
Subject: Re: [outages] yahoo.com down?

 

Yeah I can confirm, DNS resolving yahoo.com <http://yahoo.com>  were unreachable for ~50m.

 

Outage is still ongoing, I cannot reach the website from a few locations across the US, but it seems to resolve fine now.


---
Charles D’Aoust

 

 

On Thu, Sep 5, 2019 at 3:35 AM Stephane Bortzmeyer via Outages <outages at outages.org <mailto:outages at outages.org> > wrote:

On Thu, Sep 05, 2019 at 09:08:48AM +0200,
 Stephane Bortzmeyer via Outages <outages at outages.org <mailto:outages at outages.org> > wrote 
 a message of 6 lines which said:

> It seems all name servers of the yahoo.com <http://yahoo.com>  domain are unresponsive
> from most ASes (it works in some). Any idea what's going on?

Confirmed by the company (and by many user reports on Twitter):

https://twitter.com/YahooCare/status/1169500570937282560

Other Verizon services seem affected as well (verizonmedia.com <http://verizonmedia.com> ,
huffingtonpost.com <http://huffingtonpost.com> ) although less severely probably because of DNS
caching.
_______________________________________________
Outages mailing list
Outages at outages.org <mailto:Outages at outages.org> 
https://puck.nether.net/mailman/listinfo/outages

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages-discussion/attachments/20190905/8df6eec1/attachment.htm>