Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

А-а-аблака, белокрылые лашадки...

14 views
Skip to first unread message

Sergey Kubushyn

unread,
Feb 28, 2017, 7:51:46 PM2/28/17
to
http://www.foxnews.com/tech/2017/02/28/amazon-web-service-suffers-major-outage-disrupts-east-coast-internet.html

Но вы, Шура, пилите...

---
******************************************************************
* KSI@home KOI8 Net < > The impossible we do immediately. *
* Las Vegas NV, USA < > Miracles require 24-hour notice. *
******************************************************************

CF

unread,
Feb 28, 2017, 8:20:02 PM2/28/17
to

Sergey Kubushyn пишет:
А-а-а! Русские хакеры!

CF

G

unread,
Mar 1, 2017, 11:50:05 AM3/1/17
to
да лана гнать то, с кем не бывает? и на старуху бывает проруха..
G

Юpa Шaлaк

unread,
Mar 1, 2017, 9:09:55 PM3/1/17
to
"Sergey Kubushyn" <k...@koi8.net> wrote in message
news:o955v5$54q$1...@ddt.demos.su...
Amazoff

Roman N

unread,
Mar 1, 2017, 11:56:43 PM3/1/17
to
Да ниче и не было, подумаешь регион не работал частично пол-дня.

G

unread,
Mar 2, 2017, 9:55:04 AM3/2/17
to
ну лана , "ниче", мы ажно пивка прямиком в офисе хлопнули :-)
G

Ilya L

unread,
Mar 2, 2017, 12:53:56 PM3/2/17
to
https://aws.amazon.com/message/41926/

Unfortunately, one of the inputs to the command was entered incorrectly
and a larger set of servers was removed than intended.


So, basically "sudo rm -rf --no-preserve-root /" ;-)


S3 has experienced massive growth over the last several years and the
process of restarting these services and running the necessary safety
checks to validate the integrity of the metadata took longer than expected.


No periodic DR testing?


From the beginning of this event until 11:37AM PST, we were unable to
update the individual services’ status on the AWS Service Health
Dashboard (SHD) because of a dependency the SHD administration console
has on Amazon S3. Instead, we used the AWS Twitter feed (@AWSCloud) and
SHD banner text to communicate status until we were able to update the
individual services’ status on the SHD.


AWS infra should have backup capacity on GCP and Azure, just like
everyone else! :)

ilya



Roman N

unread,
Mar 2, 2017, 9:45:09 PM3/2/17
to


Ilya L wrote on 02/03/2017 09:53:
> On 3/1/17 8:56 PM, Roman N wrote:
>> G wrote on 01/03/2017 08:45:
>>> On 2/28/17 7:51 PM, Sergey Kubushyn wrote:
>>>> http://www.foxnews.com/tech/2017/02/28/amazon-web-service-suffers-major-outage-disrupts-east-coast-internet.html
>>>>
>>>>
>>>> Но вы, Шура, пилите...
>>>>
>>>> ---
>>>> ******************************************************************
>>>> * KSI@home KOI8 Net < > The impossible we do immediately. *
>>>> * Las Vegas NV, USA < > Miracles require 24-hour notice. *
>>>> ******************************************************************
>>>>
>>> да лана гнать то, с кем не бывает? и на старуху бывает проруха..
>>
>> Да ниче и не было, подумаешь регион не работал частично пол-дня.
>>
>
> https://aws.amazon.com/message/41926/
>
>
> AWS infra should have backup capacity on GCP and Azure, just like
> everyone else! :)

Root cause of outage: S3 is actually hosted on Google Cloud Storage, and
today Google Cloud Storage migrated to AWS

--
R
0 new messages