LIVE SERVICE STATUS · PAKISTANLive checks, official provider updates, and incident history for Telegram.
See the latest checks and provider updates, with separate results for Pakistan and other countries.
A recent public access check succeeded. The Pakistan result uses that check; access on Pakistani networks has not been independently tested.
Updates every 5 minutesChecks cover the measured service access; individual app features or accounts can behave differently.
The latest website check reached the service at 03-Oct-2026, 4:50 am PKT. This is one signal from the monitoring location.
A working result can use one successful public access check at the monitoring location. This does not verify every Pakistani or international network. Percentages, when shown, refer only to networks actually measured.
A responsive public website does not guarantee that every part of Telegram is working. Login, notifications, payments, media, APIs, or regional routes can fail independently. We describe the evidence we have rather than turning a single successful check into a broad claim. When the latest stored status grows stale, the page shows that the status is not verified until new measurements arrive.
A status label is only a starting point. The exact symptom and the networks involved help explain what may be happening.
Social and messaging platforms rely on several separate systems for login, feeds, media, notifications, and real-time communication. A partial problem may affect one feature while the rest of the app appears normal.
Note the exact action that fails: opening the app, refreshing content, sending a message, posting, or loading media. Compare the website and mobile app if both are available. This detail is more useful than a general report that the service is down.
Check connectivity, update the app, and try another network or browser. If one account behaves differently from another, review official account guidance before treating it as a platform-wide issue.
If the service fails on only one device, browser, or account, the cause may be local. If it fails across different connections and other people report the same symptom at the same time, a wider problem becomes more plausible. Keep troubleshooting steps reversible, particularly when a payment, booking, upload, or form submission could already be in progress.
Public endpoint checks describe only reachability. Official updates and geographically separate measurements help show whether a problem affects more than one device or network in Pakistan.
Our worker tests safe public endpoints for DNS resolution, TCP connectivity, TLS negotiation, HTTPS response, and latency. RIPE Atlas can add Pakistani and international probe observations when configured; OONI may provide access context. Official status feeds are considered where the provider publishes one. These signals are weighted conservatively, and an unavailable provider contributes no positive evidence.
An individual account restriction, missing content item, or delayed notification is not proof of a country-wide outage.
For Telegram, separate a failure to sign in from trouble sending, receiving, loading media, or refreshing a feed. Ask someone on a different connection to test the same feature at roughly the same time without sharing private content. If one account is affected, use the platform's own recovery or support process. A public check can keep succeeding while authenticated messaging is impaired. Record the exact symptom and start time when contacting the provider.
Independent checks and official updates help confirm wider disruptions. For a problem with your own account, use the service’s official support channel.
Historical charts use stored checks. They start empty and grow as monitoring runs; no incidents or availability figures are fabricated.
Switch between 24-hour, 7-day, 30-day, and 90-day views.
Average public endpoint availability in this view: 99.2%. This measures configured endpoints, not every feature of the service.
No confirmed incidents have been recorded for Telegram yet.
A public endpoint availability percentage measures only configured endpoints. It does not promise that every feature, region, account, or app function was available for the same percentage of time. Older raw checks are rolled into hourly aggregates and removed under the retention policy, while incident records remain available for context.
