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.
← All services
Media
Is Twitch down? Current status and outages
Доступен из точки NexIPHTTP-проверка из точки NexIP успешна. Доступность из всех регионов не подтверждена.
Understanding the metrics
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
Current state
Outage score
0/100
Statistical assessment
User signals
0
unique in the last 15 minutes
Automatic check
Available
Response: 2279 ms
Response time
2279 ms
Last local automatic check
User reports over the last 24 hours
Reports submitted to NexIP. One report does not prove a widespread outage.
Reports in selected period
0
No reports during this period.
30-minute intervals · Moscow time · actual dataLast 7 days
Recent incidents
No confirmed large-scale incidents were recorded during the last 7 days.
Observation points
Regional checks
Remote observation points are not connected yet.
Observation history
Latest automatic checks
OUTAGE INTELLIGENCE / SERVICE PROBES
Check history and reliability
Actual NexIP primary probe measurements, not user reports
Full-period overviewAll observations
Latest 40 intervals · CSV includes entire selection
| Time (server) | Checks | Average | Peak | Down | Blocked |
|---|---|---|---|---|---|
| 2026-11-13 14:30:00 | 4 | 1 626 ms | 1 680 ms | 0 | 0 |
| 2026-11-13 15:00:00 | 3 | 1 783 ms | 2 644 ms | 0 | 0 |
| 2026-11-13 15:30:00 | 4 | 1 753 ms | 2 534 ms | 0 | 0 |
| 2026-11-13 16:00:00 | 4 | 1 442 ms | 1 764 ms | 0 | 0 |
| 2026-11-13 16:30:00 | 4 | 1 193 ms | 1 787 ms | 0 | 0 |
| 2026-11-13 17:00:00 | 3 | 1 743 ms | 1 842 ms | 0 | 0 |
| 2026-11-13 17:30:00 | 4 | 1 468 ms | 1 888 ms | 0 | 0 |
| 2026-11-13 18:00:00 | 4 | 1 001 ms | 1 685 ms | 0 | 0 |
| 2026-11-13 18:30:00 | 4 | 1 205 ms | 1 654 ms | 0 | 0 |
| 2026-11-13 19:00:00 | 3 | 1 556 ms | 2 275 ms | 0 | 0 |
| 2026-11-13 19:30:00 | 4 | 1 416 ms | 1 765 ms | 0 | 0 |
| 2026-11-13 20:00:00 | 4 | 1 177 ms | 1 573 ms | 0 | 0 |
| 2026-11-13 20:30:00 | 4 | 1 547 ms | 1 663 ms | 0 | 0 |
| 2026-11-13 21:00:00 | 3 | 1 510 ms | 2 846 ms | 0 | 0 |
| 2026-11-13 21:30:00 | 4 | 1 241 ms | 1 850 ms | 0 | 0 |
| 2026-11-13 22:00:00 | 4 | 2 189 ms | 4 074 ms | 0 | 0 |
| 2026-11-13 22:30:00 | 4 | 1 384 ms | 2 110 ms | 0 | 0 |
| 2026-11-13 23:00:00 | 3 | 1 764 ms | 1 828 ms | 0 | 0 |
| 2026-11-13 23:30:00 | 4 | 1 169 ms | 1 895 ms | 0 | 0 |
| 2026-11-14 00:00:00 | 4 | 1 547 ms | 1 824 ms | 0 | 0 |
| 2026-11-14 00:30:00 | 4 | 1 730 ms | 2 502 ms | 0 | 0 |
| 2026-11-14 01:00:00 | 3 | 1 359 ms | 1 733 ms | 0 | 0 |
| 2026-11-14 01:30:00 | 4 | 1 481 ms | 2 316 ms | 0 | 0 |
| 2026-11-14 02:00:00 | 4 | 1 640 ms | 2 348 ms | 0 | 0 |
| 2026-11-14 02:30:00 | 4 | 1 204 ms | 2 041 ms | 0 | 0 |
| 2026-11-14 03:00:00 | 3 | 1 506 ms | 1 692 ms | 0 | 0 |
| 2026-11-14 03:30:00 | 4 | 1 711 ms | 1 923 ms | 0 | 0 |
| 2026-11-14 04:00:00 | 4 | 1 818 ms | 2 281 ms | 0 | 0 |
| 2026-11-14 04:30:00 | 4 | 1 638 ms | 1 691 ms | 0 | 0 |
| 2026-11-14 05:00:00 | 3 | 1 599 ms | 1 713 ms | 0 | 0 |
| 2026-11-14 05:30:00 | 4 | 1 180 ms | 1 863 ms | 0 | 0 |
| 2026-11-14 06:00:00 | 4 | 1 484 ms | 2 024 ms | 0 | 0 |
| 2026-11-14 06:30:00 | 4 | 1 785 ms | 1 935 ms | 0 | 0 |
| 2026-11-14 07:00:00 | 3 | 1 298 ms | 1 973 ms | 0 | 0 |
| 2026-11-14 07:30:00 | 4 | 1 364 ms | 1 743 ms | 0 | 0 |
| 2026-11-14 08:00:00 | 4 | 1 299 ms | 1 728 ms | 0 | 0 |
| 2026-11-14 08:30:00 | 4 | 1 312 ms | 1 613 ms | 0 | 0 |
| 2026-11-14 09:00:00 | 3 | 1 338 ms | 1 605 ms | 0 | 0 |
| 2026-11-14 09:30:00 | 4 | 1 464 ms | 2 450 ms | 0 | 0 |
| 2026-11-14 10:00:00 | 1 | 2 279 ms | 2 279 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.
06:59
07:07
07:15
07:23
07:31
07:39
07:47
07:55
08:03
08:11
08:19
08:27
08:35
08:43
08:51
08:59
09:07
09:15
09:23
09:31
09:39
09:47
09:55
10:03
Last check
2026-11-14 10:03:13
HTTP
200
Response time
2279 ms
Your signal
Having a problem with this service?
Tell us. Registration is not required. The same signal will not be counted repeatedly within a short period.
Community reviews
User opinions are separate from the technical outage status.
Your rating
No ratings yet
Leave a comment
Published comments
No comments yet.
Is Twitch down?
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.
Additional diagnostics
Ping · Website availability · Website monitoring · All service outages
Frequently asked questions
Is Twitch down right now?
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.
Why can the service work for some users but not others?
Availability can differ by provider, region, DNS, routing, application version or service component. NexIP therefore separates observed signals from confirmed large-scale incidents.
How can I check whether the problem is on my side?
Check the host with Ping, website availability and your own connection. Comparing several independent checks helps distinguish a local problem from a wider outage.