[outages] Slack outage

[Neil Hanlon]

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"
<outages at outages.org> 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:outages-bounces at outages.org] *On Behalf Of *Sam
> Kirsch via Outages
> *Sent:* Tuesday, January 9, 2018 11:34 AM
> *To:* 'outages at outages.org' <outages at outages.org>
> *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
>
> skirsch at teamworld.com | www.teamworld.com
>
>
>
> *From:* Laurent Dumont via Outages [mailto:outages at outages.org
> <outages at outages.org>]
> *Sent:* Tuesday, January 9, 2018 2:23 PM
> *To:* outages at outages.org
> *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 <
> outages at outages.org> wrote:
>
> Same here, from two ISPs in Phoenix, AZ.
>
>
>
>
>
> On Tue, Jan 9, 2018 at 12:19 PM, Josh Luthman via Outages <
> outages at outages.org> 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 <(937)%20552-2340>
> Direct: 937-552-2343 <(937)%20552-2343>
> 1100 Wayne St
> Suite 1337
> Troy, OH 45373
>
>
>
> _______________________________________________
> Outages mailing list
> Outages at outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
>
>
>
>
> --
>
> Carlos Alvarez
>
> 602-368-6403
>
>
>
>
> _______________________________________________
> Outages mailing list
> Outages at outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
>
>
>
>
> --
>
> *Laurent Dumont*
>
> *Spécialiste réseau / Network specialist*
>
> *Fibre**noire* - www.fibrenoire.ca
>
> A: 550
>
> ​, avenue
>
> Beaumont,
>
> ​bureau
>
>  320,
>
> Montréal (Québec)
>
>  H3N 1V1
>
> T. 514 907-3002 x132
>
> C.438-394-9603
>
> ldumont at fibrenoire.ca <farchambault at fibrenoire.ca>
>
> Twitter: Twitter Fibrenoire <https://twitter.com/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
> 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/attachments/20180109/aba102f4/attachment.htm>