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: 369 ms
Response time
369 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 | 394 ms | 412 ms | 0 | 0 |
| 2026-11-13 15:00:00 | 3 | 421 ms | 440 ms | 0 | 0 |
| 2026-11-13 15:30:00 | 4 | 388 ms | 421 ms | 0 | 0 |
| 2026-11-13 16:00:00 | 4 | 428 ms | 471 ms | 0 | 0 |
| 2026-11-13 16:30:00 | 4 | 422 ms | 489 ms | 0 | 0 |
| 2026-11-13 17:00:00 | 3 | 396 ms | 400 ms | 0 | 0 |
| 2026-11-13 17:30:00 | 4 | 396 ms | 406 ms | 0 | 0 |
| 2026-11-13 18:00:00 | 4 | 386 ms | 402 ms | 0 | 0 |
| 2026-11-13 18:30:00 | 4 | 424 ms | 501 ms | 0 | 0 |
| 2026-11-13 19:00:00 | 3 | 469 ms | 601 ms | 0 | 0 |
| 2026-11-13 19:30:00 | 4 | 440 ms | 578 ms | 0 | 0 |
| 2026-11-13 20:00:00 | 4 | 430 ms | 569 ms | 0 | 0 |
| 2026-11-13 20:30:00 | 4 | 463 ms | 651 ms | 0 | 0 |
| 2026-11-13 21:00:00 | 3 | 391 ms | 407 ms | 0 | 0 |
| 2026-11-13 21:30:00 | 4 | 393 ms | 403 ms | 0 | 0 |
| 2026-11-13 22:00:00 | 4 | 408 ms | 423 ms | 0 | 0 |
| 2026-11-13 22:30:00 | 4 | 453 ms | 531 ms | 0 | 0 |
| 2026-11-13 23:00:00 | 3 | 428 ms | 485 ms | 0 | 0 |
| 2026-11-13 23:30:00 | 4 | 507 ms | 751 ms | 0 | 0 |
| 2026-11-14 00:00:00 | 4 | 378 ms | 396 ms | 0 | 0 |
| 2026-11-14 00:30:00 | 4 | 380 ms | 407 ms | 0 | 0 |
| 2026-11-14 01:00:00 | 3 | 394 ms | 401 ms | 0 | 0 |
| 2026-11-14 01:30:00 | 4 | 375 ms | 385 ms | 0 | 0 |
| 2026-11-14 02:00:00 | 4 | 398 ms | 421 ms | 0 | 0 |
| 2026-11-14 02:30:00 | 4 | 461 ms | 704 ms | 0 | 0 |
| 2026-11-14 03:00:00 | 3 | 377 ms | 403 ms | 0 | 0 |
| 2026-11-14 03:30:00 | 4 | 378 ms | 386 ms | 0 | 0 |
| 2026-11-14 04:00:00 | 4 | 390 ms | 414 ms | 0 | 0 |
| 2026-11-14 04:30:00 | 4 | 470 ms | 734 ms | 0 | 0 |
| 2026-11-14 05:00:00 | 3 | 368 ms | 371 ms | 0 | 0 |
| 2026-11-14 05:30:00 | 4 | 396 ms | 418 ms | 0 | 0 |
| 2026-11-14 06:00:00 | 4 | 547 ms | 756 ms | 0 | 0 |
| 2026-11-14 06:30:00 | 4 | 531 ms | 964 ms | 0 | 0 |
| 2026-11-14 07:00:00 | 3 | 401 ms | 422 ms | 0 | 0 |
| 2026-11-14 07:30:00 | 4 | 383 ms | 413 ms | 0 | 0 |
| 2026-11-14 08:00:00 | 4 | 388 ms | 391 ms | 0 | 0 |
| 2026-11-14 08:30:00 | 4 | 507 ms | 805 ms | 0 | 0 |
| 2026-11-14 09:00:00 | 3 | 386 ms | 404 ms | 0 | 0 |
| 2026-11-14 09:30:00 | 4 | 392 ms | 397 ms | 0 | 0 |
| 2026-11-14 10:00:00 | 1 | 369 ms | 369 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: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
09:55
10:02
Last check
2026-11-14 10:02:56
HTTP
200
Response time
369 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.