Live data from Hacker News

Meta outage

metastatus.com

381–390 of 902 posts

Re: Meta outage

#383
post #292

I was considering buying the Quest 3 this morning, this outage is timely. The fact that I can't use my perfectly working headset to play an offline game because facebook is down, makes me wonder if I should go for a different provider. Any recommendations? Excluding apple vision pro since it is too expensive.

Unless it's a recent change, it works perfectly fine offline (wifi turned off). As for alternatives, there is Pico, but Quest 3 may be superior in games selection. Or go wired which is of course less portable

This is different from it being offline, it's like the device is kicked off the associated account. A "something went wrong" window pops up with a "generate device code" button, with instructions on how to remove and re-pair the headset.

There is no way to even access wifi settings or anything else to disconnect the device from the internet. If it's still a problem much later in the day, I'll try turning off my router to see what that does.

Re: Meta outage

#384

Might be related to this event? > The cut lines include Asia-Africa-Europe 1, the Europe India Gateway, Seacom and TGN-Gulf, Hong Kong-based HGC Global Communications said. It described the cuts as affecting 25% of the traffic flowing through the Red Sea. https://apnews.com/article/red-sea-undersea-cables-yemen-hou... https://www.bbc.com/news/world-middle-east-68478828.amp

I'm pretty sure that report is just mainstream media reporting this week old cut https://www.datacenterdynamics.com/en/news/at-least-one-subs...

Pretty neat if a week after a cable is cut, FB falls over.

Especially when most of the source of truth databases are in the US and Europe, and that sort of data flow doesn't cross the Red Sea. FB has datacenters and points of presence all over, but outside the US/EU it's almost all caching.

Re: Meta outage

#385

Looking at the Downdetector home page [1], it looks like many more services are having outages, not just the ones owned by Meta, including: - Google - YouTube - Google Play - T-Mobile - X (Twitter) - Discord - TikTok - Pokemon Go - Snapchat It looks like they all have the same failure point. [1] https://downdetector.com

HN seems to be struggling too, but that could just be everyone here to talk about the outages.

Re: Meta outage

#386

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.

Surely the repeated logins can't be helping the situation. I suppose it is entirely auth related across all Meta products. The repeated strain could pose a cold start problem for example.

Re: Meta outage

#387

It logged me out and told me that my credentials were incorrect; I thought my credentials had been stolen, so I'm kinda personally glad that it seems to be happening to a lot of other people too. I know that's a bit selfish, but :shrug:

Likewise, started password reset process that won't complete, asked my wife to double check my account wasn't compromised and posting cryptocurency crap or somesuch.

Re: Meta outage

#389
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 ensure Business Continuity & Applications Resiliency redundancies feel asleep at the wheel?

Also, to assume that no down or outage messaging go out during a fairly routine maintenance based outage?

I call BS

Lol I can't find scenario where this happens, at this scale at a company of Meta's scale

Re: Meta outage

#390

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.

> catchy name

Petunia?

Post reply on HN