[Resolved] AppSheet is experiencing high latencies

[Jana_Mandic]

The incident started at 12:10 am Pacific. We're attempting to mitigate. I'll update here as we know more.

UPDATE: As of 2:40 am, latencies have recovered. We are still unsure of the root cause but are continuing to investigate.

UPDATE 2: The incident is resolved. We will continue to root cause in the morning and we will share a root cause analysis in the next few days.

I deeply apologize for this service disruption. The third in a week. We know how disruptive these outages are and we do take them seriously.

This community post is not the most effective way to communicate outages and we're working on fixing that by standing up a dashboard where you can monitor service status more reliably. I sincerely hope that there will not be another incident before that dashboard is up. However if an incident should occur, we will make use of this Community site as we did today. Thank you for bearing with us.

FINAL UPDATE -- RCA: A scaling capacity issue in one of our regions was preventing that region from scaling up to handle request volume. We've addressed 1) the root cause of the scaling issue, 2) added in load shedding to other regions, and 3) increased alert coverage. 

[GNF]

Please, resolve it more quickly! Recently, similar incidents have been occurring every week. Both we and our customers are losing confidence in the system.

[Rifad]

---

@GNF wrote:

Please, resolve it more quickly! Recently, similar incidents have been occurring every week. Both we and our customers are losing confidence in the system.

---

100% true, but having official announcements like this is better than just telling clients that AppSheet is down. They might not ask for proof since it's a rare occurrence, but it can shake their confidence and leave us feeling out of options it it keeps occuring. I appreciate this announcement right now. @Jana_Mandic 

[Rifad]

However, this seems to be one of the longest outrages with AppSheet in recent years.

[WillowMobileSys]

---

@GNF wrote:

Please, resolve it more quickly! 

---

That's like asking the paint to dry faster.  Unfortunately, it takes as long as it takes.  We have to place our trust they they are working to resolve it as fast as possible. 

@GNF @takuya_miyai @Rifad @hien_nguyen @Saki_Ishimi 

I'm curious, are all of you, who have been experiencing more frequent issues recently, using the new APAC region just recently introduced?

[takuya_miyai]

@WillowMobileSys 

No, I am not using the APAC region yet.
Maybe, I think the recent outage was in woldwide.

[Andry_Try_Apriy]

Thanks for the update, Jana. That said, this isn’t the first time we've experienced unexpected downtime without prior notice. A more proactive communication strategy like sending in-app alerts, status page notifications, or email updates as soon as an incident is detected would really help users stay informed and reduce frustration.

Real-time transparency is key, especially for teams relying on AppSheet for daily operations.

[mphoang91]

This day is the first day of using Appsheet app of my customer, and this problem made me and my customer like hell.

[hien_nguyen]

Hi @Jana_Mandic ,

I'm not sure what features you are currently testing or what exactly is happening with AppSheet, but within just one month, there have already been four major platform issues that have severely impacted millions of users worldwide. Most of these incidents occurred without any prior warning and were not explained afterward by the Google dev team.

As a no-code AppSheet developer, I’m becoming increasingly concerned about the platform’s stability. Some of my clients are starting to question the reliability of AppSheet and are considering switching to other, more stable platforms.

Best regards,

Hien Nguyen

[huynhdaibao95]

The problem has been fixed.
I hope this problem does not happen again in the future.
Thanks

[takuya_miyai]

Thank you @Jana_Mandic 

I feel it is good news that a dashboard is being planned, but as you commented, if a similar outage occurs before that dashboard is released, it will create similar confusion.

I think a workflow should be established to allow official reporting from Google as soon as possible, which can be in the same format as this community post.
Please give priority to building that workflow rather than developing a dashboard.

[griffinwilliams]

@Jana_Mandic do you know if any of these outages have been related to some unsolvable errors we've been having with one of our apps?  Or, has anyone else resolved a problem like this?  See screenshots for detail.  The warnings shown are also not consistent with actual settings.  This started Thursday, 4/17 around 3pm PT. 

I have been unable to resolve the issue in the app editor and support has, to my knowledge, treated this as a problem on my end (case #: 1-4311000038631).  All users are unable to use this app.

 

[WillowMobileSys]

Your Status column is defined as an Enum.  Do you have a Valid_If expression implemented?  Please share that - it might helpful to shoe the entire column configuration.

[griffinwilliams]

Thanks for replying, the errors have disappeared in a copy of the app that I'd shared with support and I eliminated them in the main version by switching away from a ComputedKey. 

I do still have the strange warnings in both versions of the app,  Support has ignored them so far but it seems to be a bug.  For example, there is a warning that says: "Column 'Paid' of table 'Keg Scans' is part of a computed key, but was not marked 'Required'...."  The reality is that it is NOT (and never has been) part of a computed key.  Also, it IS marked as required.

But, to answer your question.  No, there is only an initial value based on Context("view") and an editable_if condition also based only on Context("view").

[Saki_Ishimi]

 @Jana_Mandic
I am very relieved that AppSheet has recovered.
Thank you for handling this.

However, there have been frequent major incidents recently, causing significant disruption and concern for AppSheet creators and users each time. Currently, this situation leads us to question the stability of the AppSheet platform, and it is having a major impact not only on us creators but also on our customers.

Furthermore, the lack of cause analysis reports after recovery is a problem. While we greatly appreciate the implementation of the dashboard, we strongly request that you prioritize stabilizing the platform and providing prompt reports to us above all else.

[jamarshall]

I completely agree with this and hope there is a resolution. In January, I reached out to support with questions about platform stability and provided three specific incidents that occurred over several weeks. They said they had to escalate the issue. I followed up every week to request an update with the same response that it was still being investigated. The final response was after a month telling me that the incidents were over 30 days old so they couldn't be investigated further. When I reiterated that I reported them after they happened, they said they haven't happened since and other users didn't report an outage at the same time (although I have accounts with other orgs that were experiencing the exact same issue).

It is very frustrating, to say the least.

[takuya_miyai]

Hi @Jana_Mandic 

The AppSheet Database was unavailable during the time period when this problem occurred.
About Apr 21, 2025 18:13 JST

Was the AppSheet Database also failing due to the same cause as this outage?

[Jana_Mandic]

Yes, AppSheet Database would have been affected by this outage as well. 

[takuya_miyai]

Thank you @Jana_Mandic 

I was relieved that it was the same cause.

[Saddam]

great