People assume that when Instagram removes an account the record is gone. It is not. To find deleted Instagram account data you stop searching for the username and start searching for the numeric user id, because the public page returns a 404 while the account object behind it keeps answering. The bio and profile picture can still be served, and a separate last-active signal may still respond. What changes is the username, which Instagram swaps for a localized placeholder.
This post works through two banned accounts as the engine returned them on 2026-09-05, one generic word and one handle from a news story, and explains what the numeric id proves. Everything here reads public endpoints and signs in to nothing.
What Instagram does when an account goes away
There are three ways an account leaves the public web, and they look identical from the outside. A ban is Instagram disabling the account for a policy reason. A deactivation is the owner switching it off with the option to return. A deletion is the owner asking for permanent removal, carried out after a grace period. In all three cases the profile URL returns "Sorry, this page isn't available", and a scanner that trusts the HTML records a miss.
The GraphQL and mobile endpoints tell a different story. A username that was never registered returns a null user object. A banned or disabled username returns a populated object with a numeric pk, an account status, and often the last bio and avatar. The username in that object is a localized placeholder, "Instagram User" for an English exit IP or its equivalent in the request's language, which is why you never correlate banned accounts by display name.
| State | Public page | Account object by id | Bio and picture |
|---|---|---|---|
| Never registered | 404 | null | none |
| Banned by Instagram | 404 | resolves, banned_or_disabled | often still served |
| Deactivated by owner | 404 | resolves, banned_or_disabled | often still served |
| Deleted by owner | 404 | resolves during the grace period, then null | fades with the object |
The engine cannot tell a ban from an owner deactivation; both come back as banned_or_disabled. What it can tell you is that the account existed, its id, and what it looked like at the end.
How to find deleted Instagram account records by user id
The username is a label. The id is the account. Instagram assigns the numeric id at signup and never reuses it, and it survives renames, deactivations and bans. If you captured the id while the account was live, you can resolve it long after the handle stopped working. If you only have the username, a search still returns the id as long as the handle has not been released and re-registered, the trap the old usernames guide spends a section on.
Here is the first record, the handle gambling, as the engine returned it:
{
"platform": "instagram",
"username": "gambling",
"user_id": "64124577206",
"returned_username": "Instagram User",
"bio": "kiss",
"profile_picture": "served (Instagram default anonymous avatar)",
"account_status": "banned_or_disabled",
"banned": true,
"last_active_days_ago": 858
}
Read it field by field. The id is present, so the account is a real object and not a guessed URL. The returned_username is Instagram's placeholder, not the handle we searched, which alone says the account is disabled. The bio is one word, "kiss", still served. The picture is the default gray silhouette. The status field confirms the ban. And the last-active oracle, a separate presence signal, answers 858 days, which puts the last activity in the spring of 2024.
A removed handle from the news: @2bcontinued_4
The second example is a handle that news coverage points at and the public page no longer serves. Heavy (Erik C. Anderson, updated September 3, 2026) reports that federal prosecutors in the U.S. Attorney's Office for the District of Oregon accuse Daejon Love, 35, of posing as a San Francisco 49ers player and a wealthy investor in an alleged romance and investment fraud that took roughly $1.3 million from 26 identified women, and that a second man, Taylor Jamie Chan, 18, is charged as the supposed financial adviser. Sporting News identified his Instagram account as @2bcontinued_4, and Heavy reports the page has since been removed and that it presented him as an undrafted wide receiver with photos in 49ers gear. These are allegations as reported, not findings; the case post covers the coverage and the record in more depth.
Anyone running a daejon love instagram search today lands on a 404, and TMZ reported on September 1, 2026 that people searching the story kept landing on the unrelated real DaeJohn Love, a former indoor-football player. That is the handle-versus-id problem inside a news cycle. The account object still answers. Our record, pulled on 2026-09-05:
{
"platform": "instagram",
"username": "2bcontinued_4",
"user_id": "78250918300",
"returned_username": "Instagram User",
"bio": "Grind don't stop. Suisse made. NFL Wide Receiver @49ers #undrafted Trust god. @fabletics ꜱʟᴏᴡ ɢʀɪɴᴅ (ꜰʀᴇꜱʜ ɪɢ)",
"profile_picture": "served",
"account_status": "banned_or_disabled",
"banned": true,
"last_active_days_ago": null
}
Three things differ from the first record. The bio is the persona itself, "NFL Wide Receiver @49ers #undrafted", matching what Heavy reports the page showed, and it ends in small-cap Unicode reading "slow grind (fresh IG)". The profile picture is a real photo, still served. And the last-active oracle returns user not found rather than a number. Our observation today is a status of banned_or_disabled; we do not know when or why it was removed.
The oracle difference is the useful part. The presence signal and the profile object live in different systems and are not cleaned up together. An account that still answers the oracle, like the 858-day record, was disabled with its presence record left in place, which is consistent with a recent or reversible action. One that returns user not found but still resolves as a profile object has been scrubbed from one system and not the other, which usually means the removal has been processed further along. Neither is proof, but the first state is where a reactivation is still plausible.
"Fresh IG" in a bio is its own signal. People write it when this is not their first account: the previous one was banned, lost or abandoned. On an account that is itself now removed, you are looking at the middle of a chain, and the display name and any handle fragments in the bio are the seeds for the older account behind it.
What the id proves and what it does not
The numeric id is a join key. Every public Instagram post carries the owner's id in its JSON, so an archived post or a saved page source matches a banned account with certainty even though the handle on the archive and the placeholder on the live object no longer agree. In the case above, the id confirms the account existed, the bio confirms the persona the coverage describes, and 78250918300 is the number to match against the screenshots that circulated. Breach records that include an Instagram user id match directly.
- Same id on an archived post and a banned object: the same account, no ambiguity.
- Same handle on a screenshot and a live object: the same account only if the ids agree or the dates rule out a re-registration.
What the id does not do is name a human. A banned account with a bio and a picture is still just an account. Nothing in the record says who operated it, and a handle that looks like a real name is a string someone typed; the TMZ confusion is what happens when a name is treated as an identifier. In the news case attribution came from prosecutors and reporters, not from a tool. The username search tool guide covers corroboration; the id proves continuity of the account, not the identity behind it.
Doing this with OSINTsearch
Run the handle as a normal username search on osintsearch.org. If the account is banned or disabled, the Instagram row comes back as found with the banned flag, the numeric id, and whatever bio and picture the endpoint still serves. A free account sees the row in full: the id, the bio, the picture, the banned status and any former usernames Instagram still exposes. Starter adds the CSV and JSON export; Pro adds deep search on the pivots you find and full breach records. The pricing page has the current matrix.
Every plan exports as JSON and CSV. For banned accounts that matters more than usual: an id that resolves with a bio now can go null once a deletion grace period ends, and the export is your timestamped record that it was there.
FAQ
Can you see a deleted Instagram account?
Not the page. The numeric account object often still resolves, with the last bio and picture, for banned and deactivated accounts and during the deletion grace period. After a permanent deletion completes the object may return null.
What does "Instagram User" mean in a username search result?
It is the placeholder Instagram substitutes for the handle on a disabled account, localized to the language of the request. Read the original handle from your search input or an archive, not from the object.
How do I find the user id of an Instagram account?
A username search returns it as user_id. It also appears in the JSON of any public post and in the source of a saved profile page.
Does a banned account still show former usernames?
Usually not. The about-this-account panel does not populate for disabled accounts, so a renamed and then banned handle shows the ban and the id and little else. Archives are the fallback for rename history.
Write down the number
The habit that makes this work is boring: the first time you see an account, record its id. Usernames are released and re-registered, display names become placeholders, pages return 404. The id is the one field Instagram never reassigns, and it is the difference between "the account is gone" and "the account is banned, its last bio said this, and it went quiet 858 days ago".
