@ecotopor · Place Score 88 · 1.2M @denissexy · Place Score 88 · 135.1K @seeallochnaya · Place Score 84 · 77.8K @travelwithrutravel · Place Score 84 · 20.5K @durov · Place Score 82 · 11.1M @finindie · Place Score 82 · 73.1K @grillhub · Place Score 82 · 59.3K @travel_insid · Place Score 80 · 220.6K

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

Started:
2026-08-19 18:17 UTC
Confirmed:
2026-08-19 22:47 UTC
Closed:
2026-08-19 23:49 UTC
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.

  • 18:1718:27 UTCt.me links
  • 18:5318:54 UTCt.me links
  • 19:5219:53 UTCt.me links
  • 19:5419:55 UTCt.me links
  • 19:5920:00 UTCt.me links
  • 20:1320:14 UTCt.me links
  • 20:2420:25 UTCt.me links
  • 20:2620:40 UTCt.me links
  • 21:2521:52 UTCt.me links
  • 22:2622:31 UTCt.me links
  • 22:4622:54 UTCt.me links
  • 23:4223:49 UTCBot API, t.me links

What is happening

  1. 2026-08-19 23:42 UTC

    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. 2026-08-19 22:46 UTC

    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. 2026-08-19 22:26 UTC

    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. 2026-08-19 21:44 UTC

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

  5. 2026-08-19 21:43 UTC

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

  6. 2026-08-19 21:43 UTC

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

  7. 2026-08-19 21:25 UTC

    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. 2026-08-19 20:28 UTC

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

  9. 2026-08-19 20:26 UTC

    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. 2026-08-19 20:26 UTC

    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. 2026-08-19 20:24 UTC

    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. 2026-08-19 20:13 UTC

    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. 2026-08-19 19:59 UTC

    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. 2026-08-19 19:54 UTC

    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. 2026-08-19 19:52 UTC

    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. 2026-08-19 18:54 UTC

    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. 2026-08-19 18:53 UTC

    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. 2026-08-19 18:27 UTC

    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. 2026-08-19 18:17 UTC

    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 state on this page is recalculated every minute.

What it was

We do not name a cause: we have availability measurements, not access to Telegram's infrastructure.

All incidents