How to Do a Telegram Shadowbanned Check in 2026

what you will end up with

A telegram shadowbanned check is not a single button press. It is a layered diagnostic across five distinct failure modes, each of which Telegram handles through a different internal system. By the end of this guide you will know which layer is broken for your account, whether the problem is account-level, IP-level, or regional interference, and what your realistic options are to fix it. The whole process takes about 20 minutes with the right setup. No root access, third-party apps, or paid tools required.

before you start

You need two Telegram accounts: your primary (the one you suspect is restricted) and a clean test account registered to a separate phone number you have never used for Telegram. A fresh SIM from any carrier works. Run them on separate physical devices if you can. The Telegram desktop and mobile clients sometimes cache visibility state differently, and that will muddy your results. Make sure your primary account is on Telegram version 10.x or later. On Android, check under Settings > About Telegram. On iOS, go to Settings and look at the version field near the bottom.

# Android only: confirm Telegram version via adb (useful if managing accounts programmatically)
adb shell dumpsys package org.telegram.messenger | grep versionName
# expected output: versionName=10.x.x or higher
# if lower, update from the Play Store before starting the diagnostic

If you do not have a second SIM, a temporary virtual number works for the test account. Do not use the same virtual number provider for both accounts. If both accounts share infrastructure, the test will not give you useful signal.

the step-by-step

1. Attempt a cold DM to a stranger.

From your primary account, find an active public channel with recent comments. Try to open a direct message with someone you have never messaged before. If Telegram returns “Sorry, you can’t send messages to this user” immediately, or if the message sits unsent with no error but also no delivery confirmation, your account has outgoing DM restrictions applied. This is usually the first external sign of a flag from Telegram’s automated anti-spam layer. It does not always indicate a permanent restriction. It does mean the account is in a constrained state. Read more about the mechanisms behind account flags in the why Telegram bans accounts post.

2. Query @SpamBot from your primary account.

Open a chat with @SpamBot (official, verified, blue checkmark, no profile photo). Send /start. The response is one of three things: a clean bill of health, a temporary restriction with an end date, or an open-ended restriction with no date. If the bot confirms a restriction, screenshot the message before tapping anything. You will need that if you appeal. If SpamBot says your account is clean but you still have symptoms from step 1, the restriction is not account-level. Keep going.

3. Search your username from the clean test account.

This is the single most diagnostic step in a telegram shadowbanned check. Log into your clean test account on the second device. Open the search bar and type your primary account’s username exactly, including the @ symbol. If your profile does not appear, or appears only after a significant delay with no message preview or recent activity, your account’s discoverability is suppressed. Search suppression is a separate system from the DM restriction in step 1. An account can send messages normally and still be invisible to anyone searching for it by handle. Telegram does not notify you when this happens.

4. Check your channel or group from outside.

If you run a channel or group, search for it by full name and handle from the clean test account. If it does not appear in search results but is still accessible via a direct t.me/yourchannel link, the channel is search-restricted. Telegram applies this to channels that have accumulated a high volume of spam reports or that the automated system has flagged for guideline violations. Operator circles sometimes call it “search invisibility,” and it is distinct from account suspension. The channel still functions. Existing members can use it. New discovery is suppressed.

5. Run a web preview check on your public handle.

Open a browser (not the Telegram app) and visit https://t.me/yourusername. Then do the same from a clean device on a different network.

# check whether Telegram's preview layer is serving your channel metadata publicly
curl -s "https://t.me/yourusername" | grep -o 'og:title[^"]*"[^"]*"' | head -1
# if the output shows your channel name, the page is publicly indexed and discoverable
# if you get a generic Telegram title, an empty result, or an error page, visibility is suppressed
# run this from a clean residential IP; datacenter ASNs get inconsistent responses from Telegram's CDN

Replace yourusername with your actual handle. Results from a datacenter IP or a well-known VPN exit node are not reliable. Telegram’s CDN responds differently depending on the ASN. This is one reason a static residential or mobile IP matters for accurate diagnostics, a topic covered in depth in the dedicated vs shared mobile IPs post.

6. Test reaction propagation.

Post something to your channel from the primary account. Ask your clean test account (or a trusted contact in a different country) to react to the post. Watch whether the reaction appears on your side. If the reacting account sees its own reaction reflected but your view shows zero reactions, or if the reaction count stays stuck, broadcast delivery from your account is being silently throttled. This is less common than DM restrictions or search suppression, but it does happen during active review periods when Telegram’s system is rate-limiting an account’s reach while an investigation is in progress.

7. Confirm direct message delivery with a trusted contact.

From your primary account, send a short message to someone you know is online. Ask them explicitly: did it arrive, and when? One tick means the message reached Telegram’s server but has not been delivered to the recipient’s device. Two ticks means delivered. Blue ticks mean opened. If a known-online contact receives a message with a timestamp that is minutes or hours behind when you sent it, delivery throttling is active on your session. That is different from DM restrictions in step 1, which prevent outgoing messages entirely. Throttling lets messages through but delays or queues them.

8. Rule out regional blocking with OONI.

Before concluding your account is shadowbanned, verify that Telegram itself is reachable from your network. telegram/" target="_blank" rel="noopener">OONI’s Telegram network test runs a probe that checks connectivity to Telegram’s web and app endpoints from your current ISP. If the probe shows interference, the problem is your network, not your account. This is especially relevant if you are in Iran, Russia, Belarus, or Ethiopia, countries where Telegram has faced documented state-level blocking. Freedom House’s Freedom on the Net 2024 report tracks which countries have active Telegram restrictions at the ISP level. If OONI shows interference and your account passes steps 1 through 7, the issue is not a shadowban at all.

what can go wrong

SpamBot says clean but symptoms persist. SpamBot reflects account-level restrictions only. Search suppression and IP reputation are separate layers and SpamBot does not report on either. If the bot clears your account but step 3 fails, the discoverability problem is in Telegram’s indexing system, not in the account’s messaging permissions. The fix is time and legitimate engagement, not an appeal. Avoid behaviors that can re-trigger the flag: mass invites, identical messages to many new contacts, or unofficial clients that make high-frequency API calls.

DMs fail only to contacts in certain countries. Not every delivery failure is account-wide. Cross-border delivery issues sometimes trace to relay node outages or regional network partitioning on Telegram’s infrastructure side, not your account. The telegram.org/api/errors" target="_blank" rel="noopener">Telegram API error code reference documents the specific codes returned during server-side outages. If your DMs work to contacts in one region but fail to another, check whether Telegram has a known outage on that corridor before treating it as an account problem.

The account locks entirely during the diagnostic. Triggering repeated login attempts from multiple IPs in a short window, or hitting rate limits with automated tools during testing, can escalate a minor flag to a temporary full lock. If Telegram sends an SMS verification request during this process, complete it promptly with the correct code. Do not retry the verification repeatedly. One bad sequence within the verification window extends the lockout. If you end up locked out, stop all activity and wait out the window (usually 24 hours) before trying again.

Search suppression does not lift after SpamBot clears you. SpamBot clearing your account does not instantly restore search visibility. Telegram’s search index updates on its own schedule. Accounts that have been search-suppressed sometimes take 3 to 14 days to reappear in search results after the underlying flag is resolved, even with no further violations. This is not a second ban. It is a caching delay. There is no manual flush available to users.

how this looks on managed hosting

When a Telegram session runs on a telegramvault cloud phone, steps 5 and 8 give you cleaner signal from the start. The session is pinned to a single static Singapore mobile IP on a real SIM (SingTel, M1, StarHub, or Vivifi depending on availability). No VPN layer, no proxy, no rotation. That means if OONI shows clean connectivity and the curl check in step 5 returns nothing, you know with more confidence that the problem is the account and not the connection. The IP cannot be the variable because it has not changed.

Steps 1 through 7 run identically. You access the live Telegram client through a browser-based STF session from anywhere in the world, so you are watching the actual session, not a desktop client’s interpretation of it. Customers running multiple accounts on separate cloud phones can also use one phone as the clean test device for steps 3 through 6, rather than needing to provision a second SIM separately. For accounts that have gone through a telegram shadowbanned check and come back clean on account health but were previously operating on a datacenter IP or shared residential pool, migrating to a dedicated mobile SIM often resolves residual search suppression. Telegram’s indexing systems treat mobile carrier ASNs differently from datacenter ASNs. The session’s IP history is part of what the scoring system sees when it decides whether to surface an account in search. The BYO number Telegram hosting post explains how the login flow works if you want the session stability without handing your number to a hosting provider.

recovery if you mess up

If the diagnostic accidentally triggers additional restrictions, here is the sequence.

Complete any SMS or email verification Telegram sends, immediately. Use the same device you normally use for this number if at all possible. Once back in, stop all outgoing activity for 48 hours. No mass messages, no group invites, no API calls. Let the account sit idle and warm.

After 48 hours, re-run steps 1 and 2. If SpamBot still shows an active restriction, respect the listed end date. Telegram support is reachable via the in-app “Report a problem” flow or by messaging the support bot directly from within Telegram. Realistic turnaround on restriction appeals ranges from 3 to 21 days for first-time appeals and longer for repeat restrictions. The Electronic Frontier Foundation has documented platform restriction opacity across multiple messaging apps, and Telegram does not publish specific thresholds for what triggers a restriction or what reverses one. That is by design. Write your appeal in plain factual language. No emotional appeals, no legal threats. Short and specific wins more often than long and frustrated.

If the account is unrecoverable and the phone number is one you own, Telegram releases numbers for re-registration after six months of inactivity. Accounts tied to your real number are recoverable that way. Accounts built on recycled virtual numbers are often not, because the number itself carries restriction history from previous users that Telegram’s system has already scored.

Understand why flags get triggered. The telegram shadowbanned check above tells you what is broken, not always why. The why Telegram bans accounts post goes through the trigger categories: spam complaint volume, API abuse patterns, unofficial clients, and behavioral signals the automated system scores as high-risk. Reading it before attempting recovery reduces the chance of repeating the trigger accidentally.

Choose the right IP setup before you get flagged. A significant portion of unexplained Telegram restrictions trace back to IP history rather than account behavior. Shared residential pools, rotated datacenter IPs, and consumer VPNs all carry risk from previous users. The dedicated vs shared mobile IPs post breaks down what makes a mobile carrier IP a different risk category, what the practical tradeoffs are, and when the cost difference is worth it.

Host your session without handing over your number. If you want session stability on a dedicated IP without giving a third party access to your OTP, the BYO number Telegram hosting post explains the model. You authenticate once with your own number on your own device. The session then runs on the cloud phone. No one on the hosting side ever sees your verification code.

Know your regional context. If your country’s mobile IPs carry a reputation flag with Telegram’s scoring system (this happens in some markets where there has been enforcement pressure or known abuse), the why Singapore mobile IPs post explains why Singapore carrier ASNs sit in a cleaner reputation zone and what that means for message delivery rates and search visibility.

final word

A telegram shadowbanned check is not a single test. It is a stack: account restrictions, search indexing, delivery throttling, and network-level interference each fail differently and require different fixes. Work through each layer in order before drawing conclusions. If every layer passes but reach is still degraded, the session’s IP history is almost always the remaining variable. The telegramvault waitlist is the fastest path to a dedicated static Singapore SIM IP if that is where the diagnostic lands you.