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.
Media
HTTP-проверка из точки NexIP успешна. Доступность из всех регионов не подтверждена.
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.
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
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-09 12:00:00 | 22 | 1 849 ms | 2 705 ms | 0 | 0 |
| 2026-11-09 15:00:00 | 22 | 1 834 ms | 3 413 ms | 0 | 0 |
| 2026-11-09 18:00:00 | 23 | 1 742 ms | 2 284 ms | 0 | 0 |
| 2026-11-09 21:00:00 | 22 | 2 041 ms | 3 686 ms | 0 | 0 |
| 2026-11-10 00:00:00 | 23 | 1 736 ms | 2 610 ms | 0 | 0 |
| 2026-11-10 03:00:00 | 22 | 1 727 ms | 2 146 ms | 0 | 0 |
| 2026-11-10 06:00:00 | 23 | 1 806 ms | 5 003 ms | 0 | 0 |
| 2026-11-10 09:00:00 | 23 | 1 549 ms | 2 129 ms | 0 | 0 |
| 2026-11-10 12:00:00 | 22 | 1 704 ms | 2 432 ms | 0 | 0 |
| 2026-11-10 15:00:00 | 23 | 2 016 ms | 3 361 ms | 0 | 0 |
| 2026-11-10 18:00:00 | 22 | 1 594 ms | 2 588 ms | 0 | 0 |
| 2026-11-10 21:00:00 | 23 | 1 848 ms | 2 983 ms | 0 | 0 |
| 2026-11-11 00:00:00 | 22 | 2 087 ms | 2 738 ms | 0 | 0 |
| 2026-11-11 03:00:00 | 23 | 1 949 ms | 2 734 ms | 0 | 0 |
| 2026-11-11 06:00:00 | 22 | 1 936 ms | 4 044 ms | 0 | 0 |
| 2026-11-11 09:00:00 | 23 | 2 047 ms | 5 186 ms | 0 | 0 |
| 2026-11-11 12:00:00 | 22 | 2 827 ms | 5 120 ms | 0 | 0 |
| 2026-11-11 15:00:00 | 23 | 3 459 ms | 7 427 ms | 0 | 0 |
| 2026-11-11 18:00:00 | 22 | 2 834 ms | 4 172 ms | 0 | 0 |
| 2026-11-11 21:00:00 | 23 | 2 197 ms | 2 770 ms | 0 | 0 |
| 2026-11-12 00:00:00 | 22 | 2 111 ms | 2 633 ms | 0 | 0 |
| 2026-11-12 03:00:00 | 23 | 2 152 ms | 2 820 ms | 0 | 0 |
| 2026-11-12 06:00:00 | 22 | 2 145 ms | 2 768 ms | 0 | 0 |
| 2026-11-12 09:00:00 | 23 | 2 032 ms | 2 827 ms | 0 | 0 |
| 2026-11-12 12:00:00 | 22 | 2 065 ms | 2 541 ms | 0 | 0 |
| 2026-11-12 15:00:00 | 22 | 1 861 ms | 2 694 ms | 0 | 0 |
| 2026-11-12 18:00:00 | 23 | 1 664 ms | 3 397 ms | 0 | 0 |
| 2026-11-12 21:00:00 | 22 | 1 727 ms | 5 575 ms | 0 | 0 |
| 2026-11-13 00:00:00 | 23 | 1 555 ms | 2 105 ms | 0 | 0 |
| 2026-11-13 03:00:00 | 22 | 1 512 ms | 2 060 ms | 0 | 0 |
| 2026-11-13 06:00:00 | 23 | 1 359 ms | 1 885 ms | 0 | 0 |
| 2026-11-13 09:00:00 | 22 | 1 449 ms | 2 276 ms | 0 | 0 |
| 2026-11-13 12:00:00 | 23 | 1 361 ms | 2 549 ms | 0 | 0 |
| 2026-11-13 15:00:00 | 22 | 1 546 ms | 2 644 ms | 0 | 0 |
| 2026-11-13 18:00:00 | 23 | 1 306 ms | 2 275 ms | 0 | 0 |
| 2026-11-13 21:00:00 | 22 | 1 534 ms | 4 074 ms | 0 | 0 |
| 2026-11-14 00:00:00 | 23 | 1 499 ms | 2 502 ms | 0 | 0 |
| 2026-11-14 03:00:00 | 22 | 1 578 ms | 2 281 ms | 0 | 0 |
| 2026-11-14 06:00:00 | 23 | 1 429 ms | 2 024 ms | 0 | 0 |
| 2026-11-14 09:00:00 | 8 | 1 519 ms | 2 450 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 Twitch, 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 Twitch 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.