Slack seems to have fallen over again. 1455 Pacific Time. Please limit METOOs to 3-4 this time thank you.
-george Sent from my iPhone > On Jan 9, 2018, at 12:31 PM, Karl Katzke via Outages <[email protected]> > wrote: > > It looks like this was more of a “whichever node this account is attaching > to” as opposed to a “total system outage” or a “geographic outage” – I am > connected to four slack accounts that I use regularly, and two worked and two > didn’t from the same physical location. Other folks at my own workplace could > connect to our corporate account and use it fully, but could not connect to > other organization accounts that I could connect to. > > Sounds more like a rolling patch situation, or a roll of a patch that went > poorly and needed manual poking to recover from. > > -- > Karl Katzke > > From: Outages <[email protected]> on behalf of Scott Borden via > Outages <[email protected]> > Reply-To: Scott Borden <[email protected]> > Date: Tuesday, January 9, 2018 at 2:14 PM > To: "[email protected]" <[email protected]> > Cc: "[email protected]" <[email protected]> > Subject: Re: [outages] Slack outage > > Back up in Dallas. > > From: Outages [mailto:[email protected]] On Behalf Of Krassimir > Tzvetanov via Outages > Sent: Tuesday, January 09, 2018 14:00 > To: Nathan Coffren > Cc: [email protected] > Subject: Re: [outages] Slack outage > > I was checking every 5-7 minutes. It never gave me an error. > > On Tue, Jan 9, 2018 at 11:57 AM, Nathan Coffren via Outages > <[email protected]> wrote: > Oh the irony. > > On another note, the outage notification on Slack's status page 404s and it's > back to all green. Maybe they're in denial. > > Nate > > On Jan 9, 2018 2:52 PM, "Joshua Delaughter via Outages" <[email protected]> > wrote: > I think all of the “okay stop now” emails are outnumbering the “me too’s” at > this point. > > Sent from my iPhone > > On Jan 9, 2018, at 1:49 PM, Neil Hanlon via Outages <[email protected]> > wrote: > > Please take discussion to outages-discussion, not the main list. This is not > a difficult concept. > > On Jan 9, 2018 14:44, "Chapman, Brad (Contractor-NBCUniversal) via Outages" > <[email protected]> wrote: > Hi Sam, > > I agree that there are a lot of ‘me-too’ responses; however, Slack is a team > chat program hosted in the cloud. If any part of their hosting goes down, it > has the potential to impact a lot of customers. > > --Brad > > From: Outages [mailto:[email protected]] On Behalf Of Sam Kirsch > via Outages > Sent: Tuesday, January 9, 2018 11:34 AM > To: '[email protected]' <[email protected]> > Subject: [EXTERNAL] Re: [outages] Slack outage > > Is slack something other than a team chat program? There’s almost 10 ‘me > too’ responses now that are all useless for what this list is about. Please > move to outage-discussions or at least stop replying here… > > “The primary goal of this mailing list ("outages") is for outages-reporting > that would apply to failures of major communications infrastructure > components having significant traffic-carrying capacity“ > > Pretty sure you can find a subreddit or something to discuss the Slack outage > on now that it’s been posted here once and confirmed. It’s enough. > > Sam Kirsch > Network Administrator > > TeamWorld, Inc. > 498 Conklin Avenue, Binghamton, NY 13903 > T (607) 352-1431 | C (607) 242-3412 | F (607) 770-1153 > [email protected] | www.teamworld.com > > From: Laurent Dumont via Outages [mailto:[email protected]] > Sent: Tuesday, January 9, 2018 2:23 PM > To: [email protected] > Subject: Re: [outages] Slack outage > > Their status page might be down too - or just extremely slow. > > On Tue, Jan 9, 2018 at 2:21 PM, Carlos Alvarez via Outages > <[email protected]> wrote: > Same here, from two ISPs in Phoenix, AZ. > > > On Tue, Jan 9, 2018 at 12:19 PM, Josh Luthman via Outages > <[email protected]> wrote: > The community says "Server Error" and links the status page, which doesn't > report anything at this time. > > https://status.slack.com > > Josh Luthman > Office: 937-552-2340 > Direct: 937-552-2343 > 1100 Wayne St > Suite 1337 > Troy, OH 45373 > > _______________________________________________ > Outages mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/outages > > > > > -- > Carlos Alvarez > 602-368-6403 > > > _______________________________________________ > Outages mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/outages > > > > > -- > Laurent Dumont > Spécialiste réseau / Network specialist > Fibrenoire - www.fibrenoire.ca > A: 550 > , avenue > Beaumont, > bureau > 320, > Montréal (Québec) > H3N 1V1 > T. 514 907-3002 x132 > C.438-394-9603 > [email protected] > Twitter: Twitter Fibrenoire > > --Note de confidentialité-- > > Ce message électronique et toutes pièces jointes contiennent des informations > privilégiées et confidentielles. Si vous n'êtes pas le destinataire prévu, il > est strictement interdit d'utiliser, de copier ou divulguer les informations > ainsi transmises; merci d'en aviser l'expéditeur et de les supprimer de votre > ordinateur. > > --Confidentiality Note-- > > This email message and any attachments contain privileged and confidential > information. If you are not the intended recipient, your use, copying or > disclosure of this information is prohibited; please contact the sender and > delete the material from your computer. > > _______________________________________________ > Outages mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/outages > > _______________________________________________ > Outages mailing list > [email protected] > https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DwICAg&c=I2efTSIilX30_3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mzozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWufE&s=Ew9QPPwDapO941BpXODiG3edVhzy6YPE_kNGRU88RU0&e= > IMPORTANT/CONFIDENTIAL: This e-mail transmission, and any documents, files or > previous e-mail messages attached to it, may be privileged, confidential, > and/or exempt from disclosure by federal and state law. If you are not the > intended recipient, you are hereby notified that any disclosure, copying, > distribution or use of any of the information contained in or attached to > this message is STRICTLY PROHIBITED. If you have received this transmission > in error, please immediately notify us by reply e-mail or by telephone at > (337) 269-9566, and destroy the original transmission and its attachments > without reading them or retaining any copies. > > _______________________________________________ > Outages mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/outages > > > _______________________________________________ > Outages mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/outages > > > > > This message and any attached files contain confidential information and is > intended only for the individual named. If you are not the named addressee > you should not disseminate, distribute or copy this e-mail. Please notify the > sender immediately by e-mail if you have received this e-mail by mistake and > delete this e-mail from your system. E-mail transmission cannot be guaranteed > to be secure or without error as information could be intercepted, corrupted, > lost, destroyed, arrive late or incomplete, or contain viruses. The sender > therefore does not accept liability for any errors or omissions in the > contents of this message, which arise as a result of e-mail transmission. If > verification is required please request a hard-copy version. > _______________________________________________ > Outages mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list [email protected] https://puck.nether.net/mailman/listinfo/outages
