[sf-lug] "all better now:" Re: outage: [www.]{sf-lug,balug}.org

[Michael Paoli]

And ... again, same deal, went off-line at:
<~= 2018-01-11T01:23:21+00:00 2018-01-10T17:23:21-08:00
and back on-line by:
> ~= 2018-01-11T04:04:06+00:00 2018-01-10T20:04:06-08:00
... again, swift kick to the power switch on DSL modem to reset it,
and "all better" - again ... at least for now.

> From: "Michael Paoli" <Michael.Paoli at cal.berkeley.edu>
> Subject: "all better now:" Re: outage: [www.]{sf-lug,balug}.org  
> (ETR: eveningish)
> Date: Wed, 06 Dec 2017 18:08:09 -0800

> And ... swift kick to the power switch on DSL modem to reset it,
> and "all better now".
> Looks like the outage started around:
> BALUG PING: ping6 2001:470:1f04:19e::2 FAILED 2017-12-06T20:53:56+00:00
> GW PING: ping 198.144.194.233 FAILED 2017-12-06T20:54:09+00:00
> and service restored a few minutes ago
>
>
>> From: "Michael Paoli" <Michael.Paoli at cal.berkeley.edu>
>> Subject: outage: [www.]{sf-lug,balug}.org (ETR: eveningish)
>> Date: Wed, 06 Dec 2017 14:46:38 -0800
>
>> So,
>>
>> They were up and on-line this morning, at least as late as about
>> mid-morning or later, but off-line now.
>> POTS line appears to be working, but not IP,
>> likely the DSL modem needs to be reset (powercycled) again ...
>> but don't have means to do that remotely.
>>
>> Presumably I'll have this resolved sometime this evening once I'm
>> on-site again.
>>
>> impacts all [*.]sf-lug.{org,com} & [*.]balug.org
>> SF-LUG lists remain up and on-line (at least as far as I'm aware).