Facebook, Instagram and WhatsApp hit by a Meta outage


Meta had a bad Friday morning. A major Meta outage knocked out Facebook, Instagram, WhatsApp, and Messenger for users around the world, starting shortly before 10am ET. By midday it was recovering, unevenly, region by region.

The trouble appeared to begin on WhatsApp, then spread. Facebook users were abruptly logged out, met with a “Query Error” or a “Sorry, something went wrong” message, and unable to log back in. Others could open the app but not post, comment, react, search, or load Stories and Marketplace.

What Down Detector shows

The outage-tracking site Down Detector logged a sharp spike. Facebook bore the brunt, with reports passing 130,000; Instagram logged around 9,500, and WhatsApp far fewer. Across all three, most people flagged problems with the app, then login.

Those numbers are self-reported, so they track complaints, not Meta’s own data. But the reports came in from far beyond the US, from the Philippines and Taiwan to Australia, Spain, and South Africa, which points to something central rather than a local glitch.

Businesses caught out

The 💜 of EU tech

The latest rumblings from the EU tech scene, a story from our wise ol’ founder Boris, and some questionable AI art. It’s free, every week, in your inbox. Sign up now!

It was not just scrolling. Meta’s status page logged “high disruptions” across its business products, including Facebook Ads Manager, the Messenger Platform, the Messenger API for Instagram, and the WhatsApp Business Platform. Advertisers could not create or edit ads, and Meta apologised “for any inconvenience.” On a Friday, the timing stung.

Meta confirms the disruption, but not the cause

Meta acknowledged the problems on its status page, flagging “high disruptions” and saying its engineering teams were “actively looking to resolve the issue as quickly as possible.” It did not say what caused the outage, or how many users were hit.

There is no word yet on whether it was a configuration error, an infrastructure failure, or something else.

Recovery was already under way. Meta marked some services, such as ad delivery, as resolved, with others “in the process of being restored.” On the consumer side, Facebook was loading closer to normal and Down Detector reports were falling, though some users still saw an empty Stories bar, a stale feed, or a “Try Again” error.

The scale is the point: Meta’s apps reach billions, and even a couple of hours offline ripples through messaging, businesses, and logins far beyond the feed. It capped an eventful day for Meta, which this morning pledged free AI glasses to every blind US veteran. This is a developing story; we will update it with Meta’s explanation and an all-clear.



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


“It was severely downgraded,” Gilbert confirms. “I never would have found it if I was just looking through Google results.” (I tried the same prompt in Gemini earlier this month, and after an initial denial, the tool also gave me Eiger’s number.)

After this experience, Eiger, Gilbert, and another UW PhD student, Anna-Maria Gueorguieva, decided to test ChatGPT to see what it would surface about a professor. 

At first, OpenAI’s guardrails kicked in, and ChatGPT responded that the information was unavailable. But in the same response, the chatbot suggested, “if you want to go deeper, I can still try a more ‘investigative-style’ approach.” Their inquiry just had to help “narrow things down,” ChatGPT said, by providing “a neighborhood guess” for where the professor might live, or “a possible co-owner name” for the professor’s home. ChatGPT continued: “That’s usually the only way to surface newer or intentionally less-visible property records.” 

The students provided this information, leading ChatGPT to produce the professor’s home address, home purchase price, and spouse’s name from city property records. 

(Taya Christianson, an OpenAI representative, said she was not able to comment on what happened in this case without seeing screenshots or knowing which model the students had tested, even after we pointed out that many users may not know which model they were using in the ChatGPT interface. She also declined to comment generally about the exposure of PII by the chatbot, instead providing links to documents describing how OpenAI handles privacy, including filtering out PII, and other tools.) 

This reveals one of the fundamental problems with chatbots, says DeleteMe’s Shavell. AI companies “can build in guardrails, but [their chatbots] are also designed to be effective and to answer customer questions.”

The exposure issue is not limited to Gemini or ChatGPT. Last year, Futurism found that if you prompted xAI’s chatbot Grok with “[name] address,” in almost all cases, it provided not only residential addresses but also often the person’s phone numbers, work addresses, and addresses for people with similar-sounding names. (xAI did not respond to a request for comment.) 

No clear answers

There aren’t straightforward solutions to this problem—there’s no easy way to either verify whether someone’s personal information is in a given model’s training set or to compel the models to remove PII. 



Source link