Is Instagram down on desktop but still working on my phone today?
Table of Contents
- Is Instagram down on desktop but still working on my phone today?
- Key Takeaways
- Understanding the Facebook “Query Error” and the June 12 Outage
- The Technical Breakdown: What Is a Query Error?
- The Business Reality: Why Advertisers Knew First
- Timeline of the Disruption
- Symptoms and User Experience
- What to Do When Meta Goes Dark
Tired of “something went wrong”? Learn the real server-side cause of today’s Facebook query error and why checking Ads Manager reveals more than the main app.
Key Takeaways
What: A widespread Meta outage on June 12 caused login failures and “query errors” across Facebook and Instagram.
Why: Server-side communication failures prevented devices from retrieving account data.
How: Check the Meta Ads Status page for the most accurate disruption reports and toggle between Wi-Fi and cellular data.
Understanding the Facebook “Query Error” and the June 12 Outage
When your Facebook feed stops refreshing or Instagram refuses to load, the immediate reaction is usually to check your Wi-Fi. But on Friday, June 12, the problem was far deeper than a weak signal. Starting around 9:30 a.m. ET, a wave of connectivity issues hit Meta’s platforms, leaving over 100,000 users staring at “something went wrong” messages. While most news reports focused on the sheer number of frustrated users, the real story lay in a specific technical failure known as a “query error.”
The Technical Breakdown: What Is a Query Error?
A query error isn’t just a generic glitch; it is a specific communication failure between your device and Meta’s infrastructure. Specifically, this error occurs when the Facebook app or website sends a request for data—like your newest notifications or a friend’s photo—and Meta’s servers fail to retrieve that information.
During the June 12 incident, users were essentially knocking on the door, but the servers weren’t answering. This resulted in a fragmented experience where the shell of the app might load, but the actual content—the data you came for—remained missing.
The Business Reality: Why Advertisers Knew First
Standard industry logic suggests that a company’s official status page is the most reliable source of truth during an outage. However, this outage proved that standard logic is often wrong. The counter-intuitive insight here is that Meta’s consumer-facing status reports are frequently less accurate than their business-facing ones.
While many users saw “no known issues” on general status trackers, Meta’s Ads Manager status page was transparent about “High disruptions”. Because advertisers are the primary source of revenue, Meta’s engineering teams are often quicker to acknowledge failures in the tools used to create and edit ads. If you want to know if Facebook is truly struggling, ignore the public “all systems go” lights and look at the status of the Ads Manager instead.
Timeline of the Disruption
The spike in reports began sharply in the mid-morning hours on the East Coast. Downdetector, which monitors user-submitted reports, saw numbers climb from a few hundred to nearly 70,000 for Facebook alone in less than an hour.
The issues weren’t limited to the United States. Reports spanned globally, with users in the UK seeing problems by mid-afternoon their time. The outage was particularly erratic; while Facebook and Messenger seemed most affected, Instagram’s desktop site struggled even when its mobile app appeared stable for some.
Symptoms and User Experience
The outage didn’t look the same for everyone. Some people were hit with “404 – Page Not Found” errors on specific sub-pages, while others were unexpectedly logged out and found it impossible to sign back in.
Common error messages included:
- “An unexpected error occurred”
- “We’re working on it”
- “This page isn’t available right now”
These disruptions can be localized. Because of how data is routed, you might find yourself unable to load a single image while someone a few miles away is browsing without a hitch.
What to Do When Meta Goes Dark
Meta rarely offers a play-by-play explanation while an outage is in progress. If you find yourself caught in a “query error” loop, there are a few manual steps that can sometimes bypass localized routing issues.
First, try switching between Wi-Fi and cellular data to see if a different network path resolves the server communication failure. If the app is stuck, a full restart or checking for a pending update is the next logical step. Most of the time, however, the only real solution is to wait for Meta’s engineering teams to stabilize the servers and restore the data retrieval process.