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
Telecom operators
Is МТС 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: 495 ms
Response time
495 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-12 19:00:00 | 7 | 649 ms | 842 ms | 0 | 0 |
| 2026-11-12 20:00:00 | 8 | 640 ms | 861 ms | 0 | 0 |
| 2026-11-12 21:00:00 | 7 | 622 ms | 925 ms | 0 | 0 |
| 2026-11-12 22:00:00 | 8 | 528 ms | 610 ms | 0 | 0 |
| 2026-11-12 23:00:00 | 7 | 534 ms | 600 ms | 0 | 0 |
| 2026-11-13 00:00:00 | 8 | 489 ms | 555 ms | 0 | 0 |
| 2026-11-13 01:00:00 | 7 | 596 ms | 792 ms | 0 | 0 |
| 2026-11-13 02:00:00 | 7 | 523 ms | 592 ms | 0 | 0 |
| 2026-11-13 03:00:00 | 8 | 560 ms | 618 ms | 0 | 0 |
| 2026-11-13 04:00:00 | 7 | 542 ms | 811 ms | 0 | 0 |
| 2026-11-13 05:00:00 | 8 | 489 ms | 535 ms | 0 | 0 |
| 2026-11-13 06:00:00 | 8 | 567 ms | 871 ms | 0 | 0 |
| 2026-11-13 07:00:00 | 7 | 527 ms | 678 ms | 0 | 0 |
| 2026-11-13 08:00:00 | 7 | 641 ms | 894 ms | 0 | 0 |
| 2026-11-13 09:00:00 | 8 | 672 ms | 881 ms | 0 | 0 |
| 2026-11-13 10:00:00 | 7 | 1 027 ms | 2 918 ms | 0 | 0 |
| 2026-11-13 11:00:00 | 8 | 1 084 ms | 3 514 ms | 0 | 0 |
| 2026-11-13 12:00:00 | 7 | 801 ms | 2 260 ms | 0 | 0 |
| 2026-11-13 13:00:00 | 8 | 564 ms | 798 ms | 0 | 0 |
| 2026-11-13 14:00:00 | 7 | 566 ms | 663 ms | 0 | 0 |
| 2026-11-13 15:00:00 | 8 | 625 ms | 1 085 ms | 0 | 0 |
| 2026-11-13 16:00:00 | 8 | 580 ms | 671 ms | 0 | 0 |
| 2026-11-13 17:00:00 | 7 | 1 217 ms | 3 377 ms | 1 | 0 |
| 2026-11-13 18:00:00 | 8 | 625 ms | 1 029 ms | 0 | 0 |
| 2026-11-13 19:00:00 | 7 | 557 ms | 720 ms | 0 | 0 |
| 2026-11-13 20:00:00 | 7 | 555 ms | 708 ms | 0 | 0 |
| 2026-11-13 21:00:00 | 8 | 694 ms | 1 230 ms | 0 | 0 |
| 2026-11-13 22:00:00 | 8 | 603 ms | 842 ms | 0 | 0 |
| 2026-11-13 23:00:00 | 7 | 586 ms | 745 ms | 0 | 0 |
| 2026-11-14 00:00:00 | 8 | 508 ms | 551 ms | 0 | 0 |
| 2026-11-14 01:00:00 | 7 | 579 ms | 1 165 ms | 0 | 0 |
| 2026-11-14 02:00:00 | 8 | 554 ms | 962 ms | 0 | 0 |
| 2026-11-14 03:00:00 | 7 | 471 ms | 527 ms | 0 | 0 |
| 2026-11-14 04:00:00 | 8 | 508 ms | 725 ms | 0 | 0 |
| 2026-11-14 05:00:00 | 7 | 487 ms | 510 ms | 0 | 0 |
| 2026-11-14 06:00:00 | 8 | 547 ms | 872 ms | 0 | 0 |
| 2026-11-14 07:00:00 | 7 | 512 ms | 584 ms | 0 | 0 |
| 2026-11-14 08:00:00 | 8 | 534 ms | 831 ms | 0 | 0 |
| 2026-11-14 09:00:00 | 7 | 605 ms | 1 098 ms | 0 | 0 |
| 2026-11-14 10:00:00 | 1 | 495 ms | 495 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:56
10:03
Last check
2026-11-14 10:03:43
HTTP
200
Response time
495 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 МТС down?
This page tracks the current observed status of МТС, 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 МТС down right now?
NexIP shows the current observed status of МТС 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.