Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Meta outage

metastatus.com

Post reply on HN
Print view View original

591–600 of 902 posts

Re: Meta outage

#591

Post by HumblyTossed »

neocritter wrote: post #499
HumblyTossed wrote: post #491

Earlier quoted context omitted.

Does it really or is this a joke? Edit: I found the following, I wonder if it's still the case. https://news.ycombinator.com/item?id=16076041

It's real. Single core performance improves all the time. People overestimate how much power it takes to handle lots of queries per second on a well-tuned system and well-written software in 2024. https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...

> People overestimate how much power it takes to handle lots of queries per second on a well-tuned system and well-written software in 2024.

I wasn't overestimating anything, but with how easy it is to write concurrently software today, why limit your site to a single core.

Re: Meta outage

#592

Post by lamontcg »

diggan wrote: post #227
geerlingguy wrote: post #115

Earlier quoted context omitted.

I lament the fact error messages are rarely, if ever, displayed anymore. Just a generic message in its place, usually not even indicating whether it's a 'you' problem or a 'them' problem :(

Yeah, but at least it's a bit understandable that its changed in that direction, and usually you can get a developer-friendly error message if you look at the HTTP responses in the devtools. I remember one time a company I worked at received a support message where the title was (paraphrased) "DONT HURT MY CHILDREN" from some person who saw an error message saying something about "couldn't dispose of child" or someth…

Generally error messages get watered down to nothingness because it gives news reporters less meat to chew on. Not knowing if its a "me or you" problem means that small problems might actually get missed and not need any PR response. Details won't leak and produce all kinds of speculation over the causes, etc.

Re: Meta outage

#594

Post by dylan604 »

nickpsecurity wrote: post #555
DeusExMachina wrote: post #281

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

A lot of sites have features that say “log in with your X or Y account.” They connect to each other somehow. I never studied that protocol. I wonder if authentication failures across services could be tied to it. For process of elimination, do all of these services do multi-platform logins? Or do some not connect to anyone else?

that actually infuriates me more than cookie banners. the one from Googs is the worst offender.

Re: Meta outage

#595

Post by yreg »

busymom0 wrote: post #571
ndiddy wrote: post #535

Earlier quoted context omitted.

I see the "sorry, we are receiving too many requests, try again in a few minutes" error several times a day on here. I don't think that HN is reliably able to handle the amount of users it currently has.

I believe that's by design if you send an action request very quickly after a previous one. It's very easy to replicate. Open a post. Then click the upvote button and very quickly click the favorite button too. That will trigger it. I think it's used to rate limit.

>"Sorry, we're not able to serve your requests this quickly" is our little server process saying "help, I only have a single core and I'm out of breath here". If your account were rate limited it would say something like "You're posting too fast, please slow down."

dang, linked in one of the ancestor comments. But I still suspect you are correct.

Re: Meta outage

#596

Post by jordanthoms »

partiallypro wrote: post #579
DeusExMachina wrote: post #281

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

Down Detector is so unreliable. People that can't call an AT&T phone via Verizon will think (and report) that Verizon is down, when it's really AT&T. People can try logging in using Facebook's on click login and not be able to get in, so they think Tiktok is down. It's not all that useful. I hate when journalists cite it.

It has false positives and noise for sure, but it's also very sensitive and shows issues very quickly.

I wouldn't trust it as a single source, but in a case like this where our internal monitoring shows a spike of issues with the Google APIs and we can see a huge spike in reported issues for Google on Downdetector starting at the same time, it's useful to confirm that the issues have an external source.

Re: Meta outage

#598

Post by Arainach »

rimunroe wrote: post #570
redserk wrote: post #456

Earlier quoted context omitted.

Yeah, it's wild that it's now treated as an authoritative source, especially by some news organizations. It's as good as asking a neighbor what happened with a loud noise down the street. Sometimes you'll get something good, sometimes it'll be completely wrong.

> Yeah, it's wild that it's now treated as an authoritative source, especially by some news organizations. > It's as good as asking a neighbor what happened with a loud noise down the street. Sometimes you'll get something good, sometimes it'll be completely wrong. Asking my neighbors if they know what some loud noise was or about some local disturbance has been extremely reliable in my experience. The one time someo…

You must have an exceptional neighborhood. Everywhere I lived, here's a handy map of "actual cause" :: "what the neighbors said it was"

Car exhaust :: gunshot Appliance delivery truck liftgate :: gunshot Transformer explosion :: gunshot Garbage truck :: gunshot 787 at 25000ft :: complete ruining of peace and quiet Any police activity :: probably someone robbed a bank

For the record, my city has (statistically indistinguishable from 0) homicides and bank robberies and, by American standards (I know, I know) no particular issues with gun crime.

Re: Meta outage

#599

Post by tomrod »

yreg wrote: post #585
newswasboring wrote: post #577

Earlier quoted context omitted.

I have been using HN daily since I was a teenager. I've seen that message maybe 10 times outside of serious issues in last 15 years. It's strange to me that it happens so frequently for you.

That's difficult to believe to be honest. I get it several times a week.

I get something like that when I try to comment and then upvote too quickly.

Re: Meta outage

#600

Post by dylan604 »

btbuildem wrote: post #449
DeusExMachina wrote: post #281

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

What's your fave conspiracy theory? Massive cyberattack for Super Tuesday? Powers-that-be mandated takedown? Mossad sleeper agents activated? Covid-brain struck that one engineer attending to that one wire that kept everything going?

I guess the swamp got drained, so there's no more flow through the tubes.
Post reply on HN