Telegram responding with errors: media delivery, t.me links, web app
- Started:
- Confirmed:
- Closed:
- Duration:
- 9 h 17 min · 20 episodes, 3 h 19 min
- Affected:
- media delivery, t.me links, web app
Episodes
The component failed and came back several times in a row. The spans below are when exactly; in between it responded normally.
- — t.me links, web app
- — t.me links
- — t.me links
- — t.me links
- — t.me links
- — t.me links
- — t.me links
- — t.me links
- — t.me links
- — t.me links
- — t.me links
- — t.me links
- — t.me links
- — t.me links
- — t.me links
- — t.me links
- — t.me links
- — t.me links
- — t.me links
- — t.me links
What is happening
The problem is back: t.me links. This is episode 20 of the same incident — the previous one closed less than an hour ago, so we are not opening a separate record. The component keeps flapping.
The problem is back: t.me links. This is episode 19 of the same incident — the previous one closed less than an hour ago, so we are not opening a separate record. The component keeps flapping.
The problem is back: t.me links. This is episode 18 of the same incident — the previous one closed less than an hour ago, so we are not opening a separate record. The component keeps flapping.
The problem is back: t.me links. This is episode 17 of the same incident — the previous one closed less than an hour ago, so we are not opening a separate record. The component keeps flapping.
The problem is back: t.me links. This is episode 16 of the same incident — the previous one closed less than an hour ago, so we are not opening a separate record. The component keeps flapping.
The problem is back: t.me links. This is episode 15 of the same incident — the previous one closed less than an hour ago, so we are not opening a separate record. The component keeps flapping.
The problem is back: t.me links. This is episode 14 of the same incident — the previous one closed less than an hour ago, so we are not opening a separate record. The component keeps flapping.
The problem is back: t.me links. This is episode 13 of the same incident — the previous one closed less than an hour ago, so we are not opening a separate record. The component keeps flapping.
The problem is back: t.me links. This is episode 12 of the same incident — the previous one closed less than an hour ago, so we are not opening a separate record. The component keeps flapping.
The problem is back: t.me links. This is episode 11 of the same incident — the previous one closed less than an hour ago, so we are not opening a separate record. The component keeps flapping.
The problem is back: t.me links. This is episode 10 of the same incident — the previous one closed less than an hour ago, so we are not opening a separate record. The component keeps flapping.
The problem is back: t.me links. This is episode 9 of the same incident — the previous one closed less than an hour ago, so we are not opening a separate record. The component keeps flapping.
The problem is back: t.me links. This is episode 8 of the same incident — the previous one closed less than an hour ago, so we are not opening a separate record. The component keeps flapping.
The problem is back: t.me links. This is episode 7 of the same incident — the previous one closed less than an hour ago, so we are not opening a separate record. The component keeps flapping.
The problem is back: t.me links. This is episode 6 of the same incident — the previous one closed less than an hour ago, so we are not opening a separate record. The component keeps flapping.
The failure has spread: media delivery stopped responding too. Currently affected: media delivery, t.me links, web app.
The problem is back: t.me links. This is episode 5 of the same incident — the previous one closed less than an hour ago, so we are not opening a separate record. The component keeps flapping.
The problem is back: t.me links. This is episode 4 of the same incident — the previous one closed less than an hour ago, so we are not opening a separate record. The component keeps flapping.
Recovered: t.me links, web app have been responding normally for 5 cycles in a row. The incident lasted 48 min. If it still does not work for you, the cause is no longer Telegram.
Confirmed by 2 independent vantage points. Telegram is responding with errors: t.me links, web app. Some requests go through and some do not, which is why it works for some people and not for others. If a message fails to send, try again in a minute; there is no need to reinstall the app.
The problem is back: t.me links. This is episode 3 of the same incident — the previous one closed less than an hour ago, so we are not opening a separate record. The component keeps flapping.
The problem is back: t.me links. This is episode 2 of the same incident — the previous one closed less than an hour ago, so we are not opening a separate record. The component keeps flapping.
The signs were not confirmed. For 15 minutes no second independent vantage point saw the problem, so we are closing this watch. Telegram is working.
We are seeing signs of trouble: t.me links, web app. So far only one vantage point out of three reports it, so we are not calling it an outage — we are checking. If Telegram does not open for you, wait a few minutes and try again.