[prev in list] [next in list] [prev in thread] [next in thread]
List: outages
Subject: Re: [Outages-discussion] [outages] yahoo.com down?
From: <frnkblk () iname ! com>
Date: 2019-09-05 12:24:11
Message-ID: 001b01d563e4$d3a18950$7ae49bf0$ () iname ! com
[Download RAW message or body]
This is a multipart message in MIME format.
[Attachment #2 (multipart/alternative)]
This is a multipart message in MIME format.
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@outages.org> On Behalf Of Charles D'Aoust via Outages
Sent: Thursday, September 5, 2019 2:49 AM
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Cc: outages@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@outages.org \
<mailto:outages@outages.org> > wrote:
On Thu, Sep 05, 2019 at 09:08:48AM +0200,
Stephane Bortzmeyer via Outages <outages@outages.org <mailto:outages@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@outages.org <mailto:Outages@outages.org>
https://puck.nether.net/mailman/listinfo/outages
[Attachment #5 (text/html)]
<html xmlns:v="urn:schemas-microsoft-com:vml" \
xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:x="urn:schemas-microsoft-com:office:excel" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type \
content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 \
(filtered medium)"><style><!-- /* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:93406751;
mso-list-type:hybrid;
mso-list-template-ids:-1284188744 67698689 67698691 67698693 67698689 67698691 \
67698693 67698689 67698691 67698693;} @list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.25in;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.75in;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.75in;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.25in;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.75in;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:4.25in;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div \
class=WordSection1><p class=MsoNormal>This is what I saw overnight (all times U.S. \
Central):<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><ul \
style='margin-top:0in' type=disc><li class=MsoListParagraph \
style='margin-left:-.25in;mso-list:l0 level1 lfo1'>HTTPv6 checks \
to<o:p></o:p></li><ul style='margin-top:0in' type=circle><li class=MsoListParagraph \
style='margin-left:-.25in;mso-list:l0 level2 lfo1'>dstest.yahoo.com (both hosts) \
intermittently time out from ~1:10 to ~4:15 am<o:p></o:p></li><li \
class=MsoListParagraph style='margin-left:-.25in;mso-list:l0 level2 lfo1'><a \
href="http://www.frontier.com">www.frontier.com</a> timeout from ~3:02 to ~3:06 \
am<o:p></o:p></li></ul><li class=MsoListParagraph \
style='margin-left:-.25in;mso-list:l0 level1 lfo1'>Email to yahoo.com backed up from \
~2:18 to ~3:17 am<o:p></o:p></li><ul style='margin-top:0in' type=circle><li \
class=MsoListParagraph style='margin-left:-.25in;mso-list:l0 level2 lfo1'>"DNS lookup \
failed (dns=127.0.0.1 dom=yahoo.com) blank response"<o:p></o:p></li></ul></ul><p \
class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Frank<o:p></o:p></p><p \
class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>From:</b> Outages \
<outages-bounces@outages.org> <b>On Behalf Of </b>Charles D'Aoust via \
Outages<br><b>Sent:</b> Thursday, September 5, 2019 2:49 AM<br><b>To:</b> Stephane \
Bortzmeyer <bortzmeyer@nic.fr><br><b>Cc:</b> \
outages@outages.org<br><b>Subject:</b> Re: [outages] yahoo.com down?<o:p></o:p></p><p \
class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Yeah I can confirm, DNS \
resolving <a href="http://yahoo.com">yahoo.com</a> were unreachable for \
~50m.<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p \
class=MsoNormal>Outage is still ongoing, I cannot reach the website from a few \
locations across the US, but it seems to resolve fine now.<br \
clear=all><o:p></o:p></p><div><div><p class=MsoNormal>---<br>Charles \
D'Aoust<o:p></o:p></p></div></div><p \
class=MsoNormal><o:p> </o:p></p></div></div><p \
class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Thu, Sep 5, 2019 \
at 3:35 AM Stephane Bortzmeyer via Outages <<a \
href="mailto:outages@outages.org">outages@outages.org</a>> \
wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC \
1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><p \
class=MsoNormal>On Thu, Sep 05, 2019 at 09:08:48AM +0200,<br> Stephane \
Bortzmeyer via Outages <<a href="mailto:outages@outages.org" \
target="_blank">outages@outages.org</a>> wrote <br> a message of 6 lines \
which said:<br><br>> It seems all name servers of the <a href="http://yahoo.com" \
target="_blank">yahoo.com</a> domain are unresponsive<br>> from most ASes (it \
works in some). Any idea what's going on?<br><br>Confirmed by the company (and by \
many user reports on Twitter):<br><br><a \
href="https://twitter.com/YahooCare/status/1169500570937282560" \
target="_blank">https://twitter.com/YahooCare/status/1169500570937282560</a><br><br>Other \
Verizon services seem affected as well (<a href="http://verizonmedia.com" \
target="_blank">verizonmedia.com</a>,<br><a href="http://huffingtonpost.com" \
target="_blank">huffingtonpost.com</a>) although less severely probably because of \
DNS<br>caching.<br>_______________________________________________<br>Outages mailing \
list<br><a href="mailto:Outages@outages.org" \
target="_blank">Outages@outages.org</a><br><a \
href="https://puck.nether.net/mailman/listinfo/outages" \
target="_blank">https://puck.nether.net/mailman/listinfo/outages</a><o:p></o:p></p></blockquote></div></div></body></html>
_______________________________________________
Outages-discussion mailing list
Outages-discussion@outages.org
https://puck.nether.net/mailman/listinfo/outages-discussion
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic