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 Rutube 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: 393 ms
Response time
393 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-14 04:35:00 | 1 | 734 ms | 734 ms | 0 | 0 |
| 2026-11-14 04:40:00 | 1 | 372 ms | 372 ms | 0 | 0 |
| 2026-11-14 04:50:00 | 1 | 383 ms | 383 ms | 0 | 0 |
| 2026-11-14 04:55:00 | 1 | 391 ms | 391 ms | 0 | 0 |
| 2026-11-14 05:05:00 | 1 | 371 ms | 371 ms | 0 | 0 |
| 2026-11-14 05:10:00 | 1 | 362 ms | 362 ms | 0 | 0 |
| 2026-11-14 05:20:00 | 1 | 370 ms | 370 ms | 0 | 0 |
| 2026-11-14 05:30:00 | 1 | 384 ms | 384 ms | 0 | 0 |
| 2026-11-14 05:35:00 | 1 | 393 ms | 393 ms | 0 | 0 |
| 2026-11-14 05:45:00 | 1 | 390 ms | 390 ms | 0 | 0 |
| 2026-11-14 05:50:00 | 1 | 418 ms | 418 ms | 0 | 0 |
| 2026-11-14 06:00:00 | 1 | 756 ms | 756 ms | 0 | 0 |
| 2026-11-14 06:10:00 | 1 | 385 ms | 385 ms | 0 | 0 |
| 2026-11-14 06:15:00 | 1 | 378 ms | 378 ms | 0 | 0 |
| 2026-11-14 06:25:00 | 1 | 669 ms | 669 ms | 0 | 0 |
| 2026-11-14 06:35:00 | 1 | 387 ms | 387 ms | 0 | 0 |
| 2026-11-14 06:40:00 | 1 | 964 ms | 964 ms | 0 | 0 |
| 2026-11-14 06:50:00 | 1 | 382 ms | 382 ms | 0 | 0 |
| 2026-11-14 06:55:00 | 1 | 391 ms | 391 ms | 0 | 0 |
| 2026-11-14 07:05:00 | 1 | 389 ms | 389 ms | 0 | 0 |
| 2026-11-14 07:15:00 | 1 | 393 ms | 393 ms | 0 | 0 |
| 2026-11-14 07:20:00 | 1 | 422 ms | 422 ms | 0 | 0 |
| 2026-11-14 07:30:00 | 1 | 372 ms | 372 ms | 0 | 0 |
| 2026-11-14 07:35:00 | 1 | 413 ms | 413 ms | 0 | 0 |
| 2026-11-14 07:45:00 | 1 | 372 ms | 372 ms | 0 | 0 |
| 2026-11-14 07:55:00 | 1 | 376 ms | 376 ms | 0 | 0 |
| 2026-11-14 08:00:00 | 1 | 388 ms | 388 ms | 0 | 0 |
| 2026-11-14 08:10:00 | 1 | 386 ms | 386 ms | 0 | 0 |
| 2026-11-14 08:15:00 | 1 | 391 ms | 391 ms | 0 | 0 |
| 2026-11-14 08:25:00 | 1 | 385 ms | 385 ms | 0 | 0 |
| 2026-11-14 08:35:00 | 1 | 462 ms | 462 ms | 0 | 0 |
| 2026-11-14 08:40:00 | 1 | 385 ms | 385 ms | 0 | 0 |
| 2026-11-14 08:50:00 | 1 | 805 ms | 805 ms | 0 | 0 |
| 2026-11-14 08:55:00 | 1 | 377 ms | 377 ms | 0 | 0 |
| 2026-11-14 09:05:00 | 1 | 377 ms | 377 ms | 0 | 0 |
| 2026-11-14 09:10:00 | 1 | 404 ms | 404 ms | 0 | 0 |
| 2026-11-14 09:20:00 | 1 | 377 ms | 377 ms | 0 | 0 |
| 2026-11-14 09:30:00 | 1 | 397 ms | 397 ms | 0 | 0 |
| 2026-11-14 09:35:00 | 1 | 381 ms | 381 ms | 0 | 0 |
| 2026-11-14 09:45:00 | 1 | 393 ms | 393 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:43
06:51
06:59
07:07
07:15
07:23
07:31
07:39
07:47
07:55
08:03
08:10
08:19
08:27
08:35
08:43
08:50
08:59
09:07
09:14
09:23
09:31
09:39
09:46
Last check
2026-11-14 09:46:59
HTTP
200
Response time
393 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 Rutube down?
This page tracks the current observed status of Rutube, 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 Rutube down right now?
NexIP shows the current observed status of Rutube 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.