Adalo Outage History

Type: Incident Duration: 1 hour and 7 minutes Affected Components: Adalo Subdomains, Custom Domains Jun 18, 21:00:00 GMT+0 - Investigating - We're aware that published apps are currently not loading, and our team is actively investigating. We'll post another update as soon as we know more. We're sorry for the disruption and thank you for your patience. Jun 18, 22:06:57 GMT+0 - Resolved - PWAs are now loading normally again. We appreciate your patience while our team investigated and addressed the issue.

This incident has been resolved. The App Previewer and Published Apps are back to normal. Thank you for your patience.

Type: Incident Duration: 2 hours Affected Components: iOS Apr 14, 21:27:13 GMT+0 - Investigating - We are currently investigating an error with our iOS build servers causing higher than normal rates of failure. We will update as we get more information. Apr 14, 23:00:43 GMT+0 - Identified - iOS builds are currently failing due to third-party dependency that published a breaking change. We're working on a fix now and will update once it's deployed. Apr 14, 23:26:48 GMT+0 - Resolved - This incident has been resolved.

Type: Incident Duration: 1 hour and 38 minutes Affected Components: App Previewer, App Editing Backend, App Editor Apr 9, 16:20:58 GMT+0 - Investigating - Some users are currently unable to load apps in the Builder. Our team is actively working to resolve this and will keep you updated on progress. Apr 9, 17:59:20 GMT+0 - Resolved - We’ve resolved the issue that was preventing some users from loading apps in the Builder. Everything should now be working normally. Thanks for your patience while we worked on this.

Type: Incident Duration: 1 hour and 1 minute Affected Components: Android Apr 6, 14:36:04 GMT+0 - Investigating - We are currently experiencing an outage, which is causing Android builds to fail. Our team is working to resolve it as soon as possible. We apologize for the inconvenience and will provide updates as they become available. Apr 6, 15:36:38 GMT+0 - Resolved - We are happy to announce that the issue with our build servers has been resolved, and builds are now succeeding for Android! We apologize for the inconvenience this may have caused and thank you for your patience while we worked to resolve it.

Type: Maintenance Duration: 1 hour Affected Components: iOS, Adalo Subdomains, Collections API, App Analytics, Collections, Maps, Stripe, App Editing Backend, App Editor, App Previewer, Notifications, Custom Domains, Android Feb 5, 05:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance to update the Adalo infrastructure. Users may see intermittent connectivity issues during this period. Feb 5, 05:00:01 GMT+0 - Identified - Maintenance is now in progress Feb 5, 06:00:00 GMT+0 - Completed - Maintenance has completed successfully

Type: Incident Duration: 6 hours and 39 minutes Affected Components: Adalo Subdomains, , iOS, Collections, Maps, Stripe, , Collections API, App Editing Backend, App Editor, App Previewer, Notifications, Custom Domains, , Android, , App Editing → Published Apps → Web Publishing → Publishing → Jan 19, 01:00:00 GMT+0 - Identified - Infrastructure providers have identified the issue and fixes have been implemented. Node replication is taking time to kick off and restore service to Adalo. Engineering team is working to expedite as fast as possible. Jan 19, 07:37:44 GMT+0 - Monitoring - This incident has been resolved. Jan 19, 07:38:49 GMT+0 - Resolved - This incident has been resolved.

Type: Incident Duration: 1 day, 7 hours and 40 minutes Affected Components: App Analytics, Collections, , Collections API, Published Apps → Nov 11, 19:00:00 GMT+0 - Investigating - We’re currently investigating elevated timeout errors impacting some Adalo apps. Makers may experience slow load times, intermittent data errors (such as user property updates failing), or difficulty accessing certain parts of their apps. Nov 13, 02:39:34 GMT+0 - Resolved - This incident has been resolved. Nov 12, 05:03:34 GMT+0 - Monitoring - Our engineering team identified the root cause as excessive load on a specific database instance and have since rebalanced resources and stabilized performance. We’re continuing to monitor system health closely and have begun implementing measures to prevent similar issues in the future. These include better traffic distribution and additional monitoring for early warning signals.