Live data from Hacker News

Meta outage

metastatus.com

421–430 of 902 posts

Re: Meta outage

#421
I find it remarkable that Typepad, my blog host, not only isn't down but also is MUCH FASTER than its usual slothlike, approximately 5 seconds response time.

Re: Meta outage

#422

Tip for Meta engineers: when your service is failing, don't just log people out and prevent logins. Display a cute image that shows that the service is drastically failing (like a whale or something), and then people will know to stop trying to repeatedly log in. The public might even come up with a catchy name for the whale.

Beyond unbelievable that going on an hour later, they're still showing "incorrect password" errors. How many hundreds of millions of people have wasted time frantically trying (in vain) to reset their passwords and pointlessly freaking out that their account might be compromised? What a bunch of careless, incompetent excuses for engineers.

What a poor bunch of overworked human beings, with almost no control over the product they work on. Frantically following the whims of managers, reduced to labour units in this late stage capitalist hellscape.

Re: Meta outage

#424

Tip for Meta engineers: when your service is failing, don't just log people out and prevent logins. Display a cute image that shows that the service is drastically failing (like a whale or something), and then people will know to stop trying to repeatedly log in. The public might even come up with a catchy name for the whale.

For anything outside like-ing and post-ing, facebooks UI/UX is horrendous. Even Internet search does not help to find out how something trivial is done... The only way is to watch youtube videos.

Re: Meta outage

#426

Tip for Meta engineers: when your service is failing, don't just log people out and prevent logins. Display a cute image that shows that the service is drastically failing (like a whale or something), and then people will know to stop trying to repeatedly log in. The public might even come up with a catchy name for the whale.

Could be an outage in the auth service itself

Unless it's an outage in their ability to log into their own servers, they should be able to swap out the login page with a static HTML page explaining the outage. Maybe a 503 status code.

Re: Meta outage

#429

Frankly, I don't buy this explanation - technically or logically both from a devops,and systems architecture level - There is no way in hell a company like Meta is pushing database design changes this significant to production? We all know how many times these database architecture changes get run in staging,then even production subsets before rolling out to production at large. Should we assume the teams working to…

I don’t buy it either! Something’s fishy…

or phishy or both for sure
Post reply on HN