Valid
The session works and Telegram lets the account in. You can use it in any module.
- What to do
- Nothing. Before an important task, click “Check spamblock”: the regular check doesn't see it.
Reference
Telegram account statuses
What each status in the account manager means, whose decision it is — Telegram's or the service's, whether it clears by itself and what to do about it.
Account is working
NeuroCommenting +1
The module name is shown instead of the status: the account is busy in a task, “+1” means one more. The real status comes back when the tasks end.
- What to do
- Nothing. The account's tasks are listed in its card.
Checking and preparing
Service statuses: we don't know yet whether the account is alive, or we are getting it ready to work.
Unchecked
The account was just uploaded and hasn't been checked yet.
- Clears by itself?
- No.
- What to do
- Click “Check Accounts”.
Checking...
The service is logging into the session and asking Telegram about the account. “Checking proxy...” is the same for the proxy.
- Clears by itself?
- Yes, usually within a minute. If a check gets stuck, the account returns to its previous status in 10–15 minutes.
- What to do
- Wait.
Converting...
The uploaded TDATA folder is being turned into a session the service can work with.
- Clears by itself?
- Yes, usually in a couple of minutes. If conversion gets stuck, the status changes to “Connection failed” after about 15 minutes.
- What to do
- Wait. If it turned into “Connection failed”, click “Check”.
Converted
TDATA was turned into a session successfully, but the account hasn't been checked yet.
- Clears by itself?
- No.
- What to do
- Click “Check Accounts”.
Awaiting proxy
TDATA was uploaded without a proxy, and conversion only runs through a proxy.
- Clears by itself?
- No.
- What to do
- “Assign Proxy”. Conversion starts on its own as soon as the proxy passes the check.
Telegram limits
The account is alive, but Telegram has restricted it or won't let it connect. Some of these clear by themselves, some don't — see each one.
Quarantine
Telegram answered with FloodWait, asking to slow down, and the service set the account aside. A timer is shown next to it. It can also sit on top of another status: “Valid (Quarantine 2h 5m)”.
- Clears by itself?
- Yes, by the timer. Usually twice as long as Telegram asked: at least an hour, at most a day. In messaging modules after a spam limit — exactly as long as Telegram said.
- What to do
- Wait. There is a “Lift Quarantine” button, but if Telegram still holds the limit, the account gets a new quarantine right away. If it happens often, increase the module's delays.
Connection failed
We couldn't reach Telegram through the account's proxy: the proxy isn't answering or Telegram is temporarily throttling its IP. The account itself isn't penalised.
- Clears by itself?
- Sometimes. The service re-checks these accounts by itself, but no more often than every 3 days.
- What to do
- Faster: click “Check” once the proxy works again, or switch to a residential or mobile proxy. If the hint says Telegram sees the session from two addresses, changing the proxy won't help: log in by phone number via “Add Account”.
Spamblock
Telegram restricted sending for this account: because of recipients' reports, because of the phone number itself, or because of signs of automation. What exactly is forbidden and for how long depends on the type — see “Spamblock types”.
- Clears by itself?
- A block with a date lifts on that date. The service re-checks spamblocks in the background: expired ones first, the rest every few days.
- What to do
- “Check spamblock” to see the type and date right away.
Spamblock types
The type comes from @SpamBot's answer. It decides what the account can still do and whether the block lifts by itself.
Temporary until 11/01
@SpamBot named the lift date. Until then the account can't message strangers or invite to groups. Comments and reactions are formally allowed, but comments from such accounts get through noticeably less often.
- Clears by itself?
- Yes, on that date.
- What to do
- Modules take these accounts on their own, except DM mailing, the inviter and story mentions. Or wait for the date.
Block lifted 11/01
The lift date @SpamBot named has passed. Most likely the block is gone.
- Clears by itself?
- Already passed.
- What to do
- “Check spamblock” to refresh the status: the regular “Check” doesn't ask @SpamBot.
Unconfirmed
The status was set from Telegram's answer to a sent message; @SpamBot hasn't been asked yet. The duration is unknown, and it isn't necessarily permanent.
- What to do
- “Check spamblock” to see what it really is. Don't delete the account before checking. Modules only take it via “Show spamblocked”.
Permanent
@SpamBot gave no end date. Comments and reactions from such accounts usually don't get through either, so modules only take them via “Show spamblocked”.
- Clears by itself?
- As a rule, no. The exception is a block “because of the number” on fresh accounts: it sometimes lifts by itself within a few days — re-check before deleting.
- What to do
- “Lift spamblock” files an appeal. Telegram moderators decide within hours to days, and rarely approve.
Appealing
The appeal is filed; waiting for Telegram moderators.
- Clears by itself?
- The decision arrives by itself, in a few hours to a few days.
- What to do
- Wait, then “Check spamblock”.
Permanent, appeal rejected
Telegram answered that the restriction won't be lifted: the appeal was already rejected or the block is final.
- Clears by itself?
- No.
- What to do
- Use it where no messaging is needed, or replace the account.
Closed by Telegram
This is Telegram's own decision. The service cannot lift it.
Frozen
Telegram froze the account: it can do almost nothing. This is Telegram's decision, not the service's.
- Clears by itself?
- Almost never. Telegram deletes a frozen account after 30 days.
- What to do
- Appeal through @SpamBot with the “This is a mistake” button: the bot asks for a description, full name and e-mail. The service doesn't file it for you. If it was frozen before you uploaded it to us, ask the seller for a replacement.
Banned
Telegram banned the account or its phone number.
- Clears by itself?
- No.
- What to do
- Replace the account.
Deactivated
Telegram deleted the account. It can't be restored.
- Clears by itself?
- No.
- What to do
- Replace the account.
Invalid Phone
Telegram doesn't recognise this account's phone number.
- Clears by itself?
- No.
- What to do
- Check the number with the seller or replace the account.
Session lost
The account itself may be fine, but the login key the service used no longer works. The “Reauthorize” button almost never helps here: it logs in through the same dead key. Keep in mind: by our measurements, accounts with a new session get frozen almost twice as often.
Needs Reauth / Unauthorized
Telegram no longer accepts this session's key: someone logged out, the session was terminated from another device, or it expired.
- Clears by itself?
- No.
- What to do
- “Add Account” and log in by phone number — the same record in your workspace comes back with a new key. You'll need the code from SMS or the app and the 2FA password if there is one. Or delete the record and upload a new session from the seller — the old file is dead too. A new session doesn't log others out: after 24 hours click “Terminate Sessions”. An account bought on the Marketplace can't be restored this way: you don't have its phone number, and there's no login without it. Bought accounts come with no replacement or warranty.
Deauthorized
The session was revoked: the owner or seller terminated it in settings, or Telegram reset the key.
- Clears by itself?
- No.
- What to do
- Log in by phone number via “Add Account” — the record comes back. Or delete it and upload a new session from the seller. 24 hours after logging in, click “Terminate Sessions”, or you may be kicked out again. An account bought on the Marketplace can't be restored this way: you don't have its phone number, and there's no login without it. Bought accounts come with no replacement or warranty.
Login from another IP
One session was used from two addresses at once: the seller kept a copy, the session is open on another device, or a rotating proxy changed its IP. Telegram resets the key when that happens.
- Clears by itself?
- No.
- What to do
- Log in by phone number via “Add Account” or get a new session from the seller. Use a static proxy without rotation. 24 hours after logging in, click “Terminate Sessions” so the seller's copy stops interfering. An account bought on the Marketplace can't be restored this way: you don't have its phone number, and there's no login without it. Bought accounts come with no replacement or warranty.
Session Expired
The session no longer opens: Telegram considers it outdated, or the session file is damaged.
- Clears by itself?
- No.
- What to do
- Log in by phone number via “Add Account”, or delete the record and upload a new session.
Upload errors
Something is wrong with the file you uploaded: the session or the TDATA folder.
Invalid
The account has neither a session nor TDATA — there's nothing to work with.
- Clears by itself?
- No.
- What to do
- Delete the record and upload the account again.
Conversion Failed
TDATA couldn't be turned into a session: the folder is incomplete or damaged.
- Clears by itself?
- No.
- What to do
- Upload TDATA again, the whole folder as the seller gave it.
TDATA is locked by a local password
The TDATA has a Telegram Desktop local passcode; without it the files can't be read.
- Clears by itself?
- No.
- What to do
- Turn off the passcode in Telegram Desktop and upload TDATA again.
Session File Error
The session file can't be read: it's damaged or in an unknown format.
- Clears by itself?
- No.
- What to do
- Upload the session again.
Duplicate
This Telegram account already exists: in your workspace (same Telegram ID, phone or session) or in someone else's GramGPT workspace.
- Clears by itself?
- No.
- What to do
- If it's alive in your workspace, work with it. If the record there is dead, delete it and upload again, or log in by phone number via “Add Account”. If the account is in someone else's workspace, contact support.
Batch labels
Shown next to the status of dead accounts when it's clear that a whole batch failed, not a single account.
Frozen in a batch
Telegram froze this account within the same half hour as at least 4 other accounts of yours. That is how it takes down a whole batch or a group of linked accounts. The label is based on freeze timing only and does not prove the cause: it can be a weak batch or the same action done to many accounts (for example, the same link in the bio).
Frozen after profile change
Telegram froze these accounts shortly after their profile was changed (for example, the same link in the bio). That is how it takes down linked accounts. The label is set when most of the accounts frozen together had their profile changed through GramGPT within an hour before the freeze. Don't put the same link in the bio of many fresh accounts at once.
Batch wiped out
From this upload (your accounts uploaded on one day) half or more failed in the first week: frozen, banned, spamblocked or session lost. Most often it's a weak batch, but spamblocks and lost sessions can also come from mailings or rotating proxies. The survivors work, but better not put them on valuable tasks.
Wave (country)
Over a few days Telegram froze a whole series of registrations from one country and one day — across different customers of the service. It's a decision about the batch, not about your settings.
Dead before upload
Telegram froze the account while it was still with the seller, before it was uploaded to your workspace. It never worked with us: ask the seller for a replacement.
GramGPT lifts quarantine by the timer and re-checks accounts in the background on its own.
Try it free