Google Cloud vs. Netlify

Compare the status, incidents stats and history between Google Cloud and Netlify

Every service has different practices when updating its status page, so compare these stats with a grain of salt. E.g., one service can be more aggressive when updating its status page than other so that they will have more incidents, but it doesn't mean it is worse than the other.

Google Cloud

Google Cloud current official status is Minor Outage

Statistics

5
Incidents in the last 7 days
32
Incidents in the last 30 days
77
Incidents in the last 90 days

Latest incidents

Ongoing MemoryStore for Redis - instances update/export failures

Summary: MemoryStore for Redis - instances update/export failures Description: Mitigation work is underway by our engineering team. We will provide more information by Tuesday, 2022-09-27 15:00 US/...

about 4 hours ago Official incident report
Resolved Firestore degraded performance in europe-west3

Summary: Firestore degraded performance in europe-west3 Description: We are experiencing an issue with Cloud Firestore beginning at Tuesday, 2022-09-27 00:02 US/Pacific. Our engineering team contin...

about 9 hours ago Official incident report
Resolved Google Cloud Console is experiencing issue with displaying the list of compute instances.

Summary: Google Cloud Console is experiencing issue with displaying the list of compute instances. Description: We are experiencing an issue with Google Cloud Console. Our engineering team continue...

Netlify

Netlify current official status is Operational

Statistics

3
Incidents in the last 7 days
12
Incidents in the last 30 days
34
Incidents in the last 90 days

Latest incidents

Resolved Increased Errors and Latency on Origin, Standard and High-Performance Edge, API, and Build System

From 21:02 UTC to 21:06 UTC there were increased errors on our Origin Servers, Standard and High-Performance Edge Network, API, and Build System. The team has found the root cause and mitigated the...

Resolved API and Build System Degradation

Beginning at 16:44 UTC, we observed increased latency and errors in our API and build system. The affected components have returned to normal and the team continues to monitor.

Resolved Connection Timeouts on Standard Edge Network Load Balancer.

Starting at 11:29 UTC our legacy TCP load balancer with IP 104.198.14.52 is suffering connection timeouts due to an upstream provider problem. Customers still pointing to this Load Balancer via A r...

Easily monitor all your services providers

Increase the productivity and efficiency of your team. Enable monitoring for your services, and start receiving real-time alerts when your external dependencies have outages.

Start today for FREE