From: dan <dandenson@gmail.com>
To: Herbert Wolverson <herberticus@gmail.com>
Cc: dave.taht@gmail.com, libreqos@lists.bufferbloat.net
Subject: Re: [LibreQoS] Fwd: eero outage
Date: Wed, 10 Jul 2024 18:02:05 -0600 [thread overview]
Message-ID: <CAA_JP8WtrN1RRwRoWQU3Tu6VSWeHu1Bh9c8YqkQdoPCNwa0K2Q@mail.gmail.com> (raw)
In-Reply-To: <CA+erpM4vuxQBWKCg+jnQqLXgThSoifvnYTpCebUJ=ZAB2Ry_Yg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1357 bytes --]
I haven't seen anything, no customer complaints. I may have missed a
dashboard outage though. I can get in now.
On Wed, Jul 10, 2024 at 4:47 PM Herbert Wolverson via LibreQoS <
libreqos@lists.bufferbloat.net> wrote:
> My eero system is up, not seeing any sign it (or the management app) was
> down?
>
> On Wed, Jul 10, 2024, 5:23 PM Dave Taht via LibreQoS <
> libreqos@lists.bufferbloat.net> wrote:
>
>>
>>
>> ---------- Forwarded message ---------
>> From: Jared Mauch <jared@puck.nether.net>
>> Date: Wed, Jul 10, 2024 at 2:33 PM
>> Subject: eero outage
>> To: <nanog@nanog.org>
>>
>>
>>
>> Does anyone know about the big eero outage going on?
>>
>> - jared
>>
>> --
>> Jared Mauch | pgp key available via finger from jared@puck.nether.net
>> clue++; | http://puck.nether.net/~jared/ My statements are only
>> mine.
>>
>>
>> --
>> https://www.linkedin.com/feed/update/urn:li:activity:7203400057172180992/
>> Donations Drive.
>> Dave Täht CSO, LibreQos
>> _______________________________________________
>> LibreQoS mailing list
>> LibreQoS@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/libreqos
>>
> _______________________________________________
> LibreQoS mailing list
> LibreQoS@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/libreqos
>
[-- Attachment #2: Type: text/html, Size: 3079 bytes --]
prev parent reply other threads:[~2024-07-11 0:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Zo7bslUTmNAoocQ_@puck.nether.net>
2024-07-10 22:22 ` Dave Taht
2024-07-10 22:47 ` Herbert Wolverson
2024-07-11 0:02 ` dan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA_JP8WtrN1RRwRoWQU3Tu6VSWeHu1Bh9c8YqkQdoPCNwa0K2Q@mail.gmail.com \
--to=dandenson@gmail.com \
--cc=dave.taht@gmail.com \
--cc=herberticus@gmail.com \
--cc=libreqos@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox