Social and communication
Telegram vs WhatsApp: our checks, side by side
Whether our checks pass or fail now, and 12 months of uptime by our checks, for both. This is a factual side by side, not a recommendation: it never ranks or scores either service, and states no opinion on which to choose.
Current state
Our checks of Telegram pass from all 10 regions we check.
Our checks of Telegram did not fail from two or more distant regions in the 91 days we have checked it (since Aug 8, 2026). This does not show Telegram works for users.
Our checks of WhatsApp pass from all 10 regions we check.
Our checks of WhatsApp did not fail from two or more distant regions in the 91 days we have checked it (since Aug 8, 2026). This does not show WhatsApp works for users.
Composed by the same rule each service's own page uses, with the same omission that page's dependency-stack view carries: user reports, public chatter and each vendor's own status-page claim are not read here, only our own check readings.
12-month record
Telegram
Tracking Telegram since Aug 8, 2026. In that time our checks failed from two or more distant regions in no probe event. Months before that date are not tracked and carry no figure.
| Month | Uptime by our checks | Probe events | Time failing |
|---|---|---|---|
| Dec 2025 | not tracked | ||
| Jan 2026 | not tracked | ||
| Feb 2026 | not tracked | ||
| Mar 2026 | not tracked | ||
| Apr 2026 | not tracked | ||
| May 2026 | not tracked | ||
| Jun 2026 | not tracked | ||
| Jul 2026 | not tracked | ||
| Aug 2026 from Aug 8, 2026 | 100% | 0 | 0 min |
| Sep 2026 | 100% | 0 | 0 min |
| Oct 2026 | 100% | 0 | 0 min |
| Nov 2026 | 100% | 0 | 0 min |
Uptime by our checks is the share of each month in which no probe event was open for Telegram. An event opens only when our checks fail from two or more distant regions, meaning regions on different continents. One that nothing else backs stops counting as an outage after 6 hours, and after 48 hours we treat our check as broken. An event that fails these rules is retracted, kept, and listed on the corrections page. An event that crosses midnight on the first of a month is counted in both months with its minutes split. User reports, public posts and Telegram's own status page contribute nothing to these figures.
Tracking WhatsApp since Aug 8, 2026. In that time our checks failed from two or more distant regions in no probe event. Months before that date are not tracked and carry no figure.
| Month | Uptime by our checks | Probe events | Time failing |
|---|---|---|---|
| Dec 2025 | not tracked | ||
| Jan 2026 | not tracked | ||
| Feb 2026 | not tracked | ||
| Mar 2026 | not tracked | ||
| Apr 2026 | not tracked | ||
| May 2026 | not tracked | ||
| Jun 2026 | not tracked | ||
| Jul 2026 | not tracked | ||
| Aug 2026 from Aug 8, 2026 | 100% | 0 | 0 min |
| Sep 2026 | 100% | 0 | 0 min |
| Oct 2026 | 100% | 0 | 0 min |
| Nov 2026 | 100% | 0 | 0 min |
Uptime by our checks is the share of each month in which no probe event was open for WhatsApp. An event opens only when our checks fail from two or more distant regions, meaning regions on different continents. One that nothing else backs stops counting as an outage after 6 hours, and after 48 hours we treat our check as broken. An event that fails these rules is retracted, kept, and listed on the corrections page. An event that crosses midnight on the first of a month is counted in both months with its minutes split. User reports, public posts and WhatsApp's own status page contribute nothing to these figures.
Every figure above is read from the same measurement each service's own page and 12-month history publish, never a separate calculation for this page. These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. See Telegram's full record or WhatsApp's full record, or read how this check works.