Statuspy
Communication

Is Telegram down right now?

No, it’s up.

Telegram appears to be up and running normally.

checked responded in 260msHTTP 200

Over the last 7 days, Telegram has answered our automated checks with 100.00% availability and a typical response time of ~266 ms. The most recent outage began 2026-08-22 20:51 UTC and lasted 15m (severity: degraded).

Telegram is a cloud-based messaging platform with very large group chats, channels, and a bot API. Because messages live server-side rather than only on the device, an outage prevents access to history as well as new messages, and problems are often limited to one datacentre serving a particular region.

Is Telegram down for everyone or just you?

Our automated checks are reaching Telegram normally right now, and it answered our last one in 260ms. That makes any trouble you are hitting more likely to be local to your connection, account or network than a full outage, which usually means you can fix it from your end.

Still not working for you?Try the fixes

Telegram response time (last 24h)

Last 24hpeak 311 ms

Telegram incident history (last 90 days)

JulAugSep
  • up
  • slow
  • down
  • no reading
DateWhat happenedDurationSeverity
Measured by our checks15mDegraded
Measured by our checks15mDegraded
Measured by our checks15mDegraded
Measured by our checks15mDegraded
Measured by our checks15mDegraded
Measured by our checks15mDegraded
Measured by our checks15mDegraded
Measured by our checks15mDegraded
Measured by our checks15mDegraded
Measured by our checks15mDegraded
Measured by our checks15mDegraded
Measured by our checks20mDegraded

Telegram uptime

100.00%
7 days
99.98%
30 days
99.96%
90 days

Measured since 2026-08-12. Windows reaching further back are averaged over the 39 days we watched, not the full period. Counts our own checks. Days Telegram reported an incident are coloured in the timeline above but do not change this figure.

What to do if Telegram is down for just you

  • Check whether delivery is delayed rather than failed, since messages are queued and usually arrive once a backlog clears.
  • Test a second channel or recipient domain, because incidents are often limited to one carrier, region, or mailbox provider.
  • Confirm you have not hit a rate or spend limit, which returns the same errors as an outage.
  • Verify your webhook endpoint is still responding, as a receiving failure on your side mimics a provider problem.

Frequently asked questions

Telegram appears to be up and running normally. Last checked 2026-09-19 03:50 UTC.

Related services