Telegram responding with errors: Bot API, t.me links, web app

Started:
Confirmed:
Closed:
Duration:
5 h 32 min · 12 episodes, 1 h 17 min
Affected:
Bot API, 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
  • — 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
  • — Bot API, t.me links

What is happening

  1. The problem is back: Bot API, 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.

  2. 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.

  3. 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.

  4. The picture has changed: was "outage", now "errors and delays". Affected: Bot API, t.me links, web app.

  5. The failure has spread: Bot API stopped responding too. Currently affected: Bot API, t.me links, web app.

  6. The picture has changed: was "errors and delays", now "outage". Affected: Bot API, t.me links, web app.

  7. 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.

  8. The failure has spread: web app stopped responding too. Currently affected: t.me links, web app.

  9. 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.

  10. Confirmed by 2 independent vantage points. Telegram is responding with errors: t.me links. 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.

  11. 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.

  12. 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.

  13. 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.

  14. 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.

  15. 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.

  16. 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.

  17. 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.

  18. Recovered: t.me links have been responding normally for 5 cycles in a row. The incident lasted 10 min. If it still does not work for you, the cause is no longer Telegram.

  19. We are seeing signs of trouble: t.me links. 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.

The whole day August 19, 2026All incidents