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 03:00:00 | 4 | 5 207 ms | 5 232 ms | 0 | 0 |
| 2026-11-17 03:30:00 | 4 | 5 203 ms | 5 223 ms | 0 | 0 |
| 2026-11-17 04:00:00 | 3 | 5 208 ms | 5 215 ms | 0 | 0 |
| 2026-11-17 04:30:00 | 4 | 5 214 ms | 5 223 ms | 0 | 0 |
| 2026-11-17 05:00:00 | 4 | 5 203 ms | 5 216 ms | 0 | 0 |
| 2026-11-17 05:30:00 | 4 | 5 207 ms | 5 223 ms | 0 | 0 |
| 2026-11-17 06:00:00 | 3 | 5 209 ms | 5 225 ms | 0 | 0 |
| 2026-11-17 06:30:00 | 4 | 5 205 ms | 5 223 ms | 0 | 0 |
| 2026-11-17 07:00:00 | 4 | 5 208 ms | 5 220 ms | 0 | 0 |
| 2026-11-17 07:30:00 | 4 | 5 208 ms | 5 216 ms | 0 | 0 |
| 2026-11-17 08:00:00 | 4 | 5 199 ms | 5 208 ms | 0 | 0 |
| 2026-11-17 08:30:00 | 4 | 5 207 ms | 5 220 ms | 0 | 0 |
| 2026-11-17 09:00:00 | 4 | 5 208 ms | 5 218 ms | 0 | 0 |
| 2026-11-17 09:30:00 | 4 | 5 156 ms | 5 231 ms | 0 | 0 |
| 2026-11-17 10:00:00 | 4 | 5 210 ms | 5 222 ms | 0 | 0 |
| 2026-11-17 10:30:00 | 3 | 5 146 ms | 5 222 ms | 0 | 0 |
| 2026-11-17 11:00:00 | 4 | 5 234 ms | 5 255 ms | 0 | 0 |
| 2026-11-17 11:30:00 | 4 | 5 210 ms | 5 219 ms | 0 | 0 |
| 2026-11-17 12:00:00 | 4 | 5 230 ms | 5 253 ms | 0 | 0 |
| 2026-11-17 12:30:00 | 4 | 5 203 ms | 5 210 ms | 0 | 0 |
| 2026-11-17 13:00:00 | 3 | 5 226 ms | 5 267 ms | 0 | 0 |
| 2026-11-17 13:30:00 | 4 | 5 227 ms | 5 247 ms | 0 | 0 |
| 2026-11-17 14:00:00 | 4 | 5 221 ms | 5 266 ms | 0 | 0 |
| 2026-11-17 14:30:00 | 4 | 5 157 ms | 5 228 ms | 0 | 0 |
| 2026-11-17 15:00:00 | 3 | 5 213 ms | 5 217 ms | 0 | 0 |
| 2026-11-17 15:30:00 | 4 | 5 244 ms | 5 300 ms | 0 | 0 |
| 2026-11-17 16:00:00 | 4 | 5 212 ms | 5 217 ms | 0 | 0 |
| 2026-11-17 16:30:00 | 4 | 5 261 ms | 5 344 ms | 0 | 0 |
| 2026-11-17 17:00:00 | 3 | 5 215 ms | 5 228 ms | 0 | 0 |
| 2026-11-17 17:30:00 | 4 | 5 231 ms | 5 249 ms | 0 | 0 |
| 2026-11-17 18:00:00 | 4 | 5 195 ms | 5 322 ms | 0 | 0 |
| 2026-11-17 18:30:00 | 4 | 5 353 ms | 5 803 ms | 0 | 0 |
| 2026-11-17 19:00:00 | 3 | 5 803 ms | 6 881 ms | 0 | 0 |
| 2026-11-17 19:30:00 | 4 | 5 215 ms | 5 232 ms | 0 | 0 |
| 2026-11-17 20:00:00 | 4 | 5 377 ms | 5 528 ms | 0 | 0 |
| 2026-11-17 20:30:00 | 3 | 5 254 ms | 5 307 ms | 0 | 0 |
| 2026-11-17 21:00:00 | 4 | 5 421 ms | 5 709 ms | 0 | 0 |
| 2026-11-17 21:30:00 | 4 | 5 273 ms | 5 328 ms | 0 | 0 |
| 2026-11-17 22:00:00 | 3 | 5 383 ms | 5 700 ms | 0 | 0 |
| 2026-11-17 22:30:00 | 4 | 5 217 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.