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/ Tue, 18 Nov 2025 14:43:01 +0000 https://status.mobileaction.co/#0a230aff06d16cfbd1299182958f420a2bfdcceb295f2ab438ae3e346090d256 Backend recovered https://status.mobileaction.co/ Tue, 18 Nov 2025 14:43:01 +0000 https://status.mobileaction.co/#0a230aff06d16cfbd1299182958f420a2bfdcceb295f2ab438ae3e346090d256 Backend recovered https://status.mobileaction.co/ Tue, 18 Nov 2025 14:37:30 +0000 https://status.mobileaction.co/#0a230aff06d16cfbd1299182958f420a2bfdcceb295f2ab438ae3e346090d256 Backend went down https://status.mobileaction.co/ Tue, 18 Nov 2025 14:37:30 +0000 https://status.mobileaction.co/#0a230aff06d16cfbd1299182958f420a2bfdcceb295f2ab438ae3e346090d256 Backend went down https://status.mobileaction.co/ Tue, 18 Nov 2025 12:30:10 +0000 https://status.mobileaction.co/#52a58fecf1c9c5cb89ba2a62a9e66e2e31ff1823f269f98e11a461877a4bc53c MobileAction Dashboard recovered https://status.mobileaction.co/ Tue, 18 Nov 2025 12:03:33 +0000 https://status.mobileaction.co/#f2294b5e7286f4e95f6a67ab6648190e4bbea243111fe805f3319b218ccedbfd MobileAction Public Site recovered https://status.mobileaction.co/ Tue, 18 Nov 2025 11:42:27 +0000 https://status.mobileaction.co/#f2294b5e7286f4e95f6a67ab6648190e4bbea243111fe805f3319b218ccedbfd MobileAction Public Site went down https://status.mobileaction.co/ Tue, 18 Nov 2025 11:41:57 +0000 https://status.mobileaction.co/#52a58fecf1c9c5cb89ba2a62a9e66e2e31ff1823f269f98e11a461877a4bc53c MobileAction Dashboard went down https://status.mobileaction.co/ Mon, 03 Nov 2025 18:40:44 +0000 https://status.mobileaction.co/#35e2ba0d6750d237cdf118e5b4e740b7c94b24f51e0a0df2bcac0e279d3dc848 Backend recovered https://status.mobileaction.co/ Mon, 03 Nov 2025 18:40:44 +0000 https://status.mobileaction.co/#35e2ba0d6750d237cdf118e5b4e740b7c94b24f51e0a0df2bcac0e279d3dc848 Backend recovered https://status.mobileaction.co/ Mon, 03 Nov 2025 18:32:09 +0000 https://status.mobileaction.co/#35e2ba0d6750d237cdf118e5b4e740b7c94b24f51e0a0df2bcac0e279d3dc848 Backend went down https://status.mobileaction.co/ Mon, 03 Nov 2025 18:32:09 +0000 https://status.mobileaction.co/#35e2ba0d6750d237cdf118e5b4e740b7c94b24f51e0a0df2bcac0e279d3dc848 Backend went down https://status.mobileaction.co/ Fri, 31 Oct 2025 14:19:28 +0000 https://status.mobileaction.co/#fd2d7903a0c6cbb252732ed52b046630ec3834fa5f0812ad24e4709605c5c1e5 Backend recovered https://status.mobileaction.co/ Fri, 31 Oct 2025 14:19:28 +0000 https://status.mobileaction.co/#fd2d7903a0c6cbb252732ed52b046630ec3834fa5f0812ad24e4709605c5c1e5 Backend recovered https://status.mobileaction.co/ Fri, 31 Oct 2025 14:11:30 +0000 https://status.mobileaction.co/#fd2d7903a0c6cbb252732ed52b046630ec3834fa5f0812ad24e4709605c5c1e5 Backend went down https://status.mobileaction.co/ Fri, 31 Oct 2025 14:11:30 +0000 https://status.mobileaction.co/#fd2d7903a0c6cbb252732ed52b046630ec3834fa5f0812ad24e4709605c5c1e5 Backend went down 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 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 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 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 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/ Mon, 20 Oct 2025 17:56:30 +0000 https://status.mobileaction.co/#01bd3ed7ee26067c2cd68bd928f8832ccff059d9143232ad91b9c10c0b551af5 SearchAds Dashboard recovered https://status.mobileaction.co/ Mon, 20 Oct 2025 16:17:07 +0000 https://status.mobileaction.co/#01bd3ed7ee26067c2cd68bd928f8832ccff059d9143232ad91b9c10c0b551af5 SearchAds Dashboard went down https://status.mobileaction.co/ Mon, 20 Oct 2025 16:10:57 +0000 https://status.mobileaction.co/#e0b6eac372da8bee832e2e19e3e6bc1d9efbe647262683764b92bdc9600972fb SearchAds Dashboard recovered https://status.mobileaction.co/ Mon, 20 Oct 2025 15:38:42 +0000 https://status.mobileaction.co/#e0b6eac372da8bee832e2e19e3e6bc1d9efbe647262683764b92bdc9600972fb SearchAds Dashboard went down 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 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 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 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 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/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/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/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/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/ Sun, 05 Oct 2025 07:15:47 +0000 https://status.mobileaction.co/#e2ca147dd2a4e41e724151d0be470278458a30a4a67059f7a8a114bd6fbf3c02 Apple SearchAds API Status recovered https://status.mobileaction.co/ Sun, 05 Oct 2025 06:15:46 +0000 https://status.mobileaction.co/#e2ca147dd2a4e41e724151d0be470278458a30a4a67059f7a8a114bd6fbf3c02 Apple SearchAds API Status went down 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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