Confirmed from Chambersburg PA and NYC. Eric Franson Senior Corp IT Engineer Etsy On Tue, Jan 9, 2018 at 2:20 PM, Peter Kristolaitis via Outages < outages@outages.org> wrote:

Seeing the same thing in Ottawa, Canada.

On 2018-01-09 02:19 PM, Josh Luthman via Outages 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 listOutages@outages.orghttps://puck.nether.net/mailman/listinfo/outages

_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages

I’m starting to see things reconnect.

On Jan 9, 2018, at 2:23 PM, Laurent Dumont via Outages <outages@outages.org> wrote:

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@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@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 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373

_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages

-- Carlos Alvarez 602-368-6403

_______________________________________________ Outages mailing list Outages@outages.org 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 ldumont@fibrenoire.ca 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 Outages@outages.org https://puck.nether.net/mailman/listinfo/outages

This is the incident URL to follow up: https://status.slack.com/2018-01/d8cf1517de9ecfa8cea On Tue, Jan 9, 2018 at 11:38 AM Sam Kirsch via Outages <outages@outages.org> wrote:

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@teamworld.com | www.teamworld.com

*From:* Laurent Dumont via Outages [mailto:outages@outages.org] *Sent:* Tuesday, January 9, 2018 2:23 PM *To:* outages@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@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@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@outages.org https://puck.nether.net/mailman/listinfo/outages

--

Carlos Alvarez

602-368-6403 <(602)%20368-6403>

_______________________________________________ Outages mailing list Outages@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 <(514)%20907-3002>

C.438-394-9603 <(438)%20394-9603>

ldumont@fibrenoire.ca <farchambault@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@outages.org https://puck.nether.net/mailman/listinfo/outages

-- Denis Malinovskiy Software Engineer, drchrono

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@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@outages.org] *On Behalf Of *Sam Kirsch via Outages *Sent:* Tuesday, January 9, 2018 11:34 AM *To:* 'outages@outages.org' <outages@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@teamworld.com | www.teamworld.com

*From:* Laurent Dumont via Outages [mailto:outages@outages.org <outages@outages.org>] *Sent:* Tuesday, January 9, 2018 2:23 PM *To:* outages@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@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@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@outages.org https://puck.nether.net/mailman/listinfo/outages

--

Carlos Alvarez

602-368-6403

_______________________________________________ Outages mailing list Outages@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@fibrenoire.ca <farchambault@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@outages.org https://puck.nether.net/mailman/listinfo/outages

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" <outages@outages.org> 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 <outages@outages.org> 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" <outages@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@outages.org] *On Behalf Of *Sam Kirsch via Outages *Sent:* Tuesday, January 9, 2018 11:34 AM *To:* 'outages@outages.org' <outages@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@teamworld.com | www.teamworld.com <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.teamworld.com_&d=DwMFaQ&c=I2efTSIilX30_3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mzozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWufE&s=ZBcznTc1cf4cNvfzscbJT8jFxTCQEUV5jM5gYTHf1B4&e=>

*From:* Laurent Dumont via Outages [mailto:outages@outages.org <outages@outages.org>] *Sent:* Tuesday, January 9, 2018 2:23 PM *To:* outages@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@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@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 <https://urldefense.proofpoint.com/v2/url?u=https-3A__status.slack.com&d=DwMFaQ&c=I2efTSIilX30_3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mzozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWufE&s=jEdWjAYTE25s1plpNBhgYquUjkwl3ZkKi4z05pjeif8&e=>

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@outages.org https://puck.nether.net/mailman/listinfo/outages <https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DwMFaQ&c=I2efTSIilX30_3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mzozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWufE&s=Ew9QPPwDapO941BpXODiG3edVhzy6YPE_kNGRU88RU0&e=>

--

Carlos Alvarez

602-368-6403 <(602)%20368-6403>

_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages <https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DwMFaQ&c=I2efTSIilX30_3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mzozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWufE&s=Ew9QPPwDapO941BpXODiG3edVhzy6YPE_kNGRU88RU0&e=>

--

*Laurent Dumont*

*Spécialiste réseau / Network specialist*

*Fibre**noire* - www.fibrenoire.ca <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.fibrenoire.ca_&d=DwMFaQ&c=I2efTSIilX30_3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mzozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWufE&s=WD__vFH3y4NjQlfv7OemfI5WdYav9zqf5QXbL7NIJ2o&e=>

A: 550

​, avenue

Beaumont,

​bureau

320,

Montréal (Québec)

H3N 1V1

T. 514 907-3002 x132 <(514)%20907-3002>

C.438-394-9603 <(438)%20394-9603>

ldumont@fibrenoire.ca <farchambault@fibrenoire.ca>

Twitter: Twitter Fibrenoire <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_fibrenoire&d=DwMFaQ&c=I2efTSIilX30_3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mzozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWufE&s=OkarkaThgsPiVjzkTHj3RHvgsa2LOdSEP7J4XdN0Q-E&e=>

*--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@outages.org https://puck.nether.net/mailman/listinfo/outages <https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DwMFaQ&c=I2efTSIilX30_3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mzozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWufE&s=Ew9QPPwDapO941BpXODiG3edVhzy6YPE_kNGRU88RU0&e=>

_______________________________________________ Outages mailing list Outages@outages.org 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 Outages@outages.org https://puck.nether.net/mailman/listinfo/outages

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 < outages@outages.org> 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" < outages@outages.org> 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 <outages@outages.org> 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" <outages@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@outages.org] *On Behalf Of *Sam Kirsch via Outages *Sent:* Tuesday, January 9, 2018 11:34 AM *To:* 'outages@outages.org' <outages@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@teamworld.com | www.teamworld.com <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.teamworld.com_&d=DwMFaQ&c=I2efTSIilX30_3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mzozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWufE&s=ZBcznTc1cf4cNvfzscbJT8jFxTCQEUV5jM5gYTHf1B4&e=>

*From:* Laurent Dumont via Outages [mailto:outages@outages.org <outages@outages.org>] *Sent:* Tuesday, January 9, 2018 2:23 PM *To:* outages@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@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@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 <https://urldefense.proofpoint.com/v2/url?u=https-3A__status.slack.com&d=DwMFaQ&c=I2efTSIilX30_3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mzozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWufE&s=jEdWjAYTE25s1plpNBhgYquUjkwl3ZkKi4z05pjeif8&e=>

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@outages.org https://puck.nether.net/mailman/listinfo/outages <https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DwMFaQ&c=I2efTSIilX30_3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mzozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWufE&s=Ew9QPPwDapO941BpXODiG3edVhzy6YPE_kNGRU88RU0&e=>

--

Carlos Alvarez

602-368-6403 <(602)%20368-6403>

_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages <https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DwMFaQ&c=I2efTSIilX30_3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mzozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWufE&s=Ew9QPPwDapO941BpXODiG3edVhzy6YPE_kNGRU88RU0&e=>

--

*Laurent Dumont*

*Spécialiste réseau / Network specialist*

*Fibre**noire* - www.fibrenoire.ca <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.fibrenoire.ca_&d=DwMFaQ&c=I2efTSIilX30_3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mzozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWufE&s=WD__vFH3y4NjQlfv7OemfI5WdYav9zqf5QXbL7NIJ2o&e=>

A: 550

​, avenue

Beaumont,

​bureau

320,

Montréal (Québec)

H3N 1V1

T. 514 907-3002 x132 <(514)%20907-3002>

C.438-394-9603 <(438)%20394-9603>

ldumont@fibrenoire.ca <farchambault@fibrenoire.ca>

Twitter: Twitter Fibrenoire <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_fibrenoire&d=DwMFaQ&c=I2efTSIilX30_3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mzozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWufE&s=OkarkaThgsPiVjzkTHj3RHvgsa2LOdSEP7J4XdN0Q-E&e=>

*--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@outages.org https://puck.nether.net/mailman/listinfo/outages <https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DwMFaQ&c=I2efTSIilX30_3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mzozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWufE&s=Ew9QPPwDapO941BpXODiG3edVhzy6YPE_kNGRU88RU0&e=>

_______________________________________________ Outages mailing list Outages@outages.org https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.ne ther.net_mailman_listinfo_outages&d=DwICAg&c=I2efTSIilX30_ 3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mz ozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWu fE&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 Outages@outages.org https://puck.nether.net/mailman/listinfo/outages

_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages

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 <outages-bounces@outages.org> on behalf of Scott Borden via Outages <outages@outages.org> Reply-To: Scott Borden <sborden@hosting.com> Date: Tuesday, January 9, 2018 at 2:14 PM To: "maillists@krassi.biz" <maillists@krassi.biz> Cc: "outages@outages.org" <outages@outages.org> Subject: Re: [outages] Slack outage Back up in Dallas. From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Krassimir Tzvetanov via Outages Sent: Tuesday, January 09, 2018 14:00 To: Nathan Coffren Cc: outages@outages.org 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 <outages@outages.org<mailto:outages@outages.org>> 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" <outages@outages.org<mailto:outages@outages.org>> 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 <outages@outages.org<mailto:outages@outages.org>> 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" <outages@outages.org<mailto:outages@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@outages.org<mailto:outages-bounces@outages.org>] On Behalf Of Sam Kirsch via Outages Sent: Tuesday, January 9, 2018 11:34 AM To: 'outages@outages.org<mailto:outages@outages.org>' <outages@outages.org<mailto:outages@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<tel:(607)%20352-1431> | C (607) 242-3412<tel:(607)%20242-3412> | F (607) 770-1153<tel:(607)%20770-1153> skirsch@teamworld.com<mailto:skirsch@teamworld.com> | www.teamworld.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.teamworld.com_&d=DwMFaQ&c=I2efTSIilX30_3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mzozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWufE&s=ZBcznTc1cf4cNvfzscbJT8jFxTCQEUV5jM5gYTHf1B4&e=> From: Laurent Dumont via Outages [mailto:outages@outages.org] Sent: Tuesday, January 9, 2018 2:23 PM To: outages@outages.org<mailto:outages@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@outages.org<mailto:outages@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@outages.org<mailto:outages@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<https://urldefense.proofpoint.com/v2/url?u=https-3A__status.slack.com&d=DwMFaQ&c=I2efTSIilX30_3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mzozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWufE&s=jEdWjAYTE25s1plpNBhgYquUjkwl3ZkKi4z05pjeif8&e=> Josh Luthman Office: 937-552-2340<tel:(937)%20552-2340> Direct: 937-552-2343<tel:(937)%20552-2343> 1100 Wayne St Suite 1337 Troy, OH 45373 _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages<https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DwMFaQ&c=I2efTSIilX30_3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mzozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWufE&s=Ew9QPPwDapO941BpXODiG3edVhzy6YPE_kNGRU88RU0&e=> -- Carlos Alvarez 602-368-6403<tel:(602)%20368-6403> _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages<https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DwMFaQ&c=I2efTSIilX30_3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mzozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWufE&s=Ew9QPPwDapO941BpXODiG3edVhzy6YPE_kNGRU88RU0&e=> -- Laurent Dumont Spécialiste réseau / Network specialist Fibrenoire - www.fibrenoire.ca<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.fibrenoire.ca_&d=DwMFaQ&c=I2efTSIilX30_3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mzozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWufE&s=WD__vFH3y4NjQlfv7OemfI5WdYav9zqf5QXbL7NIJ2o&e=> A: 550 ​, avenue Beaumont, ​bureau 320, Montréal (Québec) H3N 1V1 T. 514 907-3002 x132<tel:(514)%20907-3002> C.438-394-9603<tel:(438)%20394-9603> ldumont@fibrenoire.ca<mailto:farchambault@fibrenoire.ca> Twitter: Twitter Fibrenoire<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_fibrenoire&d=DwMFaQ&c=I2efTSIilX30_3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mzozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWufE&s=OkarkaThgsPiVjzkTHj3RHvgsa2LOdSEP7J4XdN0Q-E&e=> --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@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages<https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DwMFaQ&c=I2efTSIilX30_3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mzozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWufE&s=Ew9QPPwDapO941BpXODiG3edVhzy6YPE_kNGRU88RU0&e=> _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman... 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<tel:(337)%20269-9566>, and destroy the original transmission and its attachments without reading them or retaining any copies. _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> 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.

I am in four slack teams and all of them are connecting fine. On 1/9/18 3:48 PM, George William Herbert via Outages wrote:

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 <outages@outages.org <mailto:outages@outages.org>> 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 <outages-bounces@outages.org <mailto:outages-bounces@outages.org>> on behalf of Scott Borden via Outages <outages@outages.org <mailto:outages@outages.org>> *Reply-To: *Scott Borden <sborden@hosting.com <mailto:sborden@hosting.com>> *Date: *Tuesday, January 9, 2018 at 2:14 PM *To: *"maillists@krassi.biz <mailto:maillists@krassi.biz>" <maillists@krassi.biz <mailto:maillists@krassi.biz>> *Cc: *"outages@outages.org <mailto:outages@outages.org>" <outages@outages.org <mailto:outages@outages.org>> *Subject: *Re: [outages] Slack outage

Back up in Dallas.

*From:*Outages [mailto:outages-bounces@outages.org] *On Behalf Of *Krassimir Tzvetanov via Outages *Sent:* Tuesday, January 09, 2018 14:00 *To:* Nathan Coffren *Cc:* outages@outages.org <mailto:outages@outages.org> *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 <outages@outages.org <mailto:outages@outages.org>> 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" <outages@outages.org <mailto:outages@outages.org>> 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 <outages@outages.org <mailto:outages@outages.org>> 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" <outages@outages.org <mailto:outages@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@outages.org <mailto:outages-bounces@outages.org>] *On Behalf Of *Sam Kirsch via Outages *Sent:* Tuesday, January 9, 2018 11:34 AM *To:* 'outages@outages.org <mailto:outages@outages.org>' <outages@outages.org <mailto:outages@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 <tel:(607)%20352-1431> | C (607) 242-3412 <tel:(607)%20242-3412> | F (607) 770-1153 <tel:(607)%20770-1153>

skirsch@teamworld.com <mailto:skirsch@teamworld.com>| www.teamworld.com <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.teamworld.com_&d=DwMFaQ&c=I2efTSIilX30_3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mzozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWufE&s=ZBcznTc1cf4cNvfzscbJT8jFxTCQEUV5jM5gYTHf1B4&e=>

*From:*Laurent Dumont via Outages [mailto:outages@outages.org] *Sent:* Tuesday, January 9, 2018 2:23 PM *To:* outages@outages.org <mailto:outages@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@outages.org <mailto:outages@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@outages.org <mailto:outages@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 <https://urldefense.proofpoint.com/v2/url?u=https-3A__status.slack.com&d=DwMFaQ&c=I2efTSIilX30_3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mzozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWufE&s=jEdWjAYTE25s1plpNBhgYquUjkwl3ZkKi4z05pjeif8&e=>

Josh Luthman Office: 937-552-2340 <tel:(937)%20552-2340> Direct: 937-552-2343 <tel:(937)%20552-2343> 1100 Wayne St Suite 1337 Troy, OH 45373

_______________________________________________ Outages mailing list Outages@outages.org <mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages <https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DwMFaQ&c=I2efTSIilX30_3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mzozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWufE&s=Ew9QPPwDapO941BpXODiG3edVhzy6YPE_kNGRU88RU0&e=>

--

Carlos Alvarez

602-368-6403 <tel:(602)%20368-6403>

_______________________________________________ Outages mailing list Outages@outages.org <mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages <https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DwMFaQ&c=I2efTSIilX30_3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mzozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWufE&s=Ew9QPPwDapO941BpXODiG3edVhzy6YPE_kNGRU88RU0&e=>

--

*Laurent Dumont*

/Spécialiste réseau / Network specialist/

*Fibre**noire* - www.fibrenoire.ca <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.fibrenoire.ca_&d=DwMFaQ&c=I2efTSIilX30_3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mzozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWufE&s=WD__vFH3y4NjQlfv7OemfI5WdYav9zqf5QXbL7NIJ2o&e=>

A: 550

​, avenue

Beaumont,

​bureau

 320,

Montréal (Québec)

 H3N 1V1

T. 514 907-3002 x132 <tel:(514)%20907-3002>

C.438-394-9603 <tel:(438)%20394-9603>

ldumont@fibrenoire.ca <mailto:farchambault@fibrenoire.ca>

Twitter: Twitter Fibrenoire <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_fibrenoire&d=DwMFaQ&c=I2efTSIilX30_3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mzozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWufE&s=OkarkaThgsPiVjzkTHj3RHvgsa2LOdSEP7J4XdN0Q-E&e=>

/--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@outages.org <mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages <https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_outages&d=DwMFaQ&c=I2efTSIilX30_3uvjg8Hm0Ao-qGfGH2XkNeOvmNAWpg&r=VtyiT6g7Y1hJ8DzI4aDXhUEU0Mzozoes7w0nUb-LgDo&m=QFDO9u71jFpoZnNNC8NAKRJ9RYyTJ2eIfSl9v7TWufE&s=Ew9QPPwDapO941BpXODiG3edVhzy6YPE_kNGRU88RU0&e=>

_______________________________________________ Outages mailing list Outages@outages.org <mailto:Outages@outages.org> https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman...

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 <tel:(337)%20269-9566>, and destroy the original transmission and its attachments without reading them or retaining any copies.

_______________________________________________ Outages mailing list Outages@outages.org <mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages

_______________________________________________ Outages mailing list Outages@outages.org <mailto:Outages@outages.org> 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 Outages@outages.org <mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages

_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages

the slack outage is likely related to an NSone network connectivity outage that we noticed via catchpoint. some slack services are named by NSone. $ host -a lb.slack-msgs.com Trying "lb.slack-msgs.com" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41067 ;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;lb.slack-msgs.com. IN ANY ;; ANSWER SECTION: lb.slack-msgs.com. 3600 IN NS dns2.p02.nsone.net. lb.slack-msgs.com. 3600 IN NS dns3.p02.nsone.net. lb.slack-msgs.com. 3600 IN NS dns4.p02.nsone.net. lb.slack-msgs.com. 3600 IN NS dns1.p02.nsone.net. lb.slack-msgs.com. 3600 IN SOA dns1.p02.nsone.net. hostmaster.nsone.net. 1515493525 43200 7200 1209600 3600 Received 171 bytes from 127.0.0.1#53 in 20 ms On Tue, Jan 9, 2018 at 12:40 PM, Chapman, Brad (Contractor-NBCUniversal) via Outages <outages@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@outages.org] *On Behalf Of *Sam Kirsch via Outages *Sent:* Tuesday, January 9, 2018 11:34 AM *To:* 'outages@outages.org' <outages@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@teamworld.com | www.teamworld.com

*From:* Laurent Dumont via Outages [mailto:outages@outages.org <outages@outages.org>] *Sent:* Tuesday, January 9, 2018 2:23 PM *To:* outages@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@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@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@outages.org https://puck.nether.net/mailman/listinfo/outages

--

Carlos Alvarez

602-368-6403 <(602)%20368-6403>

_______________________________________________ Outages mailing list Outages@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 <(514)%20907-3002>

C.438-394-9603 <(438)%20394-9603>

ldumont@fibrenoire.ca <farchambault@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@outages.org https://puck.nether.net/mailman/listinfo/outages

Well, the app still tells me "Smooth Sailing" when I check it's status and it obviously is down, not only for me but for many of use, so I an not sure if they are aware or if their monitoring is catching whatever is happening right now. On Tue, Jan 9, 2018 at 11:55 AM, George Herbert via Outages < outages@outages.org> wrote:

Right. And though the MeToos are excessive, the app really is That Important to That Many People now. So it's on topic.

George William Herbert Sent from my iPhone

On Jan 9, 2018, at 11:40 AM, Chapman, Brad (Contractor-NBCUniversal) via Outages <outages@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@outages.org <outages-bounces@outages.org>] *On Behalf Of *Sam Kirsch via Outages *Sent:* Tuesday, January 9, 2018 11:34 AM *To:* 'outages@outages.org' <outages@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@teamworld.com | www.teamworld.com

*From:* Laurent Dumont via Outages [mailto:outages@outages.org <outages@outages.org>] *Sent:* Tuesday, January 9, 2018 2:23 PM *To:* outages@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@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@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@outages.org https://puck.nether.net/mailman/listinfo/outages

--

Carlos Alvarez

602-368-6403 <(602)%20368-6403>

_______________________________________________ Outages mailing list Outages@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 <(514)%20907-3002>

C.438-394-9603 <(438)%20394-9603>

ldumont@fibrenoire.ca <farchambault@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@outages.org https://puck.nether.net/mailman/listinfo/outages

_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages

Started about the same time as the LastPass outage, but all major cloud providers’ status boards are green (AWS, MS, Google, etc). From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Tim Choe via Outages Sent: Tuesday, January 9, 2018 2:22 PM To: outages@outages.org Subject: Re: [outages] Slack outage Same here at LA :-( On 01/09/2018 11:19 AM, Josh Luthman via Outages 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 Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages

I think it’s clear by now that it’s having an outage. Not sure we need any more “me too” responses. From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Ivan Kovacevic via Outages Sent: 09 January 2018 19:22 To: Josh Luthman <josh@imaginenetworksllc.com> Cc: outages@outages.org Subject: Re: [outages] Slack outage Ditto – Naples, FL. Best Regards, Ivan Kovacevic Vice President, Client Services Star Telecom | www.startelecom.ca<http://t.sidekickopen05.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg1qMvVnW3LjyBM63K6FlW63JXmj56dLPjf6TyZWx02?t=http%3A%2F%2Fwww.startelecom.ca%2F&si=6470560385859584&pi=b3487421-6941-46fe-aa1b-8aeceeeca3c0> | SIP Based Services for Contact Centers | LinkedIn<http://t.sidekickopen05.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg1qMvVnW3LjyBM63K6FlW63JXmj56dLPjf6TyZWx02?t=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fstar-telecom-www-startelecom-ca-%3Ftrk%3Dbiz-companies-cym&si=6470560385859584&pi=b3487421-6941-46fe-aa1b-8aeceeeca3c0> From: Outages [mailto:outages-bounces@outages.org<mailto:outages-bounces@outages.org>] On Behalf Of Josh Luthman via Outages Sent: January 9, 2018 2:19 PM To: outages@outages.org<mailto:outages@outages.org> Subject: [outages] Slack outage 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

My community resolves to 52.84.1.124 which is part of Amazon AWS Network Operations. AWS status has nothing at this time - https://status.aws.amazon.com Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Tue, Jan 9, 2018 at 2:23 PM, Anthony Oren <anthony@nero-consulting.com> wrote:

Seeing the same in our Slack (NYC)

Also Lastpass having intermittent issues, must be similar host (AWS?) ᐧ

Anthony Oren *Nero Consulting Inc.* W: 347-699-6376 <(347)%20699-6376> M: 718-303-2400 <(718)%20303-2400>

Is your company ready for New York State's Cyber Security Regulations? *www.nero-consulting.com <http://www.nero-consulting.com> * *Trusted+Technology+Partner*

Notice: The information contained in this email is CONFIDENTIAL and intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copy of this communication is strictly PROHIBITED and will be considered a tortuous interference in our confidential business relationships. Additionally, unauthorized dissemination of this confidential information subjects you to criminal and civil penalties. If you have received this communication in error, please notify us immediately by email, and delete the original message.

On Tue, Jan 9, 2018 at 2:19 PM, Josh Luthman via Outages < outages@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 <https://maps.google.com/?q=1100+Wayne+St+Suite+1337+Troy,+OH+45373&entry=gmail&source=g> Suite 1337 <https://maps.google.com/?q=1100+Wayne+St+Suite+1337+Troy,+OH+45373&entry=gmail&source=g> Troy, OH 45373 <https://maps.google.com/?q=1100+Wayne+St+Suite+1337+Troy,+OH+45373&entry=gmail&source=g>

_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages

I think we’ve confirmed a Slack outage. “Me, too!” messages are probably redundant at this point. Dominick C. Colangelo <www.hinckleyallen.com/> Systems Administrator ________________________________ Hinckley Allen <http://www.hinckleyallen.com/> 28 State Street Boston, MA 02109-1775 p: 617-378-4188 | f: 617-345-9020 dcolangelo@hinckleyallen.com<mailto:dcolangelo@hinckleyallen.com> From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Laura Bacon via Outages Sent: Tuesday, January 9, 2018 2:30 PM To: Josh Luthman <josh@imaginenetworksllc.com> Cc: outages@outages.org Subject: Re: [outages] Slack outage Can confirm, Slack is also unavailable in Secaucus, NJ area. On Tue, Jan 9, 2018 at 11:19 AM, Josh Luthman via Outages <outages@outages.org<mailto:outages@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<tel:(937)%20552-2340> Direct: 937-552-2343<tel:(937)%20552-2343> 1100 Wayne St Suite 1337 Troy, OH 45373 _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages