<div dir="auto">There was definitely a reset of Auth. Seen here in the middle east. Whether that was intentional eg security patch similar to Google I'm not sure but it recovered after a few minutes and looks okay since</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 6 Mar 2024, 00:17 Aaron Hope via Outages, <<a href="mailto:outages@outages.org">outages@outages.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)">
GAH! Too many emails about Facebook today! Now I got bit!</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)">
Sorry all :)</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)">
Aaron</div>
<div id="m_4410075299482183942appendonsend"></div>
<hr style="display:inline-block;width:98%">
<div id="m_4410075299482183942divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Outages <<a href="mailto:outages-bounces@outages.org" target="_blank" rel="noreferrer">outages-bounces@outages.org</a>> on behalf of Aaron Hope via Outages <<a href="mailto:outages@outages.org" target="_blank" rel="noreferrer">outages@outages.org</a>><br>
<b>Sent:</b> Tuesday, March 5, 2024 3:14 PM<br>
<b>To:</b> Ross Tajvar <<a href="mailto:ross@tajvar.io" target="_blank" rel="noreferrer">ross@tajvar.io</a>>; Jay Ashworth <<a href="mailto:jra@baylink.com" target="_blank" rel="noreferrer">jra@baylink.com</a>><br>
<b>Cc:</b> <a href="mailto:outages@outages.org" target="_blank" rel="noreferrer">outages@outages.org</a> <<a href="mailto:outages@outages.org" target="_blank" rel="noreferrer">outages@outages.org</a>><br>
<b>Subject:</b> Re: [outages] After-Action Report: Facebook/Meta outage</font>
<div> </div>
</div>
<div dir="ltr">
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)">
We are not renewing Splunk. We have migrated to Azure Sentinel for logging and monitoring.</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)">
Aaron</div>
<div id="m_4410075299482183942x_appendonsend"></div>
<hr style="display:inline-block;width:98%">
<div id="m_4410075299482183942x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Outages <<a href="mailto:outages-bounces@outages.org" target="_blank" rel="noreferrer">outages-bounces@outages.org</a>> on behalf of Jay Ashworth via Outages <<a href="mailto:outages@outages.org" target="_blank" rel="noreferrer">outages@outages.org</a>><br>
<b>Sent:</b> Tuesday, March 5, 2024 2:59 PM<br>
<b>To:</b> Ross Tajvar <<a href="mailto:ross@tajvar.io" target="_blank" rel="noreferrer">ross@tajvar.io</a>><br>
<b>Cc:</b> <a href="mailto:outages@outages.org" target="_blank" rel="noreferrer">outages@outages.org</a> <<a href="mailto:outages@outages.org" target="_blank" rel="noreferrer">outages@outages.org</a>><br>
<b>Subject:</b> Re: [outages] After-Action Report: Facebook/Meta outage</font>
<div> </div>
</div>
<div>
<div dir="auto">Yeah, but I shouldn't have gotten bitten. I'm supposed to be holding myself to a higher standard, as a moderator of this particular group.</div>
<br>
<br>
<div>
<div dir="auto">On March 5, 2024 2:58:00 PM EST, Ross Tajvar <<a href="mailto:ross@tajvar.io" target="_blank" rel="noreferrer">ross@tajvar.io</a>> wrote:</div>
<blockquote style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">Indeed - this happens every time facebook has a major outage, because they stopped putting out posts explaining what happened and because people tend not to look too closely before spreading links that look plausible.</div>
<br>
<div>
<div dir="ltr">On Tue, Mar 5, 2024 at 2:56 PM Jay R. Ashworth via Outages <<a href="mailto:outages@outages.org" target="_blank" rel="noreferrer">outages@outages.org</a>> wrote:<br>
</div>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Well, when I pulled up the link from Ross's mobile version, it had comments<br>
under it from 10/22; if those people didn't know where to go either... :-}<br>
<br>
----- Original Message -----<br>
> From: "Damian Menscher" <<a href="mailto:damian@google.com" target="_blank" rel="noreferrer">damian@google.com</a>><br>
> To: "jra" <<a href="mailto:jra@baylink.com" target="_blank" rel="noreferrer">jra@baylink.com</a>><br>
> Cc: <a href="mailto:outages@outages.org" target="_blank" rel="noreferrer">outages@outages.org</a><br>
> Sent: Tuesday, March 5, 2024 2:16:33 PM<br>
> Subject: Re: [outages] After-Action Report: Facebook/Meta outage<br>
<br>
> It clearly *is* from 2010:<br>
> <a href="https://engineering.fb.com/2010/09/23/uncategorized/more-details-on-today-s-o" rel="noreferrer noreferrer" target="_blank">
https://engineering.fb.com/2010/09/23/uncategorized/more-details-on-today-s-o</a><br>
> <br>
> Damian<br>
> <br>
> On Tue, Mar 5, 2024 at 11:13 AM Jay R. Ashworth via Outages <<br>
> <a href="mailto:outages@outages.org" target="_blank" rel="noreferrer">outages@outages.org</a>> wrote:<br>
> <br>
>> Well, it seems equivocal whether that's about *this* outage<br>
>> rather than an earlier one -- though it's clearly not from 2010.<br>
>><br>
>> More to follow.<br>
>><br>
>> Cheers,<br>
>> -- jra<br>
>><br>
>> ----- Original Message -----<br>
>> > From: "Jay R. Ashworth via Outages" <<a href="mailto:outages@outages.org" target="_blank" rel="noreferrer">outages@outages.org</a>><br>
>> > To: <a href="mailto:outages@outages.org" target="_blank" rel="noreferrer">outages@outages.org</a><br>
>> > Sent: Tuesday, March 5, 2024 1:57:24 PM<br>
>> > Subject: [outages] After-Action Report: Facebook/Meta outage<br>
>><br>
>> > [ I can't set the header from Zimbra, but please, Reply-To: -discuss ]<br>
>> ><br>
>> > Here's a link to FB's AAR about this morning's 70-minuteish outage.<br>
>> ><br>
>> > It's been pointed out to me that this affected other services as well, if<br>
>> > they are an OAuth client, and you chose to use FB's OAuth service to<br>
>> create<br>
>> > your account there.<br>
>> ><br>
>> ><br>
>> <a href="https://m.facebook.com/nt/screen/?params=%7B%22note_id%22%3A10158791436142200%7D&path=%2Fnotes%2Fnote%2F" rel="noreferrer noreferrer" target="_blank">
https://m.facebook.com/nt/screen/?params=%7B%22note_id%22%3A10158791436142200%7D&path=%2Fnotes%2Fnote%2F</a><br>
>> ><br>
>> > [ Hat-tip: Jorge Amodio ]<br>
>> ><br>
>> > Cheers,<br>
>> > -- jra<br>
>> ><br>
>> > --<br>
>> > Jay R. Ashworth Baylink<br>
>> <a href="mailto:jra@baylink.com" target="_blank" rel="noreferrer">jra@baylink.com</a><br>
>> > Designer The Things I Think<br>
>> RFC 2100<br>
>> > Ashworth & Associates <a href="http://www.bcp38.info" rel="noreferrer noreferrer" target="_blank">http://www.bcp38.info</a> 2000 Land<br>
>> Rover DII<br>
>> > St Petersburg FL USA BCP38: Ask For It By Name! +1 727<br>
>> 647 1274 <(727)%20647-1274><br>
>> > _______________________________________________<br>
>> > Outages mailing list<br>
>> > <a href="mailto:Outages@outages.org" target="_blank" rel="noreferrer">Outages@outages.org</a><br>
>> > <a href="https://puck.nether.net/mailman/listinfo/outages" rel="noreferrer noreferrer" target="_blank">
https://puck.nether.net/mailman/listinfo/outages</a><br>
>><br>
>> --<br>
>> Jay R. Ashworth Baylink<br>
>> <a href="mailto:jra@baylink.com" target="_blank" rel="noreferrer">jra@baylink.com</a><br>
>> Designer The Things I Think RFC<br>
>> 2100<br>
>> Ashworth & Associates <a href="http://www.bcp38.info" rel="noreferrer noreferrer" target="_blank">http://www.bcp38.info</a> 2000 Land<br>
>> Rover DII<br>
>> St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647<br>
>> 1274 <(727)%20647-1274><br>
>> _______________________________________________<br>
>> Outages mailing list<br>
>> <a href="mailto:Outages@outages.org" target="_blank" rel="noreferrer">Outages@outages.org</a><br>
>> <a href="https://puck.nether.net/mailman/listinfo/outages" rel="noreferrer noreferrer" target="_blank">
https://puck.nether.net/mailman/listinfo/outages</a><br>
<br>
-- <br>
Jay R. Ashworth Baylink <a href="mailto:jra@baylink.com" target="_blank" rel="noreferrer">jra@baylink.com</a><br>
Designer The Things I Think RFC 2100<br>
Ashworth & Associates <a href="http://www.bcp38.info" rel="noreferrer noreferrer" target="_blank">http://www.bcp38.info</a> 2000 Land Rover DII<br>
St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274<br>
_______________________________________________<br>
Outages mailing list<br>
<a href="mailto:Outages@outages.org" target="_blank" rel="noreferrer">Outages@outages.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/outages" rel="noreferrer noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/outages</a><br>
</blockquote>
</div>
</blockquote>
</div>
<div dir="auto">
<div>-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.</div>
</div>
</div>
WARNING CONCERNING CONFIDENTIALITY This email message, including any attachments, is for the sole use by its intended recipient or recipients and may contain confidential and privileged information. Any unauthorized review, use, disclosure, or distribution
is prohibited. If you are not the intended recipient of this message, please immediately notify the sender and delete the original message without making a copy.
</div>
WARNING CONCERNING CONFIDENTIALITY This email message, including any attachments, is for the sole use by its intended recipient or recipients and may contain confidential and privileged information. Any unauthorized review, use, disclosure, or distribution
is prohibited. If you are not the intended recipient of this message, please immediately notify the sender and delete the original message without making a copy.
</div>
_______________________________________________<br>
Outages mailing list<br>
<a href="mailto:Outages@outages.org" target="_blank" rel="noreferrer">Outages@outages.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/outages" rel="noreferrer noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/outages</a><br>
</blockquote></div>
<br>
<div><font color="#808080" size="1"><b style="font-family:Slack-Lato,appleLogo,sans-serif;background-color:white">CONFIDENTIALITY AND DISCLAIMER NOTICE: </b></font></div><div><font color="#808080" size="1"><span style="font-family:Slack-Lato,appleLogo,sans-serif;background-color:white">This email is intended only for the person to whom it is addressed and/or otherwise authorized personnel. The information contained herein and attached is confidential. If you are not the intended recipient, please be advised that viewing this message and any attachments, as well as copying, forwarding, printing, and disseminating any information related to this email is prohibited, and that you should not take any action based on the content of this email and/or its attachments. If you received this message in error, please contact the sender and destroy all copies of this email and any attachment. Please note that the views and opinions expressed herein are solely those of the author and do not necessarily reflect those of the company. While antivirus protection tools have been employed, you should check this email and attachments for the presence of viruses. No warranties or assurances are made in relation to the safety and content of this email and attachments. The Company accepts no liability for any damage caused by any virus transmitted by or contained in this email and attachments. No liability is accepted for any consequences arising from this email.</span></font></div><div><font style="background-color:white" color="#808080" size="1"><br></font></div><div><font style="background-color:white" color="#808080" size="1"><b style="font-family:Slack-Lato,appleLogo,sans-serif">AVIS DE CONFIDENTIALITÉ ET DE NON RESPONSABILITE</b><span style="font-family:Slack-Lato,appleLogo,sans-serif"> : </span></font></div><div><font color="#808080" size="1"><span style="font-family:Slack-Lato,appleLogo,sans-serif;background-color:white">Ce courriel, ainsi que toute pièce jointe, est confidentiel et peut être protégé par le secret professionnel. Si vous n’en êtes pas le destinataire visé, veuillez en aviser l’expéditeur immédiatement et le supprimer. Vous ne devez pas le copier, ni l’utiliser à quelque fin que ce soit, ni divulguer son contenu à qui que ce soit. BSO se réserve le droit de contrôler toute transmission qui passe par son réseau. Veuillez noter que les opinions exprimées dans cet e-mail sont uniquement celles de l'auteur et ne reflètent pas nécessairement celles de la société. Bien que des outils de protection antivirus aient été utilisés, vous devez vérifier cet e-mail et les pièces jointes pour toute présence de virus. Aucune garantie ou assurance n'est donnée concernant la sécurité et le contenu de cet e-mail et de ses pièces jointes. La Société décline toute responsabilité pour tout dommage causé par tout virus transmis par ou contenu dans cet e-mail et ses pièces jointes. Aucune responsabilité n'est acceptée pour les conséquences découlant de cet e-mail.</span></font></div>