Is Telegram down?
Checks passingchecked moments ago
Our checks of Telegram pass from all 10 regions we check.
As of Oct 11, 2026, 9:31 PM UTC, RealUptime's checks of Telegram passed in all 10 regions that returned a reading.
Our checks of Telegram did not fail from two or more distant regions in the 64 days we have checked it (since Aug 8, 2026). This does not show Telegram works for users.
Email me when our checks of Telegram fail from two or more distant regions
Telegram publishes no status feed we can read, so the only reading here is our check reading on the left.
Telegram response time, by region
Check your own site while you wait on Telegram
Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Telegram -- it cannot diagnose Telegram's own systems.
What we measured, function by function
Telegram answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the web row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.
- WebprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- AuthUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
What our checks show, and what people reported
- North AmericaChecks passingUS-East, US-West, US-Central, Canada
- US-EastChecks passinglatency: 748msstatus code: 200checked: Oct 11, 2026, 9:31 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Telegram normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestChecks passinglatency: 832msstatus code: 200checked: Oct 11, 2026, 9:29 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Telegram normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-CentralChecks passinglatency: 535msstatus code: 200checked: Oct 11, 2026, 9:14 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Telegram normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
- CanadaChecks passinglatency: 554msstatus code: 200checked: Oct 11, 2026, 9:27 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Telegram normally. We do not have enough reports from Canada to say anything about what people there are seeing.
- South AmericaChecks passinglatency: 1372msstatus code: 200checked: Oct 11, 2026, 9:21 PM UTC0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Telegram normally. We do not have enough reports from South America to say anything about what people there are seeing.
- EuropeChecks passingEurope, UK
- EuropeChecks passinglatency: 245msstatus code: 200checked: Oct 11, 2026, 9:22 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Telegram normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- UKChecks passinglatency: 107msstatus code: 200checked: Oct 11, 2026, 9:28 PM UTC0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Telegram normally. We do not have enough reports from UK to say anything about what people there are seeing.
- Asia PacificChecks passingAsia-Pacific, Southeast Asia, Australia
- Asia-PacificChecks passinglatency: 1413msstatus code: 200checked: Oct 11, 2026, 9:22 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Telegram normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast AsiaChecks passinglatency: 1270msstatus code: 200checked: Oct 11, 2026, 9:27 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Telegram normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
- AustraliaChecks passinglatency: 1758msstatus code: 200checked: Oct 11, 2026, 9:29 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Telegram normally. We do not have enough reports from Australia to say anything about what people there are seeing.
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using Telegram, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We started counting reports for Telegram on September 8, 2026.
Recent probe events
No probe events on record yet for Telegram.
check entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring Telegram since August 8, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.
Need this in writing? Generate an SLA evidence report for Telegram covering any window you pick, with our check readings and Telegram's own claim at the time, side by side.
Full check history for Telegram: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.
Put this badge in your README
Live, from this page's own readings.[](https://realuptime.io/outages/telegram)<a href="https://realuptime.io/outages/telegram"><img src="https://realuptime.io/outages/telegram/badge.svg?days=30" alt="Telegram uptime by RealUptime's checks"></a>The badge shows the share of our checks that passed over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.
How our checks compare with Telegram's stated SLA
At or above your target
Our checks of Telegram failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.
Our checks show no gap in this period. That does not rule out one you saw.
These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, not from Telegram's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.
What we check
What our check can and cannot see
A pass means the service's public web page loaded and answered normally. It does not show that the product, the API or sign-in behind it works; a page can load from a cache while the product is down.
Host checked: web.telegram.org