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
Government services
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: 147 ms
Response time
147 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 | 154 ms | 154 ms | 0 | 0 |
| 2026-11-14 04:40:00 | 1 | 147 ms | 147 ms | 0 | 0 |
| 2026-11-14 04:50:00 | 1 | 169 ms | 169 ms | 0 | 0 |
| 2026-11-14 04:55:00 | 1 | 176 ms | 176 ms | 0 | 0 |
| 2026-11-14 05:05:00 | 1 | 180 ms | 180 ms | 0 | 0 |
| 2026-11-14 05:15:00 | 1 | 188 ms | 188 ms | 0 | 0 |
| 2026-11-14 05:20:00 | 1 | 158 ms | 158 ms | 0 | 0 |
| 2026-11-14 05:30:00 | 1 | 175 ms | 175 ms | 0 | 0 |
| 2026-11-14 05:35:00 | 1 | 154 ms | 154 ms | 0 | 0 |
| 2026-11-14 05:45:00 | 1 | 149 ms | 149 ms | 0 | 0 |
| 2026-11-14 05:55:00 | 1 | 153 ms | 153 ms | 0 | 0 |
| 2026-11-14 06:00:00 | 1 | 182 ms | 182 ms | 0 | 0 |
| 2026-11-14 06:10:00 | 1 | 157 ms | 157 ms | 0 | 0 |
| 2026-11-14 06:15:00 | 1 | 184 ms | 184 ms | 0 | 0 |
| 2026-11-14 06:25:00 | 1 | 188 ms | 188 ms | 0 | 0 |
| 2026-11-14 06:35:00 | 1 | 201 ms | 201 ms | 0 | 0 |
| 2026-11-14 06:40:00 | 1 | 155 ms | 155 ms | 0 | 0 |
| 2026-11-14 06:50:00 | 1 | 157 ms | 157 ms | 0 | 0 |
| 2026-11-14 06:55:00 | 1 | 181 ms | 181 ms | 0 | 0 |
| 2026-11-14 07:05:00 | 1 | 148 ms | 148 ms | 0 | 0 |
| 2026-11-14 07:15:00 | 1 | 135 ms | 135 ms | 0 | 0 |
| 2026-11-14 07:20:00 | 1 | 145 ms | 145 ms | 0 | 0 |
| 2026-11-14 07:30:00 | 1 | 149 ms | 149 ms | 0 | 0 |
| 2026-11-14 07:35:00 | 1 | 152 ms | 152 ms | 0 | 0 |
| 2026-11-14 07:45:00 | 1 | 183 ms | 183 ms | 0 | 0 |
| 2026-11-14 07:55:00 | 1 | 157 ms | 157 ms | 0 | 0 |
| 2026-11-14 08:00:00 | 1 | 181 ms | 181 ms | 0 | 0 |
| 2026-11-14 08:10:00 | 1 | 146 ms | 146 ms | 0 | 0 |
| 2026-11-14 08:15:00 | 1 | 186 ms | 186 ms | 0 | 0 |
| 2026-11-14 08:25:00 | 1 | 163 ms | 163 ms | 0 | 0 |
| 2026-11-14 08:35:00 | 1 | 176 ms | 176 ms | 0 | 0 |
| 2026-11-14 08:40:00 | 1 | 158 ms | 158 ms | 0 | 0 |
| 2026-11-14 08:50:00 | 1 | 148 ms | 148 ms | 0 | 0 |
| 2026-11-14 08:55:00 | 1 | 160 ms | 160 ms | 0 | 0 |
| 2026-11-14 09:05:00 | 1 | 212 ms | 212 ms | 0 | 0 |
| 2026-11-14 09:15:00 | 1 | 160 ms | 160 ms | 0 | 0 |
| 2026-11-14 09:20:00 | 1 | 152 ms | 152 ms | 0 | 0 |
| 2026-11-14 09:30:00 | 1 | 160 ms | 160 ms | 0 | 0 |
| 2026-11-14 09:35:00 | 1 | 165 ms | 165 ms | 0 | 0 |
| 2026-11-14 09:45:00 | 1 | 147 ms | 147 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:44
06:51
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
Last check
2026-11-14 09:47:41
HTTP
200
Response time
147 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.