What does reachable from NexIP mean?
The monitored web endpoint returned a successful HTTP response from the NexIP location. This does not guarantee that messaging, calls, login or other features work for every user or region.
← All services
Messengers
Is Telegram down? Current status and outages
Доступен из точки NexIPHTTP-проверка из точки NexIP успешна. Доступность из всех регионов не подтверждена.
Understanding the metrics
Reports over 24 hours, signals over 15 minutes and the outage index measure different periods and conditions. Their values may differ without being contradictory.
Service monitoring
Current state
Outage score
0/100
Statistical assessment
User signals
0
unique in the last 15 minutes
Automatic check
Available
Response: 276 ms
Response time
276 ms
Last local automatic check
User reports over the last 24 hours
Reports submitted to NexIP. One report does not prove a widespread outage.
Reports in selected period
0
No reports during this period.
30-minute intervals · Moscow time · actual dataLast 7 days
Recent incidents
No confirmed large-scale incidents were recorded during the last 7 days.
Observation points
Regional checks
Remote observation points are not connected yet.
Observation history
Latest automatic checks
OUTAGE INTELLIGENCE / SERVICE PROBES
Check history and reliability
Actual NexIP primary probe measurements, not user reports
Full-period overviewAll observations
Latest 40 intervals · CSV includes entire selection
| Time (server) | Checks | Average | Peak | Down | Blocked |
|---|---|---|---|---|---|
| 2026-11-13 14:30:00 | 4 | 564 ms | 1 339 ms | 0 | 0 |
| 2026-11-13 15:00:00 | 3 | 290 ms | 317 ms | 0 | 0 |
| 2026-11-13 15:30:00 | 4 | 305 ms | 319 ms | 0 | 0 |
| 2026-11-13 16:00:00 | 4 | 287 ms | 317 ms | 0 | 0 |
| 2026-11-13 16:30:00 | 4 | 297 ms | 317 ms | 0 | 0 |
| 2026-11-13 17:00:00 | 3 | 292 ms | 316 ms | 0 | 0 |
| 2026-11-13 17:30:00 | 4 | 300 ms | 309 ms | 0 | 0 |
| 2026-11-13 18:00:00 | 4 | 303 ms | 316 ms | 0 | 0 |
| 2026-11-13 18:30:00 | 4 | 288 ms | 322 ms | 0 | 0 |
| 2026-11-13 19:00:00 | 3 | 285 ms | 302 ms | 0 | 0 |
| 2026-11-13 19:30:00 | 4 | 293 ms | 308 ms | 0 | 0 |
| 2026-11-13 20:00:00 | 4 | 297 ms | 318 ms | 0 | 0 |
| 2026-11-13 20:30:00 | 4 | 300 ms | 317 ms | 0 | 0 |
| 2026-11-13 21:00:00 | 3 | 302 ms | 319 ms | 0 | 0 |
| 2026-11-13 21:30:00 | 4 | 312 ms | 317 ms | 0 | 0 |
| 2026-11-13 22:00:00 | 4 | 305 ms | 317 ms | 0 | 0 |
| 2026-11-13 22:30:00 | 4 | 336 ms | 401 ms | 0 | 0 |
| 2026-11-13 23:00:00 | 3 | 299 ms | 311 ms | 0 | 0 |
| 2026-11-13 23:30:00 | 4 | 284 ms | 306 ms | 0 | 0 |
| 2026-11-14 00:00:00 | 4 | 287 ms | 317 ms | 0 | 0 |
| 2026-11-14 00:30:00 | 4 | 303 ms | 317 ms | 0 | 0 |
| 2026-11-14 01:00:00 | 3 | 301 ms | 315 ms | 0 | 0 |
| 2026-11-14 01:30:00 | 4 | 294 ms | 316 ms | 0 | 0 |
| 2026-11-14 02:00:00 | 4 | 298 ms | 317 ms | 0 | 0 |
| 2026-11-14 02:30:00 | 4 | 285 ms | 307 ms | 0 | 0 |
| 2026-11-14 03:00:00 | 3 | 286 ms | 303 ms | 0 | 0 |
| 2026-11-14 03:30:00 | 4 | 308 ms | 322 ms | 0 | 0 |
| 2026-11-14 04:00:00 | 4 | 304 ms | 317 ms | 0 | 0 |
| 2026-11-14 04:30:00 | 4 | 305 ms | 347 ms | 0 | 0 |
| 2026-11-14 05:00:00 | 3 | 300 ms | 315 ms | 0 | 0 |
| 2026-11-14 05:30:00 | 4 | 301 ms | 315 ms | 0 | 0 |
| 2026-11-14 06:00:00 | 4 | 295 ms | 315 ms | 0 | 0 |
| 2026-11-14 06:30:00 | 4 | 293 ms | 317 ms | 0 | 0 |
| 2026-11-14 07:00:00 | 3 | 303 ms | 316 ms | 0 | 0 |
| 2026-11-14 07:30:00 | 4 | 307 ms | 317 ms | 0 | 0 |
| 2026-11-14 08:00:00 | 4 | 296 ms | 316 ms | 0 | 0 |
| 2026-11-14 08:30:00 | 4 | 305 ms | 318 ms | 0 | 0 |
| 2026-11-14 09:00:00 | 3 | 277 ms | 281 ms | 0 | 0 |
| 2026-11-14 09:30:00 | 4 | 301 ms | 317 ms | 0 | 0 |
| 2026-11-14 10:00:00 | 1 | 276 ms | 276 ms | 0 | 0 |
Success is up or degraded among recorded primary probe checks. This is not a public uptime SLA. Available history can be shorter than the selected range.
06:59
07:07
07:15
07:23
07:31
07:39
07:47
07:55
08:03
08:11
08:19
08:27
08:35
08:43
08:51
08:59
09:07
09:15
09:23
09:31
09:39
09:47
09:55
10:03
Last check
2026-11-14 10:03:04
HTTP
200
Response time
276 ms
Your signal
Having a problem with this service?
Tell us. Registration is not required. The same signal will not be counted repeatedly within a short period.
Community reviews
User opinions are separate from the technical outage status.
Your rating
5.0 / 5 — 3 ratings
Leave a comment
Published comments
В Московской области с утра ничего не работает
Работает очень плохо в Екатеринбурге
Is Telegram down?
This page tracks the current observed status of Telegram, recent incidents, automated availability checks and available user reports. NexIP does not treat a single failed check as proof of a global outage.
Additional diagnostics
Ping · Website availability · Website monitoring · All service outages
Frequently asked questions
Is Telegram down right now?
NexIP shows the current observed status of Telegram using automated checks, incident data and available user signals. A local connection problem may differ from a large-scale outage.
Why can the service work for some users but not others?
Availability can differ by provider, region, DNS, routing, application version or service component. NexIP therefore separates observed signals from confirmed large-scale incidents.
How can I check whether the problem is on my side?
Check the host with Ping, website availability and your own connection. Comparing several independent checks helps distinguish a local problem from a wider outage.