Fresh sessions cannot terminate other sessions
During the first 24 hours after login, a session cannot terminate other sessions. The restriction depends on the session performing the action, not on the target session's age.
Cerber Lab
Testing how Telegram sessions actually behave
We start with a specific question, record test conditions and publish only observations we can reproduce. If there is no result yet, we say so.
Three controlled test protocols are prepared. No test results have been published yet.
iPhone 15 · Telegram iOS
Dubai, UAE · active: now
Current deviceMacBook Pro · Telegram Desktop
Dubai, UAE · active: 12 minutes ago
Trusted deviceWindows · Telegram Web
Amsterdam, Netherlands · active: 3 hours ago
Unfamiliar session
Demo data
Documented platform behavior
What Telegram's documentation already establishes
These are Telegram's documented rules, not our experimental findings.
Telegram sends a new-login notification
Telegram sends a service message about a new-device login, including device and location information.
The cloud password is part of authorization
Two-step verification adds a password to new-device authorization. Active devices are managed separately in account settings.
Our tests
What we will test
Three prepared protocols. A result will appear only after completed, repeatable runs.
When can Telegram terminate other sessions again?
The 24-hour restriction
We will test which session's age determines the restriction, behavior around the 24-hour threshold, the response shown by clients, and how quickly a terminated session disappears and loses access.
Why does a session show an unfamiliar city?
Device labels and network location
We will compare the real device and network with the device list: Device, IP-based country and city, and last activity on Android, iOS, Desktop and Web, using mobile networks and different VPN exit points.
What happens to an open session when two-step verification changes?
Two-step verification and existing sessions
We will use a defined set of safe actions to check what an already authorized session can still do after the password is enabled or changed, and when behavior changes.
Method
How we run tests
Four rules keep repeatable findings separate from one-off observations.
Separate test accounts
Tests use company test accounts and devices. No personal accounts or other people's sessions.
Recorded conditions
Before each run we record the client and version, operating system, network and time from an independent clock. We repeat runs after client updates.
Repeated runs
One run does not establish a finding. We publish an observation after it repeats, together with the number of runs.
Sanitized evidence and clear limits
Screenshots and logs exclude phone numbers, addresses and device identifiers. Each conclusion states what it does not cover.
Publication
Results
No results have been published yet. The first result will appear after repeatable runs are completed and the supporting evidence is prepared.
Sources
Sources and updates
Official Telegram documentation supporting the platform rules above.
- Telegram API: account.resetAuthorization
- Telegram API: user authorization
- Telegram: new-login notification
- Telegram FAQ
English edition updated: 2026-10-12
Start with a free account check
Review active sessions, two-step verification and connected access.