Is Telegram down?
Telegram is working
Messages arrive, channels open, images load. We check every minute.
Measured just now
We post in @telega_place when Telegram is back.
By component
normal · 469 measurements over the last hour
normal · 6588 measurements over the last hour
normal · 230 measurements over the last hour
normal · 3277 measurements over the last hour
By country
How Telegram opened from different countries over the last hour. During an outage the picture refreshes more often.
Yours may differ: we look from data centres, you look from mobile or home internet. To find out about yourself, press «Check from here».
- Brazil100% answered · 22 measurements
- Germany100% answered · 22 measurements
- United Kingdom100% answered · 22 measurements
- Indonesia100% answered · 22 measurements
- India100% answered · 22 measurements
- Netherlands91% answered · 22 measurements
- Russia0% answered · 22 measurements
- United States95% answered · 22 measurements
Data centres
We watch Telegram data centres one by one. If one of them plays up, Telegram is slow for some people and fine for everyone else.
All five data centres answer.
- DC1: 100% answered · 30 measurements
- DC2: 100% answered · 30 measurements
- DC3: 100% answered · 30 measurements
- DC4: 100% answered · 30 measurements
- DC5: 100% answered · 30 measurements
Check from your side
This button asks your browser for three static Telegram files and shows whether your network reaches them. Until you press it, this page sends nothing to Telegram.
Vantage points
- Our serverreporting
- Worldwide probesreporting
47 days by component
One stripe is a day, coloured by the worst state that day. Grey — before the monitor started on 16 August.
Past incidents
- 2026-08-27 · 1 h 23 min · 3 episodesTelegram responding with errors: t.me links
- 2026-08-25 · 18 min · 2 episodesTelegram outage: t.me links
- 2026-08-24 · 1 h 44 min · 6 episodesTelegram responding with errors: Bot API, data centres, media delivery, t.me links, web app
- 2026-08-24 · 14 minTelegram responding with errors: t.me links
- 2026-08-24 · 32 min · 2 episodesTelegram responding with errors: t.me links
- 2026-08-23 · 4 h 32 min · 2 episodesTelegram responding with errors: t.me links, web app
- 2026-08-22 · 15 minTelegram responding with errors: t.me links
- 2026-08-22 · 7 minTelegram responding with errors: t.me links
- 2026-08-21 · 40 min · 2 episodesTelegram responding with errors: Bot API, media delivery, t.me links, web app
- 2026-08-21 · 10 minTelegram responding with errors: t.me links
83 more unconfirmed watches
Grey — watches never confirmed by a second vantage point.
- 2026-10-01 04:41 UTCTelegram responding with errors: t.me links, web app
- 2026-10-01 04:27 UTCTelegram responding with errors: t.me links
- 2026-09-30 19:03 UTCTelegram responding with errors: t.me links
- 2026-09-30 14:31 UTCTelegram responding with errors: t.me links
- 2026-09-30 04:30 UTCTelegram responding with errors: t.me links
- 2026-09-29 04:29 UTCTelegram responding with errors: t.me links
- 2026-09-28 23:13 UTCTelegram responding with errors: Bot API
- 2026-09-28 04:27 UTCTelegram responding with errors: Bot API, t.me links
- 2026-09-27 04:28 UTCTelegram responding with errors: t.me links
- 2026-09-26 04:28 UTCTelegram responding with errors: t.me links, web app
- 2026-09-25 04:28 UTCTelegram responding with errors: t.me links
- 2026-09-24 04:26 UTCTelegram responding with errors: t.me links
- 2026-09-23 04:27 UTCTelegram responding with errors: t.me links
- 2026-09-22 04:27 UTCTelegram responding with errors: t.me links, web app
- 2026-09-21 04:28 UTCTelegram responding with errors: t.me links
- 2026-09-20 04:27 UTCTelegram responding with errors: t.me links
- 2026-09-19 12:10 UTCTelegram responding with errors: t.me links
- 2026-09-19 09:18 UTCTelegram responding with errors: t.me links
- 2026-09-19 04:27 UTCTelegram responding with errors: t.me links
- 2026-09-18 18:53 UTCTelegram responding with errors: t.me links
- 2026-09-18 04:28 UTCTelegram responding with errors: t.me links, web app
- 2026-09-18 01:44 UTCTelegram outage: t.me links
- 2026-09-17 15:10 UTCTelegram responding with errors: t.me links
- 2026-09-17 04:26 UTCTelegram responding with errors: t.me links, web app
- 2026-09-16 20:29 UTCTelegram responding with errors: t.me links
- 2026-09-16 05:07 UTCTelegram responding with errors: t.me links
- 2026-09-14 17:22 UTCTelegram responding with errors: t.me links
- 2026-09-13 22:32 UTCTelegram responding with errors: t.me links
- 2026-09-13 17:54 UTCTelegram responding with errors: t.me links
- 2026-09-13 12:00 UTCTelegram outage: Bot API
- 2026-09-12 16:22 UTCTelegram outage: Bot API
- 2026-09-12 02:53 UTCTelegram responding with errors: data centres
- 2026-09-11 23:02 UTCTelegram outage: Bot API
- 2026-09-11 16:12 UTCTelegram outage: Bot API
- 2026-09-11 11:18 UTCTelegram outage: Bot API
- 2026-09-11 06:06 UTCTelegram outage: Bot API
- 2026-09-10 20:45 UTCTelegram outage: Bot API
- 2026-09-10 15:49 UTCTelegram responding with errors: Bot API
- 2026-09-09 12:23 UTCTelegram responding with errors: data centres
- 2026-09-09 08:30 UTCTelegram responding with errors: data centres
- 2026-09-08 22:28 UTCTelegram responding with errors: media delivery
- 2026-09-08 13:44 UTCTelegram responding with errors: data centres
- 2026-09-08 06:28 UTCTelegram responding with errors: data centres
- 2026-09-08 02:29 UTCTelegram responding with errors: data centres
- 2026-09-07 19:23 UTCTelegram responding with errors: data centres
- 2026-09-07 18:05 UTCTelegram responding with errors: data centres
- 2026-09-06 19:56 UTCTelegram responding with errors: data centres
- 2026-09-04 01:45 UTCTelegram responding with errors: data centres
- 2026-09-03 13:18 UTCTelegram responding with errors: data centres
- 2026-09-03 11:27 UTCTelegram responding with errors: data centres
- 2026-09-03 09:28 UTCTelegram responding with errors: data centres
- 2026-09-03 05:18 UTCTelegram responding with errors: data centres
- 2026-09-02 00:03 UTCTelegram responding with errors: Bot API, web app
- 2026-09-01 19:39 UTCTelegram outage: Bot API
- 2026-09-01 14:09 UTCTelegram outage: Bot API
- 2026-09-01 02:04 UTCTelegram responding with errors: Bot API
- 2026-08-30 13:06 UTCTelegram responding with errors: Bot API
- 2026-08-30 11:57 UTCTelegram responding with errors: Bot API
- 2026-08-30 03:07 UTCTelegram responding with errors: Bot API
- 2026-08-29 13:30 UTCTelegram responding with errors: Bot API
- 2026-08-28 19:19 UTCTelegram outage: Bot API
- 2026-08-28 07:53 UTCTelegram responding with errors: t.me links
- 2026-08-27 11:38 UTCTelegram outage: Bot API
- 2026-08-27 11:07 UTCTelegram responding with errors: t.me links
- 2026-08-27 08:29 UTCTelegram responding with errors: t.me links, web app
- 2026-08-27 04:31 UTCTelegram responding with errors: Bot API, t.me links, web app
- 2026-08-27 04:25 UTCTelegram outage: t.me links
- 2026-08-26 19:21 UTCTelegram responding with errors: Bot API, t.me links, web app
- 2026-08-26 18:54 UTCTelegram outage: Bot API, t.me links
- 2026-08-26 15:40 UTCTelegram responding with errors: Bot API, t.me links, web app
- 2026-08-26 11:02 UTCTelegram outage: Bot API, t.me links, web app
- 2026-08-26 10:56 UTCTelegram outage: t.me links
- 2026-08-25 21:44 UTCTelegram responding with errors: data centres
- 2026-08-25 17:28 UTCTelegram responding with errors: t.me links
- 2026-08-24 20:12 UTCTelegram responding with errors: t.me links
- 2026-08-23 12:13 UTCTelegram responding with errors: media delivery
- 2026-08-23 08:49 UTCTelegram responding with errors: web app
- 2026-08-23 08:43 UTCTelegram outage: Bot API
- 2026-08-23 00:10 UTCTelegram responding with errors: t.me links
- 2026-08-22 19:21 UTCTelegram responding with errors: Bot API
- 2026-08-22 04:32 UTCTelegram responding with errors: t.me links
- 2026-08-22 00:04 UTCTelegram outage: Bot API
- 2026-08-21 22:30 UTCTelegram responding with errors: web app
How we measure this
- We do not count complaints. There is no «it is broken for me» button here: complaints also spike when one popular channel simply goes quiet, and faking them costs next to nothing.
- We measure the network. Every minute we open Telegram ourselves from three sides: our own server, points around the world, and the browsers of people who pressed “Check from your side”.
- We only call it an outage when it is visible from at least two sides. One side is enough for a yellow “maybe”; if the second sees nothing within 15 minutes, the record closes itself.
- We clear an outage slower than we raise it: 5 calm minutes in a row are needed.
- We publish measurements, not causes. «t.me does not open from country X» is what we see. Who caused the failure and why, we do not see and do not write.
There is not a single Telegram resource on this page: no login button, no t.me widgets. That is why it opens even when Telegram does not respond.
Questions
- Why is Telegram not working?
- There are two possibilities. Either it is an outage on Telegram's side — then measurements from different countries drop at the same time, which is visible on the bars above. Or it is your network: the operator, the Wi-Fi or the device itself. The “Check from here” button helps tell them apart: it makes several requests to Telegram from your own network and shows the answer. Telegram may well be responding at our vantage points while the result differs on your network — our measurements know nothing about your connection.
- Is it down for everyone or just for me?
- Look at the «By country» block: availability is measured from vantage points around the world. Failing everywhere means an outage. Failing in one or two countries while the rest are normal means a network-side restriction; we write where the failure is visible from, but not who caused it. One important caveat: our probes sit in data centres, not on mobile operators, so a country row is availability from those networks rather than a verdict on the whole country. To find out how things stand on your own connection, press “Check from your side”: your browser makes three requests to Telegram static files from your network and shows the answer.
- What should I do if Telegram does not open?
- If the bars show an outage — wait: reinstalling the app and changing DNS will not fix it. If the bars are normal, check your connection: a different network, mobile data instead of Wi-Fi, restarting the app. We write «recovered» only after several calm minutes in a row — that is, when it really is.
For developers
Widget for your site
A «Telegram: working» line with an indicator dot. Paste the code on your site.
<a href="https://tg.place/en/signal?utm_source=widget" target="_blank" rel="noopener"><img src="https://tg.place/signal/badge.svg?theme=dark&locale=en" alt="Telegram: working" width="154" height="32" style="height:32px;width:auto" loading="lazy"></a>Measured 2026-10-01 14:56 UTC