<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<div>I agree in the canary in the coal mine aspect. When I signed up I expected that to some degree but with more of a backbone/service provider bent. I have plenty of filtering options available but filtering said canaries can be problematic if you don’t know
which colors of canaries you are going to get. :) </div>
<div><br>
</div>
<div>I worded the Slack statement poorly; my bad. My problem with the Slack stuff was the 2hrs+ later “me to” or “its working” messages after Slack’s own status page noted they had a problem and had rolled back to fix it. Slack is critical infrastructure for
some organizations and any outage for that kind of cloud service is going to generate calls to my call center if it goes on longer than the 15 minutes it takes to get from end user to technical contact to our help desk. </div>
<div><br>
</div>
<div>AWS, Azure, & Google are absolutely a reason for message; you are going to hear about it from your users/clients in a damn hurry if one of those is having a moment these days. An outage with those services now looks almost exactly the same to your networks
as guy standing next to the Big Yellow Cable Finder with a 288 count fiber hanging from the bucket saying “ooopsy” depending on your or your client’s needs. :) </div>
<div><br>
</div>
<div>Thanks for the input everybody!</div>
<div>~Jason</div>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>John Starta <<a href="mailto:john@starta.org">john@starta.org</a>><br>
<span style="font-weight:bold">Date: </span>Thursday, March 9, 2017 at 12:54 PM<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:outages-discussion@outages.org">outages-discussion@outages.org</a>" <<a href="mailto:outages-discussion@outages.org">outages-discussion@outages.org</a>><br>
<span style="font-weight:bold">Cc: </span>Peter Beckman <<a href="mailto:beckman@angryox.com">beckman@angryox.com</a>>, Jason Grider <<a href="mailto:jgrider@asc.edu">jgrider@asc.edu</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [outages] [Outages-discussion] Outages Message List Scope<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div>
<div>As you might expect there are a variety of opinions on what’s important enough to merit an outages mailing list message. I personally don’t have an issue with smaller or website specific outages being reported. I view them as potential canaries in the
coal mine. For instance, an issue with Slack can signal an AWS problem which might not have been registered on Amazon’s dashboard yet. (Given what resides on AWS, Azure, and Google Cloud these days I personally think they qualify as major [communications]
infrastructure.)</div>
<div><br>
</div>
<div>Everyone on this mailing list should have the technical skill to know how to utilize the filtering capabilities of their mail clients and/or server. If you don’t like hearing about Slack outages, for instance, then create filters to parse incoming mailing
list messages for only keywords important to you. I would recommend using server-side filters so that both your mobile[1] and desktop can benefit. If server-side filters aren’t available to you, then consider getting a Gmail account which does and subscribe
to the outages list from there.</div>
<div><br>
</div>
<div>Simply put: Why must everyone on the list be deprived of potentially useful information just because some don’t / won’t learn their tools to benefit themselves.</div>
<div><br>
</div>
<div>John Starta</div>
<div><br>
</div>
<div>[1] A frequent complaint of many is X outage shouldn’t be reported to this list — to paraphrase: “stop filling the inbox on my mobile with outages I find unimportant.”</div>
<div><br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>On Mar 9, 2017, at 10:58 AM, Peter Beckman <<a href="mailto:beckman@angryox.com">beckman@angryox.com</a>> wrote:</div>
<div></div>
<div>Agreed, and thanks for saying something.</div>
<div></div>
<div>Though, from some standpoints, Slack being down could be considered a</div>
<div>communications failure... but I agree, clarification should be given.</div>
<div></div>
<div>Appropriate posts (based on my reading of the "Mission Statement"):</div>
<div></div>
<div> * Network link down or packet loss (show your work)</div>
<div> * Telecommunications issue (voice, video, SMS)</div>
<div> * BGP flaps</div>
<div> * DDOS affecting network latency</div>
<div> * generally packet delivery and receipt related</div>
<div></div>
<div>Maybe appropriate:</div>
<div></div>
<div> * Large cloud/service provider outage (some communication may be</div>
<div> dependent); e.g recent AWS S3 US-East issue, CloudFlare Security issue</div>
<div> * AT&T 911 Outage</div>
<div> * Mobile Network outage/issue</div>
<div> * MicroTik Zero Day</div>
<div></div>
<div>Not appropriate:</div>
<div></div>
<div> * Web service is down (endpoint related) e.g. Slack, Twitter, Amazon</div>
<div> retail, Facebook</div>
<div> * "I'm seeing a problem, are you?" posts -- either know or don't post</div>
<div> * "Me too" posts unless you are adding to the discussion with</div>
<div> additional, not before seen detail</div>
<div> * After-the-fact posts "Yeah, I saw that happen"</div>
<div></div>
<div>I do not represent the Outages list, this is my personal take on what</div>
<div>should or shouldn't be here.</div>
<div></div>
<div>Oh, and this should go to -discussion.</div>
<div></div>
<div>On Thu, 9 Mar 2017, Jason Grider via Outages wrote:</div>
<div></div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>Is a 504 – Gateway Error something that falls into this mailing list’s</div>
<div>scope? I’m asking because I’ve only been subscribed for a few days and</div>
<div>between a 10 minute outage at Slack generating ~25 messages over the</div>
<div>course of 5 hours and an (most likely internal to Invidia) HTTP server</div>
<div>error I’m wondering how much filtering I may need to put in place to get</div>
<div>the pieces of information I need from the chaff of events that have a</div>
<div>limited blast radius. There is no disrespect intended to anybody about</div>
<div>what has been sent to the list. I’m just trying to set my expectations in</div>
<div>line with the data I’ve asked for. :)</div>
<div></div>
<div>From the signup page: <a href="https://puck.nether.net/mailman/listinfo/outages">
https://puck.nether.net/mailman/listinfo/outages</a> (bold is my emphasis)</div>
<div>"The primary goal of this mailing list ("outages") is for</div>
<div>outages-reporting that would apply to failures of major communications</div>
<div>infrastructure components having significant traffic-carrying capacity,</div>
<div>similar to what FCC provided prior to 9/11 days but they seem to have</div>
<div>pulled back due to terrorism concerns. Some also believe that LEC's and</div>
<div>IXC's also like this model as they no longer have to air their dirty</div>
<div>laundry. Then again, this mailing list is not about making anyone look</div>
<div>bad, its all about information sharing and keeping network operators &</div>
<div>end users abreast on the situation as close to real-time information as</div>
<div>possible in order to assess and respond to major outage such as routing</div>
<div>voice/data via different carriers which may directly or indirectly impact</div>
<div>us and our customers. A reliable communications network is essential in</div>
<div>times of crisis.</div>
<div></div>
<div>The purpose of this list is to have a central place to lookup and report</div>
<div>so that end users & network operators know why their services (e-mail,</div>
<div>phones, etc) went down eliminating the need to open tons of trouble</div>
<div>tickets during a major event. One master ticket - such as fiber cut</div>
<div>affect xxx OC48's would suffice. We hope this would empower users and</div>
<div>network operators to post such events so that everyone could benefit from</div>
<div>it. “</div>
<div></div>
<div>Then again “OC48” may date that statement a little bit. :)</div>
<div></div>
<div>“Thank you and have a great day!” I say from the confines of my shiny</div>
<div>silver flame suit.</div>
<div>Jason Grider</div>
<div></div>
<div></div>
</blockquote>
<div></div>
<div>---------------------------------------------------------------------------</div>
<div>Peter Beckman Internet Guy</div>
<div><a href="mailto:beckman@angryox.com">beckman@angryox.com</a>
<a href="http://www.angryox.com/">http://www.angryox.com/</a></div>
<div>---------------------------------------------------------------------------</div>
</blockquote>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
</blockquote>
</span>
</body>
</html>