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-13 00:00:00 | 23 | 5 204 ms | 5 237 ms | 0 | 0 |
| 2026-11-13 03:00:00 | 22 | 5 206 ms | 5 245 ms | 0 | 0 |
| 2026-11-13 06:00:00 | 23 | 5 200 ms | 5 230 ms | 0 | 0 |
| 2026-11-13 09:00:00 | 22 | 5 201 ms | 5 246 ms | 0 | 0 |
| 2026-11-13 12:00:00 | 23 | 5 210 ms | 5 273 ms | 0 | 0 |
| 2026-11-13 15:00:00 | 22 | 5 212 ms | 5 263 ms | 0 | 0 |
| 2026-11-13 18:00:00 | 23 | 5 307 ms | 6 124 ms | 0 | 0 |
| 2026-11-13 21:00:00 | 22 | 5 397 ms | 6 658 ms | 0 | 0 |
| 2026-11-14 00:00:00 | 23 | 5 209 ms | 5 240 ms | 0 | 0 |
| 2026-11-14 03:00:00 | 22 | 5 204 ms | 5 232 ms | 0 | 0 |
| 2026-11-14 06:00:00 | 23 | 5 205 ms | 5 275 ms | 0 | 0 |
| 2026-11-14 09:00:00 | 22 | 5 210 ms | 5 251 ms | 0 | 0 |
| 2026-11-14 12:00:00 | 23 | 5 209 ms | 5 289 ms | 0 | 0 |
| 2026-11-14 15:00:00 | 22 | 5 261 ms | 5 967 ms | 0 | 0 |
| 2026-11-14 18:00:00 | 23 | 5 279 ms | 6 003 ms | 0 | 0 |
| 2026-11-14 21:00:00 | 22 | 5 208 ms | 5 334 ms | 0 | 0 |
| 2026-11-15 00:00:00 | 23 | 5 207 ms | 5 250 ms | 0 | 0 |
| 2026-11-15 03:00:00 | 22 | 5 205 ms | 5 240 ms | 0 | 0 |
| 2026-11-15 06:00:00 | 22 | 5 204 ms | 5 232 ms | 0 | 0 |
| 2026-11-15 09:00:00 | 23 | 5 205 ms | 5 237 ms | 0 | 0 |
| 2026-11-15 12:00:00 | 22 | 5 210 ms | 5 255 ms | 0 | 0 |
| 2026-11-15 15:00:00 | 23 | 5 214 ms | 5 275 ms | 0 | 0 |
| 2026-11-15 18:00:00 | 22 | 5 207 ms | 5 289 ms | 0 | 0 |
| 2026-11-15 21:00:00 | 23 | 5 313 ms | 6 793 ms | 0 | 0 |
| 2026-11-16 00:00:00 | 22 | 5 202 ms | 5 239 ms | 0 | 0 |
| 2026-11-16 03:00:00 | 23 | 5 220 ms | 5 517 ms | 0 | 0 |
| 2026-11-16 06:00:00 | 22 | 5 201 ms | 5 242 ms | 0 | 0 |
| 2026-11-16 09:00:00 | 23 | 5 215 ms | 5 280 ms | 0 | 0 |
| 2026-11-16 12:00:00 | 22 | 5 270 ms | 6 373 ms | 0 | 0 |
| 2026-11-16 15:00:00 | 23 | 5 219 ms | 5 363 ms | 0 | 0 |
| 2026-11-16 18:00:00 | 23 | 5 198 ms | 5 240 ms | 0 | 0 |
| 2026-11-16 21:00:00 | 22 | 5 212 ms | 5 313 ms | 0 | 0 |
| 2026-11-17 00:00:00 | 23 | 5 192 ms | 5 230 ms | 0 | 0 |
| 2026-11-17 03:00:00 | 23 | 5 207 ms | 5 232 ms | 0 | 0 |
| 2026-11-17 06:00:00 | 23 | 5 206 ms | 5 225 ms | 0 | 0 |
| 2026-11-17 09:00:00 | 23 | 5 196 ms | 5 255 ms | 0 | 0 |
| 2026-11-17 12:00:00 | 23 | 5 210 ms | 5 267 ms | 0 | 0 |
| 2026-11-17 15:00:00 | 22 | 5 231 ms | 5 344 ms | 0 | 0 |
| 2026-11-17 18:00:00 | 22 | 5 352 ms | 6 881 ms | 0 | 0 |
| 2026-11-17 21:00:00 | 15 | 5 319 ms | 5 709 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.