Telegram help and reporting
Use the official support form and FAQ for the affected account or messaging action.
Live Domain Check
Run a live reachability check for telegram.org. Compare the regional responses with the problem you see in Telegram.
Find Telegram help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
Telegram login, sending messages, calls and restrictions on contacting other users are different problems.
The checker above requests telegram.org from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Telegram action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse social app checks.
Use the official support form and FAQ for the affected account or messaging action.
Open the website in your browser and compare it with the result above.
Open Telegram help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
Platform/version, action, error or restriction text and timestamp without phone codes or private messages.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Telegram.
These are troubleshooting comparisons, not claims that Telegram is currently experiencing a particular incident.
Compare an existing conversation with the failed action and record its delivery/error state.
Use Telegram's official FAQ/support; preserve login progress and distinguish a restriction notice from a connection error.
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use these local troubleshooting steps after the down-check workflow when Telegram seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open telegram.org in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Telegram issue.
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Telegram support.
Run the telegram.org check and compare its original timestamps and responses with your actual error. Telegram login, sending messages, calls and restrictions on contacting other users are different problems.
Use the community buttons on this page to share whether the service works for you. For help from Telegram, use the official help/reporting resource linked above. Use the official support form and FAQ for the affected account or messaging action.
Compare an existing conversation with the failed action and record its delivery/error state. Use Telegram's official FAQ/support; preserve login progress and distinguish a restriction notice from a connection error.
Platform/version, action, error or restriction text and timestamp without phone codes or private messages.