Messaging status
WhatsApp, Discord, Telegram and the apps people talk to each other on. All 4 are checked every 20 minutes; the status beside each one is the result of its most recent check.
Messaging outages are unusual because delivery is asynchronous: Your message often sends and simply arrives late, so the service can be broken for twenty minutes without a single message being lost.
How reliable messaging has been, last 30 days
Measured by our own checks, run every 20 minutes, not taken from any provider’s status page. 4 of 4 services have enough history to report.
| Service | Now | Uptime 30d | Downtime | Response |
|---|---|---|---|---|
| Discord | Up | 100.0% | none | 174 ms |
| Snapchat | Up | 100.0% | none | 208 ms |
| Telegram | Up | 100.0% | none | 385 ms |
| Up | 100.0% | none | 1110 ms |
Discord has been the steadiest here over the last 30 days. Uptime is observed uptime: The share of measured time our checks got a usable answer. It excludes nothing, including announced maintenance.
Why messaging services go down
A chat app is a queue with a user interface. When the delivery layer slows down, messages are still accepted and still stored, they just stop moving. This is why a messaging outage feels different from a website outage: Nothing errors, the tick marks simply never turn. Most of what people report as a messaging outage is a backlog draining rather than anything being lost.
The failures that genuinely lose function are connection-level. Push notification infrastructure is shared across the whole industry, so when it degrades, messages arrive only when you open the app. People read that as the app being broken, when in fact the notification path failed and the messaging path is fine.
What an outage here looks like
Messages sit with a single tick or a spinning clock. Group chats update out of order as the backlog clears. Voice and video calls fail before text does, because they need a live connection rather than a queue.
When these services are under most strain
Late evening locally, and enormously on New Year, major holidays and during large live events. Messaging is the only category here with a reliable annual peak that operators plan for months ahead.
At a glance
- Typical duration
- 20 to 90 minutes, including backlog drain
- Usual cause
- Delivery queue congestion or push infrastructure
- Tell-tale sign
- Sent but never delivered, then a burst all at once
- Data loss
- Very rare; messages queue rather than fail
What to do when messaging is down
- Do not resend. The first message is almost certainly queued. Resending doubles the backlog you are waiting on and is why people receive the same message six times when service returns.
- Check whether calls work. Calls failing while text still sends points at the real-time layer rather than the whole service.
- Turn off Wi-Fi and use mobile data once. Messaging apps are unusually sensitive to networks that block their ports, and this one test separates a platform outage from a local one.
Still not sure whether it is them or you? Check the site from our servers - We are on a different network, a different resolver and a different route from you.