Telegram is up.
It answers from all 10 monitoring groups, in a median of 293 ms.
We keep your country, an area of about 25 km and your network's name, never your address.
Is it just you?
Asking Telegram from your connection…
Place by place
Where each check runs, what it saw last and how it did over the day.
| Place | Now | Answer | 24 h |
|---|---|---|---|
| Los AngelesLAX · group: Western North America | answers | 293 ms | 100% |
| MiamiMIA · group: Eastern North America | answers | 337 ms | 99.8% |
| AtlantaATL · group: South America | answers | 332 ms | 100% |
| LondonLHR · group: Western Europe | answers | 118 ms | 100% |
| WarsawWAW · group: Eastern Europe | answers | 199 ms | 99.8% |
| FrankfurtFRA · group: the Middle East | answers | 114 ms | 100% |
| LondonLHR · group: Africa | answers | 82 ms | 100% |
| OsakaKIX · group: Asia-Pacific | answers | 388 ms | 99.8% |
| SydneySYD · group: Oceania | answers | 555 ms | 99.8% |
| Amsterdamour server | answers | 97 ms | 100% |
The last 24 hours
Every quarter hour from each place: the darker the red, the more checks failed.
LAX
MIA
ATL
LHR
WAW
FRA
LHR
KIX
SYD
AMS
14:1520:1502:1508:1514:00
Every minute from Amsterdam
Green when it answered, red when it did not; the line is how long the answer took.
14:1014:05
24 h uptime: 100%Answer: 106 ms
Reports
People who told us it is down for them, per 15 minutes.
14:1514:00
Reports in the last hour: 0
Status page
No status page we can read.
What it depends on
Found in its DNS and addresses. When these fail, it usually fails with them.
- HostingTELEGRAM
- DNSGoogle Cloud DNS
Its outages
No repeated check failures recorded in the last 90 days.