Skip to content

Outage tracker / Telegram

Is Telegram down?

I'm having a problem

Operationalchecked 5 minutes ago

We reached Telegram from all 10 regions we check.

As of Oct 5, 2026, 8:11 PM UTC, Telegram answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 58 days we have measured Telegram (since Aug 8, 2026).

Email me the next time we see Telegram go down

Measured by our own probes from ten regions, not Telegram's status page. One email when a measured outage opens and one when it closes, after you confirm the address. No account, no card.

our independent probeslive · checked Oct 5, 2026, 8:11 PM UTC
US-East617 msOperational
US-West812 msOperational
Europe111 msOperational
Asia-Pacific1307 msOperational
US-Central499 msOperational
Canada529 msOperational
UK223 msOperational
Southeast Asia980 msOperational
Australia1129 msOperational
South America1186 msOperational
their status pagetheir claim, not our reading

Telegram publishes no status feed we can read, so the only independent reading here is ours on the left.

Telegram response time, by region

US-East
675msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 659ms2026-09-07 UTC: p95 582ms2026-09-08 UTC: p95 607ms2026-09-09 UTC: p95 560ms2026-09-10 UTC: p95 579ms2026-09-11 UTC: p95 597ms2026-09-12 UTC: p95 593ms2026-09-13 UTC: p95 838ms2026-09-14 UTC: p95 614ms2026-09-15 UTC: p95 724ms2026-09-16 UTC: p95 744ms2026-09-17 UTC: p95 791ms2026-09-18 UTC: p95 756ms2026-09-19 UTC: p95 776ms2026-09-20 UTC: p95 726ms2026-09-21 UTC: p95 698ms2026-09-22 UTC: p95 890ms2026-09-23 UTC: p95 816ms2026-09-24 UTC: p95 793ms2026-09-25 UTC: p95 645ms2026-09-26 UTC: p95 719ms2026-09-27 UTC: p95 635ms2026-09-28 UTC: p95 787ms2026-09-29 UTC: p95 779ms2026-09-30 UTC: p95 606ms2026-10-01 UTC: p95 791ms2026-10-02 UTC: p95 607ms2026-10-03 UTC: p95 598ms2026-10-04 UTC: p95 604ms2026-10-05 UTC: p95 675ms
Sep 6Sep 20Oct 5
US-West
826msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 880ms2026-09-07 UTC: p95 839ms2026-09-08 UTC: p95 791ms2026-09-09 UTC: p95 698ms2026-09-10 UTC: p95 717ms2026-09-11 UTC: p95 681ms2026-09-12 UTC: p95 718ms2026-09-13 UTC: p95 698ms2026-09-14 UTC: p95 637ms2026-09-15 UTC: p95 875ms2026-09-16 UTC: p95 927ms2026-09-17 UTC: p95 904ms2026-09-18 UTC: p95 927ms2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 973ms2026-09-29 UTC: p95 875ms2026-09-30 UTC: p95 788ms2026-10-01 UTC: p95 771ms2026-10-02 UTC: p95 1.0s2026-10-03 UTC: p95 923ms2026-10-04 UTC: p95 839ms2026-10-05 UTC: p95 826ms
Sep 6Sep 20Oct 5
Europe
309msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 492ms2026-09-07 UTC: p95 499ms2026-09-08 UTC: p95 469ms2026-09-09 UTC: p95 505ms2026-09-10 UTC: p95 283ms2026-09-11 UTC: p95 336ms2026-09-12 UTC: p95 307ms2026-09-13 UTC: p95 277ms2026-09-14 UTC: p95 333ms2026-09-15 UTC: p95 415ms2026-09-16 UTC: p95 603ms2026-09-17 UTC: p95 679ms2026-09-18 UTC: p95 637ms2026-09-19 UTC: p95 716ms2026-09-20 UTC: p95 593ms2026-09-21 UTC: p95 756ms2026-09-22 UTC: p95 731ms2026-09-23 UTC: p95 661ms2026-09-24 UTC: p95 922ms2026-09-25 UTC: p95 708ms2026-09-26 UTC: p95 552ms2026-09-27 UTC: p95 451ms2026-09-28 UTC: p95 575ms2026-09-29 UTC: p95 585ms2026-09-30 UTC: p95 292ms2026-10-01 UTC: p95 241ms2026-10-02 UTC: p95 368ms2026-10-03 UTC: p95 453ms2026-10-04 UTC: p95 348ms2026-10-05 UTC: p95 309ms
Sep 6Sep 20Oct 5
Asia-Pacific
1.9sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.4s2026-09-07 UTC: p95 1.5s2026-09-08 UTC: p95 2.2s2026-09-09 UTC: p95 1.5s2026-09-10 UTC: p95 2.2s2026-09-11 UTC: p95 1.6s2026-09-12 UTC: p95 1.5s2026-09-13 UTC: p95 1.5s2026-09-14 UTC: p95 1.6s2026-09-15 UTC: p95 2.1s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 1.3s2026-09-19 UTC: p95 1.5s2026-09-20 UTC: p95 1.5s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 1.7s2026-09-23 UTC: p95 1.5s2026-09-24 UTC: p95 1.6s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.5s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.8s2026-09-29 UTC: p95 1.6s2026-09-30 UTC: p95 2.4s2026-10-01 UTC: p95 2.1s2026-10-02 UTC: p95 1.8s2026-10-03 UTC: p95 1.8s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 1.9s
Sep 6Sep 20Oct 5
US-Central
737msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 563ms2026-09-07 UTC: p95 624ms2026-09-08 UTC: p95 626ms2026-09-09 UTC: p95 687ms2026-09-10 UTC: p95 623ms2026-09-11 UTC: p95 558ms2026-09-12 UTC: p95 644ms2026-09-13 UTC: p95 675ms2026-09-14 UTC: p95 732ms2026-09-15 UTC: p95 636ms2026-09-16 UTC: p95 618ms2026-09-17 UTC: p95 614ms2026-09-18 UTC: p95 595ms2026-09-19 UTC: p95 754ms2026-09-20 UTC: p95 715ms2026-09-21 UTC: p95 690ms2026-09-22 UTC: p95 612ms2026-09-23 UTC: p95 801ms2026-09-24 UTC: p95 909ms2026-09-25 UTC: p95 683ms2026-09-26 UTC: p95 739ms2026-09-27 UTC: p95 636ms2026-09-28 UTC: p95 641ms2026-09-29 UTC: p95 677ms2026-09-30 UTC: p95 797ms2026-10-01 UTC: p95 845ms2026-10-02 UTC: p95 846ms2026-10-03 UTC: p95 864ms2026-10-04 UTC: p95 799ms2026-10-05 UTC: p95 737ms
Sep 6Sep 20Oct 5
Canada
646msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 673ms2026-09-07 UTC: p95 590ms2026-09-08 UTC: p95 571ms2026-09-09 UTC: p95 639ms2026-09-10 UTC: p95 559ms2026-09-11 UTC: p95 739ms2026-09-12 UTC: p95 824ms2026-09-13 UTC: p95 688ms2026-09-14 UTC: p95 793ms2026-09-15 UTC: p95 702ms2026-09-16 UTC: p95 678ms2026-09-17 UTC: p95 707ms2026-09-18 UTC: p95 712ms2026-09-19 UTC: p95 808ms2026-09-20 UTC: p95 764ms2026-09-21 UTC: p95 751ms2026-09-22 UTC: p95 759ms2026-09-23 UTC: p95 841ms2026-09-24 UTC: p95 615ms2026-09-25 UTC: p95 584ms2026-09-26 UTC: p95 731ms2026-09-27 UTC: p95 829ms2026-09-28 UTC: p95 835ms2026-09-29 UTC: p95 794ms2026-09-30 UTC: p95 801ms2026-10-01 UTC: p95 819ms2026-10-02 UTC: p95 734ms2026-10-03 UTC: p95 880ms2026-10-04 UTC: p95 764ms2026-10-05 UTC: p95 646ms
Sep 6Sep 20Oct 5
UK
286msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 147ms2026-09-07 UTC: p95 193ms2026-09-08 UTC: p95 180ms2026-09-09 UTC: p95 165ms2026-09-10 UTC: p95 183ms2026-09-11 UTC: p95 188ms2026-09-12 UTC: p95 76ms2026-09-13 UTC: p95 170ms2026-09-14 UTC: p95 175ms2026-09-15 UTC: p95 203ms2026-09-16 UTC: p95 217ms2026-09-17 UTC: p95 238ms2026-09-18 UTC: p95 202ms2026-09-19 UTC: p95 299ms2026-09-20 UTC: p95 243ms2026-09-21 UTC: p95 291ms2026-09-22 UTC: p95 355ms2026-09-23 UTC: p95 329ms2026-09-24 UTC: p95 369ms2026-09-25 UTC: p95 377ms2026-09-26 UTC: p95 534ms2026-09-27 UTC: p95 259ms2026-09-28 UTC: p95 252ms2026-09-29 UTC: p95 295ms2026-09-30 UTC: p95 383ms2026-10-01 UTC: p95 462ms2026-10-02 UTC: p95 425ms2026-10-03 UTC: p95 414ms2026-10-04 UTC: p95 226ms2026-10-05 UTC: p95 286ms
Sep 6Sep 20Oct 5
Southeast Asia
1.3sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 901ms2026-09-07 UTC: p95 927ms2026-09-08 UTC: p95 939ms2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 1.0s2026-09-11 UTC: p95 1.0s2026-09-12 UTC: p95 1.1s2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 987ms2026-09-16 UTC: p95 967ms2026-09-17 UTC: p95 1.0s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.0s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.4s2026-09-22 UTC: p95 1.4s2026-09-23 UTC: p95 1.5s2026-09-24 UTC: p95 1.5s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.5s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 975ms2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.3s
Sep 6Sep 20Oct 5
Australia
2.0sp95 · latest
10s5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 5.3s2026-09-07 UTC: p95 1.7s2026-09-08 UTC: p95 1.5s2026-09-09 UTC: p95 1.6s2026-09-10 UTC: p95 1.7s2026-09-11 UTC: p95 2.0s2026-09-12 UTC: p95 1.6s2026-09-13 UTC: p95 1.4s2026-09-14 UTC: p95 1.5s2026-09-15 UTC: p95 1.5s2026-09-16 UTC: p95 2.3s2026-09-17 UTC: p95 2.5s2026-09-18 UTC: p95 2.5s2026-09-19 UTC: p95 3.3s2026-09-20 UTC: p95 2.3s2026-09-21 UTC: p95 1.8s2026-09-22 UTC: p95 1.9s2026-09-23 UTC: p95 1.7s2026-09-24 UTC: p95 1.6s2026-09-25 UTC: p95 1.9s2026-09-26 UTC: p95 1.9s2026-09-27 UTC: p95 1.8s2026-09-28 UTC: p95 1.9s2026-09-29 UTC: p95 2.2s2026-09-30 UTC: p95 2.4s2026-10-01 UTC: p95 2.1s2026-10-02 UTC: p95 2.8s2026-10-03 UTC: p95 2.2s2026-10-04 UTC: p95 2.1s2026-10-05 UTC: p95 2.0s
Sep 6Sep 20Oct 5
South America
1.7sp95 · latest
2.5s1.3s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.5s2026-09-07 UTC: p95 1.6s2026-09-08 UTC: p95 1.7s2026-09-09 UTC: p95 1.6s2026-09-10 UTC: p95 1.5s2026-09-11 UTC: p95 1.5s2026-09-12 UTC: p95 1.5s2026-09-13 UTC: p95 1.5s2026-09-14 UTC: p95 1.3s2026-09-15 UTC: p95 1.6s2026-09-16 UTC: p95 1.7s2026-09-17 UTC: p95 2.0s2026-09-18 UTC: p95 1.6s2026-09-19 UTC: p95 1.7s2026-09-20 UTC: p95 1.6s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 1.5s2026-09-23 UTC: p95 1.4s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.6s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.6s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.5s2026-10-01 UTC: p95 1.9s2026-10-02 UTC: p95 1.8s2026-10-03 UTC: p95 2.1s2026-10-04 UTC: p95 1.7s2026-10-05 UTC: p95 1.7s
Sep 6Sep 20Oct 5
Why some readings show as awaiting data. 1 of 20 readings for Telegram came back as a filtered response to our automated checks (a response code that refuses automated clients, such as 403, 405, 406, 429 or 451, a redirect loop, or a timeout we could rule out as a real outage using a second endpoint) rather than a normal success or failure. That tells us about our own probe's reception, not about Telegram's actual health, so we publish no verdict for those readings rather than guessing in either direction. Read how we tell the difference.

Is it Telegram, or is it you?

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: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • AuthUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 617msstatus code: 200checked: Oct 5, 2026, 8:11 PM UTC
      0 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-West
      Operationallatency: 812msstatus code: 200checked: Oct 5, 2026, 8:09 PM UTC
      0 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-Central
      Operationallatency: 499msstatus code: 200checked: Oct 5, 2026, 8:07 PM UTC
      0 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.
    • Canada
      Operationallatency: 529msstatus code: 200checked: Oct 5, 2026, 8:00 PM UTC
      0 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 America
    Operationallatency: 1186msstatus code: 200checked: Oct 5, 2026, 8:07 PM UTC
    0 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.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 111msstatus code: 200checked: Oct 5, 2026, 8:10 PM UTC
      0 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.
    • UK
      Operationallatency: 223msstatus code: 200checked: Oct 5, 2026, 8:10 PM UTC
      0 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 Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 1307msstatus code: 200checked: Oct 5, 2026, 8:11 PM UTC
      0 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 Asia
      Operationallatency: 980msstatus code: 200checked: Oct 5, 2026, 7:58 PM UTC
      0 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.
    • Australia
      Operationallatency: 1129msstatus code: 200checked: Oct 5, 2026, 8:04 PM UTC
      0 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 outages

No outages on record yet for Telegram.

measured 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 measurements and Telegram's own claim at the time, side by side.

Full availability history for Telegram: 90-day availability by region, month-by-month uptime, and every incident on record.

Put this badge in your README

Telegram uptime measured by RealUptimeLive, from this page's own readings.
[![Telegram uptime measured by RealUptime](https://realuptime.io/outages/telegram/badge.svg?days=30)](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 measured by RealUptime"></a>

The badge shows the share of our probes that succeeded 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: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Telegram's SLA implies, from our measurement

At or above your target

We measured none of downtime for Telegram over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, 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

primary
https://web.telegram.org/
secondaryfunctional: auth surface
https://api.telegram.org/bot0:0/getMe
RealUptime is not affiliated with Telegram; the name identifies what we measured, and nothing here speaks for Telegram's own team. We send a single web request to Telegram from 10 regions on our own schedule and time the response. We do not see inside Telegram's systems, do not use an account or real transaction, and are not the same signal Telegram's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Telegram is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.