How to interpret the monitoring status
Technical measurements reflect observations from the NexIP monitoring location. A failed or restricted request alone does not confirm a widespread outage.
Social networks
Техническая проверка выявила ошибку или задержку. Массовый сбой не подтверждён.
Technical measurements reflect observations from the NexIP monitoring location. A failed or restricted request alone does not confirm a widespread outage.
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
Мониторинг доступности сервиса Threads, пользовательских сигналов и технических проверок NexIP.
Reports submitted to NexIP. One report does not prove a widespread outage.
No reports during this period.
30-minute intervals · Moscow time · actual dataLast 7 days
Observation points
Observation history
Actual NexIP primary probe measurements, not user reports
| Time (server) | Checks | Average | Peak | Down | Blocked |
|---|---|---|---|---|---|
| 2026-11-17 17:35:00 | 1 | 5 220 ms | 5 220 ms | 0 | 0 |
| 2026-11-17 17:45:00 | 1 | 5 219 ms | 5 219 ms | 0 | 0 |
| 2026-11-17 17:50:00 | 1 | 5 249 ms | 5 249 ms | 0 | 0 |
| 2026-11-17 18:00:00 | 1 | 5 231 ms | 5 231 ms | 0 | 0 |
| 2026-11-17 18:10:00 | 1 | 5 222 ms | 5 222 ms | 0 | 0 |
| 2026-11-17 18:15:00 | 1 | 5 005 ms | 5 005 ms | 0 | 0 |
| 2026-11-17 18:25:00 | 1 | 5 322 ms | 5 322 ms | 0 | 0 |
| 2026-11-17 18:35:00 | 1 | 5 205 ms | 5 205 ms | 0 | 0 |
| 2026-11-17 18:40:00 | 1 | 5 803 ms | 5 803 ms | 0 | 0 |
| 2026-11-17 18:50:00 | 1 | 5 187 ms | 5 187 ms | 0 | 0 |
| 2026-11-17 18:55:00 | 1 | 5 217 ms | 5 217 ms | 0 | 0 |
| 2026-11-17 19:05:00 | 1 | 5 221 ms | 5 221 ms | 0 | 0 |
| 2026-11-17 19:15:00 | 1 | 5 308 ms | 5 308 ms | 0 | 0 |
| 2026-11-17 19:20:00 | 1 | 6 881 ms | 6 881 ms | 0 | 0 |
| 2026-11-17 19:30:00 | 1 | 5 232 ms | 5 232 ms | 0 | 0 |
| 2026-11-17 19:40:00 | 1 | 5 191 ms | 5 191 ms | 0 | 0 |
| 2026-11-17 19:45:00 | 1 | 5 222 ms | 5 222 ms | 0 | 0 |
| 2026-11-17 19:55:00 | 1 | 5 215 ms | 5 215 ms | 0 | 0 |
| 2026-11-17 20:05:00 | 1 | 5 332 ms | 5 332 ms | 0 | 0 |
| 2026-11-17 20:10:00 | 1 | 5 528 ms | 5 528 ms | 0 | 0 |
| 2026-11-17 20:20:00 | 1 | 5 359 ms | 5 359 ms | 0 | 0 |
| 2026-11-17 20:25:00 | 1 | 5 290 ms | 5 290 ms | 0 | 0 |
| 2026-11-17 20:35:00 | 1 | 5 220 ms | 5 220 ms | 0 | 0 |
| 2026-11-17 20:45:00 | 1 | 5 235 ms | 5 235 ms | 0 | 0 |
| 2026-11-17 20:50:00 | 1 | 5 307 ms | 5 307 ms | 0 | 0 |
| 2026-11-17 21:00:00 | 1 | 5 455 ms | 5 455 ms | 0 | 0 |
| 2026-11-17 21:10:00 | 1 | 5 297 ms | 5 297 ms | 0 | 0 |
| 2026-11-17 21:15:00 | 1 | 5 709 ms | 5 709 ms | 0 | 0 |
| 2026-11-17 21:25:00 | 1 | 5 223 ms | 5 223 ms | 0 | 0 |
| 2026-11-17 21:30:00 | 1 | 5 256 ms | 5 256 ms | 0 | 0 |
| 2026-11-17 21:40:00 | 1 | 5 211 ms | 5 211 ms | 0 | 0 |
| 2026-11-17 21:50:00 | 1 | 5 298 ms | 5 298 ms | 0 | 0 |
| 2026-11-17 21:55:00 | 1 | 5 328 ms | 5 328 ms | 0 | 0 |
| 2026-11-17 22:05:00 | 1 | 5 213 ms | 5 213 ms | 0 | 0 |
| 2026-11-17 22:10:00 | 1 | 5 700 ms | 5 700 ms | 0 | 0 |
| 2026-11-17 22:20:00 | 1 | 5 236 ms | 5 236 ms | 0 | 0 |
| 2026-11-17 22:30:00 | 1 | 5 215 ms | 5 215 ms | 0 | 0 |
| 2026-11-17 22:35:00 | 1 | 5 210 ms | 5 210 ms | 0 | 0 |
| 2026-11-17 22:45:00 | 1 | 5 210 ms | 5 210 ms | 0 | 0 |
| 2026-11-17 22:55:00 | 1 | 5 231 ms | 5 231 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.
Your signal
Tell us. Registration is not required. The same signal will not be counted repeatedly within a short period.
User opinions are separate from the technical outage status.
No ratings yet
No comments yet.
This page tracks the current observed status of Threads, recent incidents, automated availability checks and available user reports. NexIP does not treat a single failed check as proof of a global outage.
Ping · Website availability · Website monitoring · All service outages
NexIP shows the current observed status of Threads using automated checks, incident data and available user signals. A local connection problem may differ from a large-scale outage.
Availability can differ by provider, region, DNS, routing, application version or service component. NexIP therefore separates observed signals from confirmed large-scale incidents.
Check the host with Ping, website availability and your own connection. Comparing several independent checks helps distinguish a local problem from a wider outage.