Is Google Cloud AppSheet down?
Current Google Cloud AppSheet status is UP

Summary: The Issue with AppSheet automations/bots not sending AMP emails, and the preview of embedded views in the Editor is displaying errors.
Description: We are experiencing an issue with AppSheet beginning at Tuesday, 2024-04-16 13:30 US/Pacific.
Mitigation work is currently underway by our engineering team.
We will provide an update by Tuesday, 2024-04-16 21:25 US/Pacific with current details.
We apologize to all who are affected by the disruption.
Diagnosis: This affects customers using AMP emails (see https://support.google.com/appsheet/answer/11511240?hl=en). Non-AMP emails are unaffected.
Users are getting error in the Automation bot, which leads to the AMP email not being sent, while previewing the embedded view in the AppSheet gives the below error :
Error: Unable to load DLL 'ClearScriptV8.win-x64.dll' or one of its dependencies: The specified module could not be found. (0x8007007E)
Workaround: None at this time.

Summary: The Issue with AppSheet automations/bots not sending AMP emails, and the preview of embedded views in the Editor is displaying errors.
Description: We are experiencing an issue with AppSheet beginning at Tuesday, 2024-04-16 13:30 US/Pacific.
Mitigation work is currently underway by our engineering team.
We will provide an update by Tuesday, 2024-04-16 21:25 US/Pacific with current details.
We apologize to all who are affected by the disruption.
Diagnosis: This affects customers using AMP emails (see https://support.google.com/appsheet/answer/11511240?hl=en). Non-AMP emails are unaffected.
Users are getting error in the Automation bot, which leads to the AMP email not being sent, while previewing the embedded view in the AppSheet gives the below error :
Error: Unable to load DLL 'ClearScriptV8.win-x64.dll' or one of its dependencies: The specified module could not be found. (0x8007007E)
Workaround: None at this time.

Summary: AppSheet Databases UI is experiencing elevated errors when loading the AppSheet Database UI via web browsers.
Description: Mitigation work is currently underway by our engineering team.
The mitigation is expected to complete by Thursday, 2024-04-04 16:30 US/Pacific.
We will provide more information by Thursday, 2024-04-04 17:00 US/Pacific.
Diagnosis: All the customers using AppSheet Databases would encounter an error “Something has gone wrong” and are unable to manage their database data. However, there is no impact on the Apps using AppSheet Databases as their datasource.
Workaround: None at this time.

Summary: AppSheet Databases UI is experiencing elevated errors when loading the AppSheet Database UI via web browsers.
Description: Mitigation work is currently underway by our engineering team.
The mitigation is expected to complete by Thursday, 2024-04-04 16:30 US/Pacific.
We will provide more information by Thursday, 2024-04-04 17:00 US/Pacific.
Diagnosis: All the customers using AppSheet Databases would encounter an error “Something has gone wrong” and are unable to manage their database data. However, there is no impact on the Apps using AppSheet Databases as their datasource.
Workaround: None at this time.

Summary: Multiple Google Cloud products are impacted by a Cloud Monitoring issue
Description: We are experiencing an issue with Cloud monitoring which is impacting metrics and dashboards related to multiple products.
Our Engineering team identified two distinct issues causing the impact and are continuing to work on applying mitigations.
We are rolling out the mitigation for the gaps in monitoring data and estimate we are 90% mitigated. Engineers are evaluating the timeline to complete mitigation.
We have tested a mitigation for the delays in querying metric data in us-central1, the mitigation appears to reduce the backlog and we anticipate the delays to gradually return to base levels over the next 24 hours.
We will provide a progress update by Friday, 2024-01-12 08:00 US/Pacific with current details.
Diagnosis: Customers impacted by this issue may experience delays and in some cases may not see the metric data in their monitoring dashboard. Some dashboards may fail to load entirely.
GCP and third party products and services that consume these metrics via Cloud monitoring API may experience these above stated issues. This includes products that rely on metrics for autoscaling.
Alerting mechanisms reliant on this metric data may experience the issue too.
The issue affects alerts for both Google Cloud service defined and custom metrics. The metric data for custom metrics is unaffected by the issue.
Workaround: Customers that are querying metric data older than 24 hours can workaround timeout failures in loading the data by querying for data that is not older than 24 hours.
Alternatively, customers can load the metric data in their monitoring dashboards by excluding us-central1 using a location filter.
Customers can continue to write and query custom metric data newer than 24 hours without any issues.