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.
Cloud services
HTTP-проверка из точки NexIP успешна. Доступность из всех регионов не подтверждена.
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.
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
Мониторинг доступности сервиса Google Cloud, пользовательских сигналов и технических проверок NexIP.
Reports submitted to NexIP. One report does not prove a widespread outage.
No reports during this period.
30-minute intervals · Moscow time · actual dataLast 7 days
Observation points
Observation history
Actual NexIP primary probe measurements, not user reports
| Time (server) | Checks | Average | Peak | Down | Blocked |
|---|---|---|---|---|---|
| 2026-11-17 17:25:00 | 1 | 1 180 ms | 1 180 ms | 0 | 0 |
| 2026-11-17 17:35:00 | 1 | 5 005 ms | 5 005 ms | 0 | 0 |
| 2026-11-17 17:45:00 | 1 | 1 113 ms | 1 113 ms | 0 | 0 |
| 2026-11-17 17:50:00 | 1 | 1 117 ms | 1 117 ms | 0 | 0 |
| 2026-11-17 18:00:00 | 1 | 1 261 ms | 1 261 ms | 0 | 0 |
| 2026-11-17 18:05:00 | 1 | 1 200 ms | 1 200 ms | 0 | 0 |
| 2026-11-17 18:15:00 | 1 | 1 045 ms | 1 045 ms | 0 | 0 |
| 2026-11-17 18:25:00 | 1 | 1 182 ms | 1 182 ms | 0 | 0 |
| 2026-11-17 18:30:00 | 1 | 1 063 ms | 1 063 ms | 0 | 0 |
| 2026-11-17 18:40:00 | 1 | 1 123 ms | 1 123 ms | 0 | 0 |
| 2026-11-17 18:50:00 | 1 | 1 212 ms | 1 212 ms | 0 | 0 |
| 2026-11-17 18:55:00 | 1 | 1 132 ms | 1 132 ms | 0 | 0 |
| 2026-11-17 19:05:00 | 1 | 1 153 ms | 1 153 ms | 0 | 0 |
| 2026-11-17 19:15:00 | 1 | 1 288 ms | 1 288 ms | 0 | 0 |
| 2026-11-17 19:20:00 | 1 | 1 060 ms | 1 060 ms | 0 | 0 |
| 2026-11-17 19:30:00 | 1 | 1 218 ms | 1 218 ms | 0 | 0 |
| 2026-11-17 19:35:00 | 1 | 1 076 ms | 1 076 ms | 0 | 0 |
| 2026-11-17 19:45:00 | 1 | 1 129 ms | 1 129 ms | 0 | 0 |
| 2026-11-17 19:55:00 | 1 | 780 ms | 780 ms | 0 | 0 |
| 2026-11-17 20:00:00 | 1 | 6 578 ms | 6 578 ms | 0 | 0 |
| 2026-11-17 20:10:00 | 1 | 986 ms | 986 ms | 0 | 0 |
| 2026-11-17 20:20:00 | 1 | 707 ms | 707 ms | 0 | 0 |
| 2026-11-17 20:25:00 | 1 | 3 268 ms | 3 268 ms | 0 | 0 |
| 2026-11-17 20:35:00 | 1 | 780 ms | 780 ms | 0 | 0 |
| 2026-11-17 20:45:00 | 1 | 785 ms | 785 ms | 0 | 0 |
| 2026-11-17 20:50:00 | 1 | 745 ms | 745 ms | 0 | 0 |
| 2026-11-17 21:00:00 | 1 | 766 ms | 766 ms | 0 | 0 |
| 2026-11-17 21:05:00 | 1 | 791 ms | 791 ms | 0 | 0 |
| 2026-11-17 21:15:00 | 1 | 782 ms | 782 ms | 0 | 0 |
| 2026-11-17 21:25:00 | 1 | 774 ms | 774 ms | 0 | 0 |
| 2026-11-17 21:30:00 | 1 | 739 ms | 739 ms | 0 | 0 |
| 2026-11-17 21:40:00 | 1 | 738 ms | 738 ms | 0 | 0 |
| 2026-11-17 21:45:00 | 1 | 750 ms | 750 ms | 0 | 0 |
| 2026-11-17 21:55:00 | 1 | 750 ms | 750 ms | 0 | 0 |
| 2026-11-17 22:05:00 | 1 | 774 ms | 774 ms | 0 | 0 |
| 2026-11-17 22:10:00 | 1 | 741 ms | 741 ms | 0 | 0 |
| 2026-11-17 22:20:00 | 1 | 806 ms | 806 ms | 0 | 0 |
| 2026-11-17 22:30:00 | 1 | 823 ms | 823 ms | 0 | 0 |
| 2026-11-17 22:35:00 | 1 | 797 ms | 797 ms | 0 | 0 |
| 2026-11-17 22:45:00 | 1 | 758 ms | 758 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.
Your signal
Tell us. Registration is not required. The same signal will not be counted repeatedly within a short period.
User opinions are separate from the technical outage status.
No ratings yet
No comments yet.
This page tracks the current observed status of Google Cloud, recent incidents, automated availability checks and available user reports. NexIP does not treat a single failed check as proof of a global outage.
Ping · Website availability · Website monitoring · All service outages
NexIP shows the current observed status of Google Cloud using automated checks, incident data and available user signals. A local connection problem may differ from a large-scale outage.
Availability can differ by provider, region, DNS, routing, application version or service component. NexIP therefore separates observed signals from confirmed large-scale incidents.
Check the host with Ping, website availability and your own connection. Comparing several independent checks helps distinguish a local problem from a wider outage.