'Something Went Wrong' Plus 'User Not Found' on Instagram: Blocked, or a Glitch?

There's a specific sequence people describe, and it's the same story every time. You search a name, the profile appears, but the grid is empty and says "No posts yet." You tap Follow. A little banner: "Something went wrong." You pull to refresh, and now the page says "User not found."

That sequence isn't random. Here's what it means, when it means something else, and the sixty-second way to be sure.

Why the Two Errors Show Up Together

A block on Instagram isn't a single wall. It's a set of rules applied to a relationship, and different parts of the app enforce them at different moments.

• The profile shell loads because your app cached the basics (username, sometimes the post count) or because the lookup succeeded before the block rules kicked in.
• The grid is empty because the block rule hides content: "No posts yet" is Instagram's way of saying "nothing you're allowed to see," not "this account has no posts."
• Follow fails because the block rule rejects the action server-side, and the app has no specific message for "you can't follow this person," so you get the generic one. "Something went wrong."
• The refresh turns into "User not found" because a fresh lookup, with the block rules applied from the start, returns nothing at all.

Put together, the sequence is a block being enforced in stages. A deactivated or deleted account never gets that far; it fails at the first lookup and you see user not found immediately, with no half-loaded profile in between.

When It's Not a Block

The same error text appears for other reasons, and the way to separate them is scope.

It happens on every profile. Then it's you, not them. Causes, in order of likelihood:

1. Connection. Switch between Wi-Fi and cellular and try again.
2. Outdated app. Instagram deprecates old builds aggressively. Update.
3. Temporary action block. If you followed, liked, or commented a lot in a short window, Instagram may rate-limit your account for a few hours. Following is one of the first actions it restricts.
4. Outage. Check whether other people are reporting problems. Instagram outages produce "Something went wrong" across the board.

It happens on one profile, but it opens fine a minute later. Then it was a cache hiccup. Blocks don't resolve themselves.

The profile shows their real posts, but Follow errors. That's a rate limit on your account, not a block. A blocked profile never shows content.

The One-Minute Confirmation

Open the same username in a logged-out browser tab, a private window, or a second account.

• Loads normally there → you're blocked. The profile exists; it's hidden from you specifically.
• Fails there too → the account is deactivated, deleted, suspended, or renamed. In that case the "Something went wrong" step was probably a cache artifact, and the five-case breakdown of user not found applies.

If you have DM history with the person, there's an even quicker tell. Open the thread. If their name still shows and tapping it fails, that leans block. If their name has become "Instagram User", they deactivated or deleted, and no block is involved.

What to Do With the Answer

If you were blocked: nothing. Instagram deliberately doesn't notify people, and it deliberately doesn't offer an appeal, because there's nothing to appeal. Making a new account to get around it violates the platform's rules and, more to the point, the other person's decision. The broader set of block checks exists to answer the question, not to route around it.

If it was a glitch: wait, update, or switch networks. Glitches clear. Blocks don't. And if it was a rate limit on your side, that's a signal to slow down; the limits get longer each time they trigger.

The "Something went wrong, then user not found" sequence feels like the app is being cagey with you. It is. Instagram won't say "you've been blocked," so it says two vaguer things instead. Read them together and the message is clear enough.