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-14 04:35:00 | 1 | 1 691 ms | 1 691 ms | 0 | 0 |
| 2026-11-14 04:40:00 | 1 | 1 545 ms | 1 545 ms | 0 | 0 |
| 2026-11-14 04:50:00 | 1 | 1 648 ms | 1 648 ms | 0 | 0 |
| 2026-11-14 04:55:00 | 1 | 1 669 ms | 1 669 ms | 0 | 0 |
| 2026-11-14 05:05:00 | 1 | 1 571 ms | 1 571 ms | 0 | 0 |
| 2026-11-14 05:15:00 | 1 | 1 713 ms | 1 713 ms | 0 | 0 |
| 2026-11-14 05:20:00 | 1 | 1 514 ms | 1 514 ms | 0 | 0 |
| 2026-11-14 05:30:00 | 1 | 1 863 ms | 1 863 ms | 0 | 0 |
| 2026-11-14 05:35:00 | 1 | 595 ms | 595 ms | 0 | 0 |
| 2026-11-14 05:45:00 | 1 | 589 ms | 589 ms | 0 | 0 |
| 2026-11-14 05:55:00 | 1 | 1 674 ms | 1 674 ms | 0 | 0 |
| 2026-11-14 06:00:00 | 1 | 1 368 ms | 1 368 ms | 0 | 0 |
| 2026-11-14 06:10:00 | 1 | 1 509 ms | 1 509 ms | 0 | 0 |
| 2026-11-14 06:15:00 | 1 | 2 024 ms | 2 024 ms | 0 | 0 |
| 2026-11-14 06:25:00 | 1 | 1 035 ms | 1 035 ms | 0 | 0 |
| 2026-11-14 06:35:00 | 1 | 1 885 ms | 1 885 ms | 0 | 0 |
| 2026-11-14 06:40:00 | 1 | 1 935 ms | 1 935 ms | 0 | 0 |
| 2026-11-14 06:50:00 | 1 | 1 773 ms | 1 773 ms | 0 | 0 |
| 2026-11-14 06:55:00 | 1 | 1 548 ms | 1 548 ms | 0 | 0 |
| 2026-11-14 07:05:00 | 1 | 1 973 ms | 1 973 ms | 0 | 0 |
| 2026-11-14 07:15:00 | 1 | 553 ms | 553 ms | 0 | 0 |
| 2026-11-14 07:20:00 | 1 | 1 369 ms | 1 369 ms | 0 | 0 |
| 2026-11-14 07:30:00 | 1 | 1 637 ms | 1 637 ms | 0 | 0 |
| 2026-11-14 07:35:00 | 1 | 1 536 ms | 1 536 ms | 0 | 0 |
| 2026-11-14 07:45:00 | 1 | 541 ms | 541 ms | 0 | 0 |
| 2026-11-14 07:55:00 | 1 | 1 743 ms | 1 743 ms | 0 | 0 |
| 2026-11-14 08:00:00 | 1 | 1 607 ms | 1 607 ms | 0 | 0 |
| 2026-11-14 08:10:00 | 1 | 870 ms | 870 ms | 0 | 0 |
| 2026-11-14 08:15:00 | 1 | 1 728 ms | 1 728 ms | 0 | 0 |
| 2026-11-14 08:25:00 | 1 | 990 ms | 990 ms | 0 | 0 |
| 2026-11-14 08:35:00 | 1 | 1 613 ms | 1 613 ms | 0 | 0 |
| 2026-11-14 08:40:00 | 1 | 1 527 ms | 1 527 ms | 0 | 0 |
| 2026-11-14 08:50:00 | 1 | 903 ms | 903 ms | 0 | 0 |
| 2026-11-14 08:55:00 | 1 | 1 203 ms | 1 203 ms | 0 | 0 |
| 2026-11-14 09:05:00 | 1 | 1 605 ms | 1 605 ms | 0 | 0 |
| 2026-11-14 09:15:00 | 1 | 1 349 ms | 1 349 ms | 0 | 0 |
| 2026-11-14 09:20:00 | 1 | 1 061 ms | 1 061 ms | 0 | 0 |
| 2026-11-14 09:30:00 | 1 | 695 ms | 695 ms | 0 | 0 |
| 2026-11-14 09:35:00 | 1 | 1 813 ms | 1 813 ms | 0 | 0 |
| 2026-11-14 09:45:00 | 1 | 898 ms | 898 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.