Adalo - Notice history

Collections API - Operational

99.46% uptime
Aug 2022 · 99.78%Sep · 98.59%Oct · 100.0%
Aug 2022
Sep 2022
Oct 2022

App Analytics - Operational

99.91% uptime
Aug 2022 · 99.72%Sep · 100.0%Oct · 100.0%
Aug 2022
Sep 2022
Oct 2022

Notice history

View current status

Oct 2022

Android builds are failing due to dependency outage
ResolvedMajor outage16 hours 39 minutes
  • ResolvedUTC

    Most Android builds are succeeding. We will continue investigating a small number of builds impacted by component dependencies.

  • UpdateUTC

    Most Android builds are now succeeding. There are still known issues with the Adalo Audio Player Component that prevents builds from succeeding. We are looking into a solution.

  • MonitoringUTC

    Most builds are now working. We are still monitoring the situation.

  • UpdateUTC

    Even though some of the problems have been mitigated, there are still some issues with our dependencies and Android builds might still fail. See https://status.gradle.com/incidents/9740r6bzx438

  • UpdateUTC

    We are still trying to mitigate the unavailability of a dependency. We will give an update once we have more information.

  • IdentifiedUTC

    We have identified the issue and are testing a fix

  • InvestigatingUTC

    We are currently investigating this incident.

Sep 2022

App databases are not responding
ResolvedMajor outage9 hours 23 minutes
  • ResolvedUTC

    On September 18 at 1:39 AM EST, Adalo began experiencing a service interruption that impacted access to your database — in both the Adalo editor inside of your database collections and in your end-apps when trying to view or create new data. At 11:15 AM EST on September 18, access to all your databases was restored.

    We understand this is extremely frustrating, not only for you, as app creators, but also for the users of your apps & for that, we are sorry. Unfortunately, this was an upstream dependency where our hands were tied in bringing this interruption to a quick resolution.

    Here’s what happened. At 1:39 AM EST our database provider AWS started a minor upgrade on our databases. This should have only been a momentary upgrade but an unexpected error made the databases restart itself on a continuous loop — as there was an issue on their end with that process. And this is what caused the issue.

    At the beginning of the interruption, our on-call engineers were paged and immediately tried the options that we had on our end to make the databases accessible, but ultimately realized that only AWS could stop the loop causing the issue. We immediately contacted our support reps at AWS to bring our databases online. At the same time, we began a manual restore of the database to bring everything back online. That process is a lengthy process only used in case of emergency and ultimately that’s what our engineers had to do in order to resolve the issue.

    Again, we apologize for this inconvenience & our team will be doing a retrospective to prevent this from happening again in the future.

    As always, thank you so much for building with no-code and creating with Adalo.

  • UpdateUTC

    Our engineers continue to monitor the auto-upgrade of databases through AWS, which is what took them offline. They ultimately are waiting on AWS to bring our databases online at this time — either through the ending of this upgrade cycle or AWS manually turning off the upgrade.

    All of your data previous to this outage will be restored fully, with the exception of any data that was created between 11:26pm EST Sep. 17th and 1:39am EST Sep 18th. It's simply not accessible at this time.

  • IdentifiedUTC

    An auto update of our database instances is keeping them offline. The databases are restarting, but we expect them to be offline until all of the databases reboot.

  • InvestigatingUTC

    We are currently investigating this incident.

Custom actions with JSON body are failing with 422 error
ResolvedPartial outage2 hours 37 minutes
  • ResolvedUTC

    This incident has been resolved.

    If you still see your custom actions breaking, please Submit a Support Ticket so that we're able to look into it asap.

  • IdentifiedUTC

    We are currently investigating an error with Custom Actions that have a JSON body where actions are failing with Error 422. As per our current knowledge, External Collections and Custom Actions without JSON bodies are working as expected.

    We will update as we get more information.

Editor not accessible
ResolvedMajor outage22 minutes
  • ResolvedUTC

    We have resolved this incident.

    If you see any ongoing issues that appear related to this, please submit a support ticket and we will investigate further.

  • IdentifiedUTC

    The team has Identified and outage with the editor and we are working on a fix for this incident.

Aug 2022

Previous

Aug 2022 to Oct 2022

Next