@denissexy · Place Score 88 · 134.9K @durov · Place Score 82 · 11.2M @travel_insid · Place Score 81 · 220.6K @seeallochnaya · Place Score 81 · 77.6K @donttouchmyface · Place Score 80 · 55.4K @bbclearningenglish · Place Score 78 · 30.2K @brawlstars · Place Score 78 · 6.6K @finindie · Place Score 77 · 73.1K

Telegram responding with errors: t.me links

Started:
2026-08-17 02:48 UTC
Confirmed:
2026-08-17 04:49 UTC
Closed:
2026-08-17 06:00 UTC
Duration:
3 h 12 min · 7 episodes, 58 min
Affected:
t.me links

Episodes

The component failed and came back several times in a row. The spans below are when exactly; in between it responded normally.

  • 02:4802:53 UTCt.me links
  • 03:3503:40 UTCt.me links
  • 04:0104:06 UTCt.me links
  • 04:4805:12 UTCt.me links
  • 05:2505:32 UTCt.me links
  • 05:4705:52 UTCt.me links
  • 05:5306:00 UTCt.me links

What is happening

  1. 2026-08-17 06:00 UTC

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

  2. 2026-08-17 05:53 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.

  3. 2026-08-17 05:52 UTC

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

  4. 2026-08-17 05:47 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.

  5. 2026-08-17 05:32 UTC

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

  6. 2026-08-17 05:25 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.

  7. 2026-08-17 05:12 UTC

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

  8. 2026-08-17 05:04 UTC

    The failure is no longer limited to individual countries: every vantage point sees it.

  9. 2026-08-17 05:02 UTC

    The failure is visible from these countries: United Kingdom. The list changes as measurements come in.

  10. 2026-08-17 04:56 UTC

    The failure is no longer limited to individual countries: every vantage point sees it.

  11. 2026-08-17 04:56 UTC

    The picture has changed: was "failure in some countries", now "errors and delays". Affected: t.me links.

  12. 2026-08-17 04:55 UTC

    The failure is visible from these countries: United Kingdom. The list changes as measurements come in.

  13. 2026-08-17 04:55 UTC

    The picture has changed: was "errors and delays", now "failure in some countries". Affected: t.me links.

  14. 2026-08-17 04:49 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.

  15. 2026-08-17 04:48 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.

  16. 2026-08-17 04:06 UTC

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

  17. 2026-08-17 04:01 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.

  18. 2026-08-17 03:40 UTC

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

  19. 2026-08-17 03:35 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.

  20. 2026-08-17 02:53 UTC

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

  21. 2026-08-17 02:48 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