Short answer: Telegram marks every outgoing message with its state, and the marker tells you where the problem is. A clock means the message has not left your device — that is connectivity. A red exclamation mark means Telegram refused it — that is permissions or a restriction. One tick with no second tick means it reached Telegram’s servers but not the recipient — that is their end, and usually normal. A message that shows two ticks but gets no reply is not a technical problem at all. Work out which of the four you are looking at before changing any settings, because the fixes do not overlap.

Read the indicator first
| What you see | Where the message is | Cause category |
|---|---|---|
| Clock icon | Still on your device | Network or connection |
| Red exclamation mark | Rejected by Telegram | Permission or restriction |
| One tick | On Telegram’s servers, not delivered | Recipient’s device is offline |
| Two ticks | Delivered and read | Nothing is broken |
Most of the frustration around this comes from treating all four as the same problem. They are not, and three of them are not your fault.
The clock: it never left your phone
The message is queued locally. Telegram cannot reach its servers.
Work through this in order:
- Check that other apps have internet. If nothing works, it is the connection, not Telegram.
- Switch networks. Wi-Fi to mobile data or back. This resolves it more often than anything else, because the usual cause is a network that blocks or throttles Telegram rather than one that is down.
- Force-close and reopen. Telegram’s connection can get stuck in a half-open state after a network change, and a restart re-establishes it.
- Check whether Telegram is restricted where you are. Some networks — corporate Wi-Fi, some hotels, some countries — block it. Telegram’s built-in proxy settings exist for this reason: Settings → Data and Storage → Proxy.
- Check the date and time on your device. A clock that is badly wrong breaks the encrypted connection handshake. Set it to automatic.
- Update the app. Very old builds eventually stop connecting. If you installed from somewhere other than a store, this is also a good moment to read why unofficial builds are a problem and reinstall the real one.
Large files are a separate case. An upload that stalls at a percentage is not the same as a message that will not send — check the file size against your limit. The free tier caps uploads at 2 GB; Premium raises that to 4 GB.
The red exclamation mark: Telegram said no
This one is informative, because Telegram does not reject messages arbitrarily. Tap the mark — the app usually explains. The realistic causes:
You are not allowed to message this person. Telegram’s privacy settings let users restrict who can start a conversation with them. If they have not messaged you first and their settings exclude you, the message will not go.
They blocked you. No notification, no error text, just refusal. You can usually confirm it indirectly: their last-seen disappears and their profile photo stops updating.
You are posting in a group without permission. Restricted groups, slow mode, or a mute applied by an admin. Slow mode in particular looks like a fault when it is a timer.
Your account is limited. This is the one worth taking seriously. Telegram applies restrictions to accounts that have been reported for spam — typically after mass-messaging strangers, or when a newly registered account behaves like a bot. Symptoms: you can message existing contacts but not new people, and groups reject you.
To check: message @SpamBot inside Telegram. It will tell you whether a limitation is on your account and offer an appeal. This is the only route that works for this specific problem — general Telegram support cannot lift it, and the “helplines” in search results are scams.
Accounts registered with a number that many people have used before start closer to that line, which is one of the practical arguments for choosing your registration number carefully rather than taking whatever is cheapest.
One tick: it is their phone, not yours
One tick means Telegram has the message and is holding it. The recipient’s device has not collected it yet.
This is normal. Their phone is off, offline, has notifications suppressed, or is simply not open. The message is safe in Telegram’s cloud and will deliver the moment they connect. There is nothing to fix.
Two exceptions worth knowing:
- They deleted their account. The chat remains but nothing will ever deliver. The profile usually shows as “Deleted Account”.
- They are using a client that is signed out. Rare, and it resolves itself when they sign back in.
Two ticks: nothing is broken
Delivered and read. If there is no reply, that is a conversation, not a bug. The one technical possibility: they read it in a notification preview, in which case the second tick can appear before they have really engaged with it.
When it is only some chats
This pattern tells you a lot:
- One contact fails, everyone else works → their settings, or they blocked you.
- All new contacts fail, existing ones work → account limitation. Check @SpamBot.
- One group fails → group permissions or slow mode.
- Everything fails on one device only → that device’s connection or session.
That last case points at a session problem. Open Settings → Devices, terminate the session that is misbehaving, and sign in again. It is worth reviewing that screen periodically anyway — what a session can see is more than most people assume.
When it is one device but not the others
If the phone sends fine and desktop does not — or the reverse — the account is healthy and the client is not. Each install holds its own session and its own connection, which is also why running two official clients side by side is harmless.
Fix: sign out of the failing client, sign back in. If signing back in triggers a login code that never arrives, that is a different problem with its own troubleshooting order.
Common questions
Why can I receive messages but not send them? Almost always an account limitation rather than a network fault — incoming delivery does not depend on your permissions. Check @SpamBot.
Does a VPN help? On a network that blocks Telegram, yes. Otherwise it adds a hop and can make things slower or worse. Telegram’s built-in proxy support is usually the better tool for this.
I keep hitting “too many attempts” when retrying. Retrying aggressively triggers rate limits, which then look like a new fault. What rate limiting means and how long it lasts applies here too — wait it out rather than tapping again.
My messages send but the recipient says they never arrived. Check whether you are in a Secret Chat on a different device, or whether they have the conversation archived. Secret Chats are device-bound and do not sync, which produces exactly this confusion.
Could this mean my account was hacked? Not by itself. But if you are here because things are behaving strangely, the Devices screen is the place to look, and setting a cloud password is the fix if you have not already.
Wrapping up
The indicator is the diagnosis. A clock is your connection and switching networks usually clears it. A red exclamation mark is a permission or a restriction, and @SpamBot is the only thing that resolves the restriction case. One tick is the other person’s phone and needs nothing from you. Spending ten seconds identifying which one you have saves an afternoon of reinstalling an app that was never the problem.