Adalo - Adalo Published Apps Down Due To Amazon Outage – 故障详情

We’re currently seeing build and platform performance issues related to an ongoing LaunchDarkly outage, which is still being impacted by the wider AWS service interruption. While our build servers are operational again, processes that rely on LaunchDarkly are still affected, resulting in stuck or failed builds.

We’re monitoring LaunchDarkly’s recovery closely and will update here as soon as the upstream issue is resolved.

Additionally, please note that Apple recently introduced a new Developer Agreement that may cause builds to fail until it’s accepted. If you encounter build errors, log in to your Apple Developer account and accept the updated agreement before retrying.

We’ll continue to post updates here as more information becomes available.

We are currently investigating degraded performance with iOS builds to see if it is related to the AWS outage.

The team will update here as soon as we have more information.

The recent service interruption caused by the AWS outage looks to be fully resolved, and Adalo is back up and running as expected.

If you’re still noticing any unusual behavior, try refreshing your app or pushing a new build and reach out to support if you encounter any additional issues.

Adalo, like thousands of other companies around the globe relies on AWS for all or part of IT infrastructure.

Fortunately Adalo Makers are not subject to a total outage, however apps can be configured in many different ways and because of this some apps are unavoidably intertwined with AWS services.

The AWS outage has been ongoing for approximately 8 hours now, and they have indicated a mitigating fix has been identified yet state that many customers continue to be affected. We expect this to be resolved shortly and will continue actively monitoring the issue.

Thank you for your patience!

We’re currently experiencing a service interruption related to a wider AWS outage that’s affecting multiple platforms, including Adalo. Our team is closely monitoring the situation and will update here as soon as AWS resolves the issue.