Incidents reported on status page for MobileAction https://status.mobileaction.co/ https://d1lppblt9t2x15.cloudfront.net/logos/e7b79aa4e54d3e5b9cef15b9fe98a640.png https://status.mobileaction.co/ en https://status.mobileaction.co/ Fri, 19 Jun 2026 19:37:18 +0000 https://status.mobileaction.co/#5df5fdc236c2861e1a06334defbe21e449215ff6872e506bf5156a8e1c3c121c MobileAction Public Site recovered https://status.mobileaction.co/ Fri, 19 Jun 2026 18:01:17 +0000 https://status.mobileaction.co/#5df5fdc236c2861e1a06334defbe21e449215ff6872e506bf5156a8e1c3c121c MobileAction Public Site went down https://status.mobileaction.co/ Wed, 17 Jun 2026 07:01:32 +0000 https://status.mobileaction.co/#0fc46c1a83a3bd343b8453c921f7a1cd5903b168abbf830149cbe77b8e1204ad Backend recovered https://status.mobileaction.co/ Wed, 17 Jun 2026 06:37:18 +0000 https://status.mobileaction.co/#0fc46c1a83a3bd343b8453c921f7a1cd5903b168abbf830149cbe77b8e1204ad Backend went down https://status.mobileaction.co/ Wed, 17 Jun 2026 06:20:15 +0000 https://status.mobileaction.co/#9dbcca3cbfe943634d65497a00ff8cdf1c800dfcb41ddd0969728c254a1a3b42 Backend recovered https://status.mobileaction.co/ Wed, 17 Jun 2026 06:12:24 +0000 https://status.mobileaction.co/#9dbcca3cbfe943634d65497a00ff8cdf1c800dfcb41ddd0969728c254a1a3b42 Backend went down https://status.mobileaction.co/ Tue, 09 Jun 2026 05:20:26 +0000 https://status.mobileaction.co/#283b2f5f5b69a573a0d4564e533a5f9100ef35992dc67933b30d4d166edb1cd9 Backend recovered https://status.mobileaction.co/ Tue, 09 Jun 2026 05:06:48 +0000 https://status.mobileaction.co/#283b2f5f5b69a573a0d4564e533a5f9100ef35992dc67933b30d4d166edb1cd9 Backend went down https://status.mobileaction.co/ Mon, 25 May 2026 14:56:26 +0000 https://status.mobileaction.co/#e3ce0e41e275259f42b5dc32747e224e43bbd0a262a383d68169e572fded2cac Backend recovered https://status.mobileaction.co/ Mon, 25 May 2026 14:13:24 +0000 https://status.mobileaction.co/#e3ce0e41e275259f42b5dc32747e224e43bbd0a262a383d68169e572fded2cac Backend went down https://status.mobileaction.co/ Mon, 25 May 2026 14:09:18 +0000 https://status.mobileaction.co/#0c3cf0b0dba8f59353418028b8f5706f244a33f57e9b6761c3d939e2818247fc Backend recovered https://status.mobileaction.co/ Mon, 25 May 2026 13:49:16 +0000 https://status.mobileaction.co/#0c3cf0b0dba8f59353418028b8f5706f244a33f57e9b6761c3d939e2818247fc Backend went down https://status.mobileaction.co/ Mon, 25 May 2026 13:43:16 +0000 https://status.mobileaction.co/#acfb2b2a5b657a50f46d7cff72eb7e11b23a21b115c11c38d8aba378abae188f Backend recovered https://status.mobileaction.co/ Mon, 25 May 2026 13:12:20 +0000 https://status.mobileaction.co/#acfb2b2a5b657a50f46d7cff72eb7e11b23a21b115c11c38d8aba378abae188f Backend went down https://status.mobileaction.co/ Mon, 25 May 2026 13:07:17 +0000 https://status.mobileaction.co/#225b33eb74dc717b20b52bca1610710f5479121ace9ea19e8e930953d1bc5e00 Backend recovered https://status.mobileaction.co/ Mon, 25 May 2026 12:47:45 +0000 https://status.mobileaction.co/#225b33eb74dc717b20b52bca1610710f5479121ace9ea19e8e930953d1bc5e00 Backend went down https://status.mobileaction.co/ Mon, 25 May 2026 12:36:18 +0000 https://status.mobileaction.co/#3d7f7e970b905e4bb3c23746d066b0aa66ae1b037eb46f7e705dfe9ac955cccc Backend recovered https://status.mobileaction.co/ Mon, 25 May 2026 11:38:43 +0000 https://status.mobileaction.co/#3d7f7e970b905e4bb3c23746d066b0aa66ae1b037eb46f7e705dfe9ac955cccc Backend went down https://status.mobileaction.co/ Mon, 25 May 2026 11:10:33 +0000 https://status.mobileaction.co/#21cecf2841300ac0ff052f27b72e06a158025430ed058ef762234a7c5b9e946e Backend recovered https://status.mobileaction.co/ Mon, 25 May 2026 10:54:16 +0000 https://status.mobileaction.co/#21cecf2841300ac0ff052f27b72e06a158025430ed058ef762234a7c5b9e946e Backend went down https://status.mobileaction.co/ Wed, 29 Apr 2026 12:54:32 +0000 https://status.mobileaction.co/#e73858dff34b2aadd85d530648d7222d9e62ca9046f5710f80e23c17d3b7e567 Backend recovered https://status.mobileaction.co/ Wed, 29 Apr 2026 12:48:25 +0000 https://status.mobileaction.co/#e73858dff34b2aadd85d530648d7222d9e62ca9046f5710f80e23c17d3b7e567 Backend went down https://status.mobileaction.co/ Thu, 09 Apr 2026 11:49:30 +0000 https://status.mobileaction.co/#05180525ba93017a6759553f4181abd882f543d28fb424c5d0e59ca5f2530cdc Apple SearchAds API Status recovered https://status.mobileaction.co/ Thu, 09 Apr 2026 11:41:26 +0000 https://status.mobileaction.co/#05180525ba93017a6759553f4181abd882f543d28fb424c5d0e59ca5f2530cdc Apple SearchAds API Status went down https://status.mobileaction.co/incident/830474 Sun, 22 Feb 2026 05:53:00 -0000 https://status.mobileaction.co/incident/830474#f70f6267431ebc34af107ecac9ee6a24299720e8865ca6bf3319decd6c6f664f Maintenance completed. https://status.mobileaction.co/incident/746872 Tue, 21 Oct 2025 06:10:00 -0000 https://status.mobileaction.co/incident/746872#1bcbdbd719ac1257731c3a1550d93d81782ac5a848c865f7600b6c416c40dfc2 AWS status has returned to normal, and all services are running smoothly. https://status.mobileaction.co/incident/746872 Mon, 20 Oct 2025 10:01:00 -0000 https://status.mobileaction.co/incident/746872#a41ca1b34d6d9789f00ebf0832e38ea7b11c8247b0686526c8bec5fb6d37688c Most of the services are getting back to normal, we're waiting for the ready signal from AWS https://status.mobileaction.co/incident/746872 Mon, 20 Oct 2025 07:05:00 -0000 https://status.mobileaction.co/incident/746872#4f9ad2d7ab713b140cb6e57b272ea736945d0661ea07271e910f3075a58b1637 AWS having some difficulties about some of the services we use. Most of our production services are working well, but we don't have any control about the environment. https://health.aws.amazon.com/health/status We'll keep this page updated if we get any information. https://status.mobileaction.co/incident/599926 Wed, 11 Jun 2025 03:56:00 -0000 https://status.mobileaction.co/incident/599926#1960000ba81bdce7b2385622a5b67ab9f8dbfff42dba1752920b31a43571333f Heroku solved the problem. All our systems are back to normal. We'll continue to investigate if anything needs an update. https://status.mobileaction.co/incident/599926 Tue, 10 Jun 2025 19:12:00 -0000 https://status.mobileaction.co/incident/599926#a1795be5e6044e600c477a32fa37c64f149f96b704feb5c317cc0269cff61be4 Latest update from Heroku: We are aware of this issue and our engineering teams are continuing to work diligently around the clock to investigate the root cause and resolve. At this time, we do not have an ETA as we continue to investigate, but we assure you that resolving this issue is our top priority. For the latest updates and to subscribe for notifications, please continue to monitor our salesforce status page: https://status.salesforce.com/generalmessages/10001540 and heroku status page: https://status.heroku.com/incidents/2822 We sincerely apologize for the inconvenience and appreciate your understanding. https://status.mobileaction.co/incident/599926 Tue, 10 Jun 2025 11:42:00 -0000 https://status.mobileaction.co/incident/599926#3b5bc07dfee1ee70d37f4d82c711e9d8a97847b7e53edfb65d33001895773a28 Heroku is still working on the issue: https://status.heroku.com/incidents/2822 https://status.mobileaction.co/incident/599926 Tue, 10 Jun 2025 06:34:00 -0000 https://status.mobileaction.co/incident/599926#bf2ee8a5446e203159cbac6c35d713c7e5b50d5e8475a8d9396b29e228211838 We use Heroku for our application services and Heroku had difficulties on both its management UI and provided services. https://status.heroku.com/incidents/2822 https://status.salesforce.com/generalmessages/10001540