Is Telegram not working for you? Use this page to separate a possible Telegram-wide outage from a problem with your app, account, device, browser, or connection. Test the feature that is failing—messages, calls, login, media, or access—then follow the troubleshooting path that matches the scope of t
Site Administrator
Last reviewed: September 25, 2026
LATEST RECORDED STATUS
Up Telegram’s website appeared to be up and responding normally at the last check.
| Endpoint | Status | Observed |
|---|---|---|
| telegram.org | Operational | 2026-11-10 13:54 UTC |
Is it working for you?
0 recent reports — more reports are needed for a useful trend.

Telegram can appear to open normally while messages remain pending, media fails to load, calls do not connect, or sign-in does not complete. The pattern matters:
This page is a diagnostic guide rather than a live official Telegram incident feed. No dedicated official Telegram status URL is recorded here, so use Telegram’s official website, in-app notices, and official communications alongside tests from more than one device or network. Third-party outage reports are useful signals, but isolated reports do not confirm a platform-wide outage.
Check whether Telegram opens, existing chats load, new messages send, media downloads or uploads, and calls connect. Note whether the problem affects every chat, one conversation, one feature, one device, or one network. If available and permitted, test the same account on another device and connection.
A broader availability issue is more likely when Telegram fails across different devices and both Wi-Fi and mobile data, particularly when several features stop working at the same time. Avoid repeated reinstalls or account changes while the same failure is reproduced independently. Check Telegram’s official communications and in-app notices, then wait for further service information.
If Telegram works elsewhere, force-close and reopen the app, restart the device, and install any available app update. Check available storage and confirm that the device date and time are correct. If only cached media or one screen is affected, clearing temporary app data may help. Do not remove local data unless you understand what will be deleted and can sign in again.
For sign-in failures, verify the country code and phone number. Confirm access to the SIM or device that can receive the code, and check other active Telegram sessions if you can access them. A login code may be delivered to another active Telegram session instead of by text message. Avoid repeated code requests and never share a login code with another person.
If Telegram works on mobile data but not on one Wi-Fi network, the router, DNS configuration, firewall, VPN, proxy, content filter, or managed network is more likely than a Telegram-wide outage. Restart the router only if you are authorized to manage that network, then compare Telegram with another trusted connection where permitted. If other websites also fail to resolve or connect, investigate the underlying DNS or connection problem rather than treating it as Telegram-specific.
If the problem occurs only in a browser-based Telegram client, try a private window, temporarily disable extensions, clear site data for that client, or test another supported browser. If the mobile app works while the browser does not, the browser session or network path is more likely to be responsible than the account itself.
If messages work but calls fail, compare Wi-Fi with mobile data and check whether the issue affects incoming, outgoing, or all calls. If text messages work but media does not load or upload, check the affected device’s storage, app permissions, connection quality, and whether the problem occurs in multiple chats. A single feature failure is not, by itself, evidence that Telegram is completely down.
No separate Telegram API domain is recorded for this service. For an integration problem, review the integration’s logs, credentials, request errors, and network responses, then compare them with ordinary Telegram app access. An application-specific error does not establish that Telegram as a whole is unavailable.
For official service information, consult Telegram’s official website at the recorded telegram.org domain, along with Telegram’s official communications and in-app notices. Compare those updates with tests from more than one device and network. Third-party outage reports can help identify a possible incident, but isolated reports should not be treated as confirmation of a platform-wide Telegram outage.
Every time this page loads, our server makes its own request to telegram.org (and its API domain, when applicable) and reports what it got back — a real HTTP response, a timeout, or a connection failure. That result is cached for up to 2 minutes.
This confirms external reachability; it does not test every feature, region, account, or network path. Cross-check the official status page when one is available.
No. This is a live, one-off connectivity check run from our own server, not Telegram's own incident reporting. Their official status page can show partial, regional, or component-level issues our single external check cannot detect.
A basic reachability check confirms that the server responded to our request. It does not test every feature, region, ISP, browser, or account-specific issue.
A check is refreshed after the two-minute cache expires. The displayed check time shows when the observation was made.
Not necessarily. Many services split their website and API onto separate infrastructure, so one can fail while the other keeps working.
This page does not provide a live official Telegram status feed. Compare Telegram on different devices and connections, including mobile data where available. Failure across several independent tests is more consistent with a wider availability problem than failure on one device or Wi-Fi network.
Telegram may have opened successfully while its current connection is unstable or unable to reach the messaging service. Test another network, check whether every chat is affected, and restart the app. If only one conversation is affected, the problem may be specific to that chat or recipient.
Confirm the phone number and country code, check whether the code was delivered to another active Telegram session, and verify access to the relevant SIM or device. Avoid repeated requests, and never give a login code to anyone else.
The Wi-Fi network, router, DNS settings, firewall, proxy, VPN, or content filter may be disrupting Telegram. Restart the router only when authorized to manage it, then compare with another trusted network before changing account settings.
Yes. An extension, stale site data, or damaged browser session can affect a web client even when the mobile app works. Try a private window, temporarily disable extensions, clear the relevant site data, or test another browser.
Treat the working device as evidence that the account and service may be reachable. Update or restart the affected device, check its network and time settings, and review its app data or active session before reinstalling anything.
This is a live connectivity check from our server, not an official statement from Telegram. A down result may also reflect a regional or partial outage.