Send Outages-discussion mailing list submissions to
outages-discussion@outages.org
To subscribe or unsubscribe via the World Wide Web, visit
https://puck.nether.net/mailman/listinfo/outages-discussion
or, via email, send a message with subject or body 'help' to
outages-discussion-requ...@outages.org
You can reach the person managing the list at
outages-discussion-ow...@outages.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Outages-discussion digest..."
Today's Topics:
1. Re: Who broke the Internet? 2024-03-05 edition. (Chris Adams)
2. Re: Who broke the Internet? 2024-03-05 edition. (Dustin Sneath)
3. Re: Who broke the Internet? 2024-03-05 edition. (Jay Ashworth)
4. Re: [outages] REMINDER: MAIN LIST NOT FOR CHAT (Carl Perry)
5. Re: Who broke the Internet? 2024-03-05 edition. (Ivan Ip)
----------------------------------------------------------------------
Message: 1
Date: Tue, 5 Mar 2024 10:08:51 -0600
From: Chris Adams <c...@cmadams.net>
To: outages-discussion@outages.org
Subject: Re: [Outages-discussion] Who broke the Internet? 2024-03-05
edition.
Message-ID: <20240305160851.ga30...@cmadams.net>
Content-Type: text/plain; charset=utf-8
Once upon a time, Edward Vielmetti <evielme...@equinix.com> said:
> Down detector is showing elevated problems across Facebook/Meta properties,
> Google properties, T-Mobile, Discord, Tik Tok ? with no obvious single cause
> that I have seen reported. Any ideas? Ed.
Example #427 why downdetector is not terribly useful other than a rough
indicator. STOP TAKING IT AS FACT!
--
Chris Adams <c...@cmadams.net>
------------------------------
Message: 2
Date: Tue, 5 Mar 2024 10:12:20 -0600
From: Dustin Sneath <dsne...@elkgroveparks.org>
To: Chris Adams <c...@cmadams.net>, outages-discussion@outages.org
Subject: Re: [Outages-discussion] Who broke the Internet? 2024-03-05
edition.
Message-ID:
<cabtk8nr22bxg3vt-buhb7yjobaxfepgwud0v+fsfmnx0zi_...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
DownDetector is essentially someone from accounting yelling "THE INTERNET
IS DOWN!", with stats.
On Tue, Mar 5, 2024 at 10:11?AM Chris Adams via Outages-discussion <
outages-discussion@outages.org> wrote:
> Once upon a time, Edward Vielmetti <evielme...@equinix.com> said:
> > Down detector is showing elevated problems across Facebook/Meta
> properties, Google properties, T-Mobile, Discord, Tik Tok ? with no obvious
> single cause that I have seen reported. Any ideas? Ed.
>
> Example #427 why downdetector is not terribly useful other than a rough
> indicator. STOP TAKING IT AS FACT!
> --
> Chris Adams <c...@cmadams.net>
> _______________________________________________
> Outages-discussion mailing list
> Outages-discussion@outages.org
> https://puck.nether.net/mailman/listinfo/outages-discussion
>
--
Dustin Sneath
Superintendent of I.T. | Elk Grove Park District
*p *847-228-3846
elkgroveparks.org
*Go Beyond the Expected! <https://www.facebook.com/elkgroveparks>
<https://twitter.com/elkgroveparks>
<https://www.instagram.com/elkgroveparks/>
<https://www.youtube.com/user/EGParkDistrict/videos> *
?IAPD / IPRA Illinois Distinguished Accredited Agency
*Confidentiality Note:* This email may contain confidential and or private
information. Please notify the sender and delete this email if you received
it in error.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/outages-discussion/attachments/20240305/d09c78b0/attachment-0001.htm>
------------------------------
Message: 3
Date: Tue, 05 Mar 2024 11:13:01 -0500
From: Jay Ashworth <j...@baylink.com>
To: Chris Adams <c...@cmadams.net>, Chris Adams via Outages-discussion
<outages-discussion@outages.org>, outages-discussion@outages.org
Subject: Re: [Outages-discussion] Who broke the Internet? 2024-03-05
edition.
Message-ID: <f9d1057c-7ebf-48f8-8a98-7c13b3cb9...@baylink.com>
Content-Type: text/plain; charset="utf-8"
I have a reliable inside report that nobody at Meta thinks this is Network
layer.
On March 5, 2024 11:08:51 AM EST, Chris Adams via Outages-discussion
<outages-discussion@outages.org> wrote:
>Once upon a time, Edward Vielmetti <evielme...@equinix.com> said:
>> Down detector is showing elevated problems across Facebook/Meta properties,
>> Google properties, T-Mobile, Discord, Tik Tok ? with no obvious single cause
>> that I have seen reported. Any ideas? Ed.
>
>Example #427 why downdetector is not terribly useful other than a rough
>indicator. STOP TAKING IT AS FACT!
>--
>Chris Adams <c...@cmadams.net>
>_______________________________________________
>Outages-discussion mailing list
>Outages-discussion@outages.org
>https://puck.nether.net/mailman/listinfo/outages-discussion
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/outages-discussion/attachments/20240305/9de3aad8/attachment-0001.htm>
------------------------------
Message: 4
Date: Tue, 5 Mar 2024 16:21:12 +0000
From: Carl Perry <cape...@edolnx.net>
To: "outages-discussion@outages.org" <outages-discussion@outages.org>
Subject: Re: [Outages-discussion] [outages] REMINDER: MAIN LIST NOT
FOR CHAT
Message-ID: <c2a5cb92-4e06-4926-b038-3fcd1f997...@edolnx.net>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
I'd like to re-raise the proposal from a few weeks ago that the default
reply-to for the outages list be outages-discussion. I think this is the
only way to stem this tide since it's been going on for weeks.
? -Carl
On 3/5/24 16:11, Jay Ashworth via Outages wrote:
> The only other messages we should see on the main list are "it's back
> now". Please take the discussions over to -discuss.
>
> Cheers,
> -- jr '<admin/>' a
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>
> _______________________________________________
> Outages mailing list
> outa...@outages.org
> https://puck.nether.net/mailman/listinfo/outages
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/outages-discussion/attachments/20240305/0272d378/attachment-0001.htm>
------------------------------
Message: 5
Date: Tue, 5 Mar 2024 16:37:19 +0000
From: Ivan Ip <ivan...@toughlife.info>
To: Jay Ashworth <j...@baylink.com>
Cc: Chris Adams <c...@cmadams.net>, Chris Adams via Outages-discussion
<outages-discussion@outages.org>
Subject: Re: [Outages-discussion] Who broke the Internet? 2024-03-05
edition.
Message-ID:
<ca+hkw+b58jw6zj0rf1cf3cwqzsdlpuedx89xnpto3ovqj-r...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi Jay,
Any updates? ;)
On Tue, Mar 5, 2024 at 4:14?PM Jay Ashworth via Outages-discussion <
outages-discussion@outages.org> wrote:
> I have a reliable inside report that nobody at Meta thinks this is Network
> layer.
>
>
> On March 5, 2024 11:08:51 AM EST, Chris Adams via Outages-discussion <
> outages-discussion@outages.org> wrote:
>
>> Once upon a time, Edward Vielmetti <evielme...@equinix.com> said:
>>
>>> Down detector is showing elevated problems across Facebook/Meta properties,
>>> Google properties, T-Mobile, Discord, Tik Tok ? with no obvious single
>>> cause that I have seen reported. Any ideas? Ed.
>>>
>>
>> Example #427 why downdetector is not terribly useful other than a rough
>> indicator. STOP TAKING IT AS FACT!
>>
>> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
> _______________________________________________
> Outages-discussion mailing list
> Outages-discussion@outages.org
> https://puck.nether.net/mailman/listinfo/outages-discussion
>
--
Yours sincerely,
Ivan Ip
Pantry Manager at Toughlife
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/outages-discussion/attachments/20240305/b112f5db/attachment.htm>
------------------------------
Subject: Digest Footer
_______________________________________________
Outages-discussion mailing list
Outages-discussion@outages.org
https://puck.nether.net/mailman/listinfo/outages-discussion
------------------------------
End of Outages-discussion Digest, Vol 165, Issue 3
**************************************************
