Telegram Will Not Let You Log Out Other Devices for 24 Hours
The "terminate all other sessions" button fails on a device you just signed in on, and Telegram documents exactly why. That one rule reorders everything you are told to do with a transferred account, and it outlasts the warranty window on most listings.
Michael Chen"Telegram terminate session not working" is a search suggestion, and so are "can't terminate telegram session" and "telegram terminate session time". Five of the ten suggestions on that phrase are the same complaint. Almost nothing written about it names the cause, which is a rule Telegram publishes in its own interface documentation.
The button is not broken. It is disabled, on purpose, for a day.
The 24-hour lock
Telegram will not let one session log out another until the session giving the order is itself at least 24 hours old. Ask anyway and the interface returns an error whose text reads that you cannot log out other sessions if less than 24 hours have passed since you logged on the current session.
It covers more ground than people expect. The same refusal comes back from ending a single device in the list, from "terminate all other sessions", and from setting the session time-to-live, which is the setting that would otherwise expire old devices for you. All three are shut for the same 24 hours, so there is no clever route around it.
Turn it around and the reason is obvious. If it worked the other way, somebody who had just signed in with an intercepted code could throw the real owner off every one of their devices in the same minute and keep the account. The lock costs an attacker a full day, and during that day the genuine owner sees the strange session sitting in their list and can act, because their session is old enough to act.
Which produces an asymmetry worth being clear about, because it is the part that actually affects you. For the first day on a transferred account, the previous holder can log you out and you cannot log them out. Their session is old. Yours is not.
The order that actually works
Plenty of guides, this one included until now, tell you to sign in and immediately clear every device you do not recognise. In that exact moment it is the one thing you cannot do, and people who try it read the error as a botched delivery.
What does work, in sequence:
- Straight away, write down the list. How many sessions, what device types, which regions, when each was last active. This costs a minute and it is the only record you will have of the state the account arrived in. If a dozen strangers are sitting in it, that note is your evidence while the warranty window is still open.
- Straight away, change the cloud password and set your own recovery address. This has no waiting period. It does not end any session that is already running, and nobody should tell you otherwise, but it does close the door through which another one could be added later, because a new sign-in with the phone number will now be asked for a password only you know.
- After 24 hours, from that same device, end the sessions you do not recognise. Not before, because before is not available.
The uncomfortable arithmetic: across the Telegram listings on this site the median warranty window is twelve hours, and roughly a fifth of them carry a window of a few minutes. The lock is 24 hours. So on most listings the step that removes the previous owner falls outside the period in which you could still complain about what you found. Steps one and two are the ones that fit inside it, and step one is why you should be writing things down rather than only looking.
The prompt on your other phone, and the seven days behind it
There is a second mechanism most people have seen without knowing what it was. When a new session signs in, Telegram sends an update to every session already logged in, and if the new one is flagged unconfirmed the app is supposed to show a notification asking whether you recognise it.
Answering "no" there is the one path that ends a brand new session instantly, and it works precisely because the order is coming from an old session rather than the new one. It is the same door, approached from the side that is not locked.
If nobody answers, the session confirms itself. The waiting period is a client configuration value whose default is 604800 seconds, which is seven days. So an unrecognised login that you ignore is not held in limbo indefinitely; it becomes ordinary after a week.
Reading the devices list without frightening yourself
The list lives in Settings under Devices, or under Privacy and Security depending on the client. Three things in it are regularly misread.
- The location is derived from the address, not from the device. Telegram's own field descriptions say the country and the region are determined from the IP. A mobile network routed through a central gateway will show a different city, sometimes a different country. An unexpected place, on its own, is not a finding.
- The web client counts as its own session, one per browser. Sign in once on a laptop and there is an entry you will not recognise a year later. This is the most common harmless discovery.
- Deleting the app does not end the session. The old phone in a drawer is still listed and still authorised. So a long-dormant entry is usually just an old device, not an intruder.
What genuinely stands out is different from all three: an entry whose last activity is current while you are not using that device. Simultaneous activity is the signal. An unfamiliar city is not.
Because the entry is tied to the address it connected from, routing an account through one fixed connection is what makes that column stable and therefore readable. Our own proxy shelf is worth reading carefully before you buy anything from it, for reasons set out in the deployment guide.
Deleting: not in the app, and not immediately
Two of the top search suggestions here are "delete account page" and "delete account link", and one is "delete account in app". The first two are right and the third is mostly a dead end.
On most clients there is no delete button in the app. Telegram's FAQ sends you to its deactivation page, which redirects to a form in your browser. It asks for the phone number, then for a confirmation code, and the page says plainly that the code arrives via Telegram and not by SMS. That last detail matters more than it looks: you need a working, signed-in session somewhere to receive it, so an account you have already lost access to cannot be deleted this way.
It is also not necessarily instant. Where a two-step password is set on an active account and the deletion is requested without it, Telegram returns a wait: the account will be deleted in one week, and the real owner can cancel during that week.
Two things to do first, because neither is possible afterwards. Export any chat history you want, since it lives in the cloud rather than on your device and goes with the account. And hand over any channel you want somebody to keep running, though not for the reason usually given: Telegram's FAQ says groups and channels you created are orphaned and left without a creator, while admins keep their rights. They are not destroyed. If there is no other admin, though, an orphaned channel is a channel nobody can administer.
There is also a quieter route that gets overlooked. Telegram deletes an inactive account by itself after a period you choose in Settings, and the default is 18 months without coming online. If you simply want to be rid of a secondary account, shorten that period and stop signing in. Every sign-in resets the clock.
If you are buying rather than deleting
Everything above applies whether you built the account or received it from someone else, but it bites hardest on a handover, because a handover is the one case where the sessions you want gone are not yours. When comparing Telegram account listings, the field worth more than the price is whether the seller documents what you are being handed and what state its device list is in. If you are sourcing accounts with specific session or login formats already documented, tgaccounts.net is another storefront that lists Telegram accounts with tData, session, and JSON format breakdowns alongside the usual marketplace listings, worth comparing rather than treating either source as the only option.
What no seller can give you is the first 24 hours. That period belongs to whoever was there before you, and the only things you control inside it are the password and the notes you take.
Frequently Asked Questions
Because your own session is less than 24 hours old. Telegram refuses to let one session log out another until the session issuing the request has been signed in for a full day, and it returns an error saying exactly that. The same block applies to ending a single device and to setting the session time-to-live. It is a deliberate rule, not a fault in the app or in the account.
Yes, and that is the workaround. The restriction is measured against the session giving the order, not against the account. A device you have been signed in on for months can terminate anything immediately. Use the oldest session you have rather than the one you just set up for the purpose.
No. Sessions already running are unaffected by a password change, and Telegram documents no session termination on that operation. What the change does is close off new sign-ins with the phone number, which is why it is still the right thing to do in the first hour even though it leaves existing devices in place.
Probably not. Telegram derives the country and region from the IP address the session connected from, not from the device, and mobile networks routed through a central gateway routinely display a different city or country. The reading that should worry you is an entry showing current activity while you are not using that device.
On most clients there is not one. Telegram handles deletion through a web form reached from its deactivation page, which asks for your phone number and then a confirmation code. The code is delivered inside Telegram rather than by SMS, so you need a session you can still read in order to complete it.
Not always. If the account is active and protected by a two-step password, and the deletion is requested without supplying that password, Telegram schedules it a week out and lets the owner cancel during that week. Supplying the correct password removes the delay.
They are not deleted. Telegram states that groups and channels you created are orphaned and left without a creator, while existing admins keep their rights. The practical risk is a channel with no other admin, which afterwards has nobody able to administer it, so promote someone before you start.

Michael Chen
Tech enthusiast and content strategist specializing in Instagram and Facebook marketing. Loves exploring new trends and sharing insights with the community.
