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 03:00:00 | 4 | 800 ms | 808 ms | 0 | 0 |
| 2026-11-17 03:30:00 | 4 | 793 ms | 832 ms | 0 | 0 |
| 2026-11-17 04:00:00 | 3 | 785 ms | 835 ms | 0 | 0 |
| 2026-11-17 04:30:00 | 4 | 796 ms | 811 ms | 0 | 0 |
| 2026-11-17 05:00:00 | 4 | 811 ms | 847 ms | 0 | 0 |
| 2026-11-17 05:30:00 | 4 | 720 ms | 760 ms | 0 | 0 |
| 2026-11-17 06:00:00 | 3 | 801 ms | 827 ms | 0 | 0 |
| 2026-11-17 06:30:00 | 4 | 815 ms | 860 ms | 0 | 0 |
| 2026-11-17 07:00:00 | 4 | 799 ms | 852 ms | 0 | 0 |
| 2026-11-17 07:30:00 | 4 | 782 ms | 809 ms | 0 | 0 |
| 2026-11-17 08:00:00 | 4 | 779 ms | 804 ms | 0 | 0 |
| 2026-11-17 08:30:00 | 4 | 814 ms | 835 ms | 0 | 0 |
| 2026-11-17 09:00:00 | 4 | 941 ms | 998 ms | 0 | 0 |
| 2026-11-17 09:30:00 | 4 | 840 ms | 956 ms | 0 | 0 |
| 2026-11-17 10:00:00 | 4 | 1 142 ms | 1 716 ms | 0 | 0 |
| 2026-11-17 10:30:00 | 4 | 883 ms | 945 ms | 0 | 0 |
| 2026-11-17 11:00:00 | 3 | 1 180 ms | 1 886 ms | 0 | 0 |
| 2026-11-17 11:30:00 | 4 | 894 ms | 986 ms | 0 | 0 |
| 2026-11-17 12:00:00 | 4 | 896 ms | 1 024 ms | 0 | 0 |
| 2026-11-17 12:30:00 | 4 | 752 ms | 772 ms | 0 | 0 |
| 2026-11-17 13:00:00 | 4 | 1 015 ms | 1 121 ms | 0 | 0 |
| 2026-11-17 13:30:00 | 3 | 1 217 ms | 1 238 ms | 0 | 0 |
| 2026-11-17 14:00:00 | 4 | 1 129 ms | 1 181 ms | 0 | 0 |
| 2026-11-17 14:30:00 | 4 | 1 090 ms | 1 166 ms | 0 | 0 |
| 2026-11-17 15:00:00 | 4 | 1 185 ms | 1 235 ms | 0 | 0 |
| 2026-11-17 15:30:00 | 3 | 1 193 ms | 1 326 ms | 0 | 0 |
| 2026-11-17 16:00:00 | 4 | 1 119 ms | 1 127 ms | 0 | 0 |
| 2026-11-17 16:30:00 | 4 | 1 134 ms | 1 180 ms | 0 | 0 |
| 2026-11-17 17:00:00 | 4 | 1 180 ms | 1 215 ms | 0 | 0 |
| 2026-11-17 17:30:00 | 3 | 2 412 ms | 5 005 ms | 0 | 0 |
| 2026-11-17 18:00:00 | 4 | 1 172 ms | 1 261 ms | 0 | 0 |
| 2026-11-17 18:30:00 | 4 | 1 133 ms | 1 212 ms | 0 | 0 |
| 2026-11-17 19:00:00 | 3 | 1 167 ms | 1 288 ms | 0 | 0 |
| 2026-11-17 19:30:00 | 4 | 1 051 ms | 1 218 ms | 0 | 0 |
| 2026-11-17 20:00:00 | 4 | 2 885 ms | 6 578 ms | 0 | 0 |
| 2026-11-17 20:30:00 | 3 | 770 ms | 785 ms | 0 | 0 |
| 2026-11-17 21:00:00 | 4 | 778 ms | 791 ms | 0 | 0 |
| 2026-11-17 21:30:00 | 4 | 744 ms | 750 ms | 0 | 0 |
| 2026-11-17 22:00:00 | 3 | 774 ms | 806 ms | 0 | 0 |
| 2026-11-17 22:30:00 | 4 | 788 ms | 823 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.