How to interpret the monitoring status
Technical measurements reflect observations from the NexIP monitoring location. A failed or restricted request alone does not confirm a widespread outage.
← All services
Telecom operators
Is T2 down? Current status and outages
Доступ ограничен для NexIPАвтоматический запрос из точки 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
Limited
Response: 74 ms
Response time
74 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-09 12:00:00 | 22 | 75 ms | 82 ms | 0 | 22 |
| 2026-11-09 15:00:00 | 22 | 76 ms | 81 ms | 0 | 22 |
| 2026-11-09 18:00:00 | 23 | 76 ms | 81 ms | 0 | 23 |
| 2026-11-09 21:00:00 | 22 | 76 ms | 81 ms | 0 | 22 |
| 2026-11-10 00:00:00 | 23 | 78 ms | 90 ms | 0 | 23 |
| 2026-11-10 03:00:00 | 22 | 81 ms | 92 ms | 0 | 22 |
| 2026-11-10 06:00:00 | 23 | 74 ms | 78 ms | 0 | 23 |
| 2026-11-10 09:00:00 | 23 | 75 ms | 80 ms | 0 | 23 |
| 2026-11-10 12:00:00 | 22 | 81 ms | 172 ms | 0 | 22 |
| 2026-11-10 15:00:00 | 23 | 85 ms | 248 ms | 0 | 23 |
| 2026-11-10 18:00:00 | 22 | 79 ms | 87 ms | 0 | 22 |
| 2026-11-10 21:00:00 | 23 | 94 ms | 420 ms | 0 | 23 |
| 2026-11-11 00:00:00 | 22 | 76 ms | 80 ms | 0 | 22 |
| 2026-11-11 03:00:00 | 23 | 77 ms | 85 ms | 0 | 23 |
| 2026-11-11 06:00:00 | 22 | 78 ms | 83 ms | 0 | 22 |
| 2026-11-11 09:00:00 | 23 | 78 ms | 83 ms | 0 | 23 |
| 2026-11-11 12:00:00 | 22 | 79 ms | 84 ms | 0 | 22 |
| 2026-11-11 15:00:00 | 23 | 84 ms | 218 ms | 0 | 23 |
| 2026-11-11 18:00:00 | 22 | 79 ms | 90 ms | 0 | 22 |
| 2026-11-11 21:00:00 | 23 | 78 ms | 86 ms | 0 | 23 |
| 2026-11-12 00:00:00 | 22 | 77 ms | 120 ms | 0 | 22 |
| 2026-11-12 03:00:00 | 23 | 77 ms | 82 ms | 0 | 23 |
| 2026-11-12 06:00:00 | 22 | 76 ms | 95 ms | 0 | 22 |
| 2026-11-12 09:00:00 | 23 | 76 ms | 86 ms | 0 | 23 |
| 2026-11-12 12:00:00 | 22 | 75 ms | 78 ms | 0 | 22 |
| 2026-11-12 15:00:00 | 22 | 76 ms | 79 ms | 0 | 22 |
| 2026-11-12 18:00:00 | 23 | 76 ms | 80 ms | 0 | 23 |
| 2026-11-12 21:00:00 | 22 | 79 ms | 159 ms | 0 | 22 |
| 2026-11-13 00:00:00 | 23 | 78 ms | 95 ms | 0 | 23 |
| 2026-11-13 03:00:00 | 22 | 81 ms | 139 ms | 0 | 22 |
| 2026-11-13 06:00:00 | 23 | 75 ms | 77 ms | 0 | 23 |
| 2026-11-13 09:00:00 | 22 | 75 ms | 79 ms | 0 | 22 |
| 2026-11-13 12:00:00 | 23 | 81 ms | 191 ms | 0 | 23 |
| 2026-11-13 15:00:00 | 22 | 76 ms | 81 ms | 0 | 22 |
| 2026-11-13 18:00:00 | 23 | 77 ms | 100 ms | 0 | 23 |
| 2026-11-13 21:00:00 | 22 | 83 ms | 100 ms | 0 | 22 |
| 2026-11-14 00:00:00 | 23 | 74 ms | 78 ms | 0 | 23 |
| 2026-11-14 03:00:00 | 22 | 75 ms | 77 ms | 0 | 22 |
| 2026-11-14 06:00:00 | 23 | 74 ms | 78 ms | 0 | 23 |
| 2026-11-14 09:00:00 | 8 | 75 ms | 78 ms | 0 | 8 |
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:04
HTTP
503
Response time
74 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 T2 down?
This page tracks the current observed status of T2, 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 T2 down right now?
NexIP shows the current observed status of T2 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.