Is Ionic Services Down Right Now? Check if there is a current outage ongoing.

Starting on Jan 6th, 2024 at 17:17 UTC, Appflow builds using the iOS 2024.10 build stack began failing. An issue was identified that was preventing builds from successful completion, resulting in stuck builds timing out after an hour. The issue was resolved Jan 6th 2024 20:15 UTC.

Appflow production environment experienced an outage, which resulted in Appflow being unable to build iOS Apps. The incident occurred due to expiration of Ionic’s Certificate Authority \(CA\)—the trusted entity that ensures secure communications between the worker and controller that orchestrates iOS builds. The CA was mistakenly set to expire causing the workers to no longer communicate with the controller, leading to the disruption. The incident was resolved by generating a new certificate. To prevent such incidents in the future, Ionic’s CA rotation process is being reviewed for opportunities to increase reliability and security with additional monitoring.

This incident has been resolved.

A fix has been applied that should resolve iOS build failures and we are monitoring the results.

We are currently investigating an ongoing issue with iOS builds in Appflow.

On May 8th, the Appflow service experienced degraded performance from 3 AM EDT to 9:45 AM EDT. This was caused by an upgrade in our cloud hypervisor software specifically for Mac virtual machines running on Intel CPU Architecture. Late evening May 7th, 2024, the Appflow team rolled out an upgrade to the Mac Hypervisor software on Intel Mac machines in the Appflow Build Cloud. This change introduced a new limitation to network requests within Mac virtual machines which subsequently caused timeouts on external requests within build executions. As a result, all builds running on the affected instances would fail or timeout. On May 8th, 2024 at approximately 9:45 AM EDT, we rolled back all of the affected instances with the older version of the software to resolve the introduced problem.

This incident has been resolved.

A fix has been implemented and we currently working on identifying the root cause. We expect that new iOS builds should no longer fail. Thank you for your patience.

Beginning around 5:00 am ET, degraded performance of the iOS build runners has been identified. iOS builds may be intermittently failing. We are working on investigating the issue and should have more details available shortly. Thank you for your patience.

In the week of March 24, Ionic made some internal changes to GitHub configuration during the process of migrating to a new CI/CD setup. While deploying one service to test the changes, one of the required secrets was not correctly migrated. This was not immediately detected as the service's successful responses were heavily cached. Once the caches expired, the missing secret caused the service to respond with failure responses to permission checks. These failures were incorrectly interpreted by downstream services. This was the root cause of these services failing and resulting downtime with the Appflow dashboard. Once the required secret was migrated and caches were flushed, all service was restored. Remediation CI/CD pipeline is updated to check for missing / incorrectly migrated secrets and fail fast under this scenario. Additional changes weee made to downstream services to not misinterpret failure responses.

Around 8:00 am ET, a partial outage was identified in which iOS deployments that were deployed independently from builds were failing to deploy successfully. A fix was released around 10:00 am ET, which has since resolved any iOS deployment issues.

At 4pm on September 20, 2023, an Appflow code deployment impacted the ability to download Ionic Enterprise native plugins requiring an authorization key. The issue originated from changes in the way we handle authentication parameters. Users were encountering 403 errors during download requests. The issue was identified and resolved. No action is required from Customers at this time.

This incident has been resolved. If you are still seeing any issues please reach out to our Support team.

A fix has been implemented for this and users should be able to run iOS builds as expected. Please reach out to our support team in case if you are still seeing any issues. Thank you for your patience.

We are currently investigating issues with iOS build signing on Appflow. This may prevent users from completing new iOS builds using the MacOS builds stacks. We will post more details shortly. Thank you for your patience.

A fix has been deployed by the GitHub Team. The Appflow integration should work as expected. Please do contact support if you are seeing any issues. Thanks for your patience.

The Appflow dashboard integration with GitHub is currently impacted by a widespread Github webhooks degraded performance. Users may be unable to see new commits from GitHub during this incident. This is an issue with 3rd party service and our Appflow team is actively monitoring. Thanks for your patience!

This incident is now resolved. Please reach out to our support incase if you are still seeing any related issues.

The issue has been fixed and we were able to confirm that new iOS builds can trigger. Please reach out to our support in case if you are still seeing any issues. Thank you for your patience.

We are currently investigating iOS builds that are stuck in the queued state. This may prevent users from triggering new builds using the MacOS builds stacks. We will post further details soon. Thanks for your cooperation.

On Wednesday, March 29th, 2023, we implemented an update to our live updates service that incorporated a dependency update, inadvertently affecting the response time of requests to our manifest endpoint. This issue became apparent on Thursday morning as regular traffic increased, resulting in noticeably slower live update responses. We promptly addressed the situation by rolling back the update, pinpointing the specific change responsible for the slowdown, and successfully redeploying an improved version.

We believe this incident is resolved. Please do reach out to our support in case you are still seeing any issues. Thank you for your patience.

We believe this is resolved as of now. We are currently monitoring the results for any reoccurance. Please do reach out to our support in case you are seeing any further issues. Thanks for your patience.

Our Appflow team is currently investigating reports of live updates failures or slower live updates. We will keep you informed as soon as we have further updates. Thanks for your patience.

We believe this incident is resolved and users should be able to deploy to the Appstore as expected. If you are still seeing any issues, please contact our support. Thank you for your co-operation.

There has been an ongoing connection issue between Appflow and Apple. We believe Apple has begun accepting binary uploads again, so please redeploy your app(s) as needed. Please do reach out to our support in case you are seeing any further issues. Thanks for your patience.

We are currently investigating an issue preventing deployments to Appstore for iOS builds. Users can build as expected but may not be able to deploy from Appflow. Thanks for your patience.

This incident has been resolved by our team and users should be able deploy as expected. Please do contact our support in case you are still seeing any further issues. Thanks for your patience.

We are currently investigating an issue that is preventing Appstore deployments for iOS Appstore builds from all older build stacks other than macOS - 2022.10. We are working on a fix but in the meantime, it is recommended that you can try using the latest build stack macOS - 2022.10 as a workaround. Thank you for your patience.

This incident has been resolved. Please contact our Appflow support if you are still seeing any further issues. Thanks for your patience.

A fix has been deployed for this issue and we are currently monitoring the results. Users should be able to trigger builds as usual. Please contact our Appflow support if you are still seeing any further issues. Thank you for your patience.

We are currently investigating failures to initialize builds when using macOS 2021.06 & 2021.09 build stacks. In the short term the 2021.10 and later build stacks can be used as an alternative. We will follow up with further details soon. Thanks for your patience.

We were able to confirm that the fix applied resolves this issue. Please do reach out to our customer support in case you are seeing any further issue. Thank you for your patience.

Our engineering team has implemented a fix for this and users should be able to build for iOS in Appflow now. There might be a slight delay as the backlog clears, please do reach out to our customer support in case you are still seeing any further issues. Thank you for your patience.

We are currently investigating iOS build failures, where the builds fail to initiate when using the MacOS 2022.09 & MacOS 2021.10 build stacks. This may degrade the performance on other iOS build stacks as well. We will keep you informed as soon as we have further information on this. Thank you for your patience.

We were able to confirm that this issue is resolved by the fix deployed by our engineering team. Please reach out to our support in case you are still seeing any issues. Thanks for your patience.

Our engineering team has deployed a fix for this issue and it appears to fix this issue. We are still monitoring the fix and working on a permanent fix. Please reach out to our support team in case you are still seeing any issues. Thanks for your patience.

We are currently seeing reports of live updates failures or slower live updates. This appears to be related to degraded performance with our CDN and our engineers are currently testing a workaround. We will keep you informed on further updates, thanks for your patience.

Our engineering team deployed a fix for this and it appears to be working. Please reach out to our support in case you are still seeing any issues. Thanks for your patience.

The Ionic dashboard login is affected by a widespread Heroku outage. Users may be unable to login until the problem is resolved. We are closely watching this and will inform about further updates. Thanks for your patience! For more info see: https://status.heroku.com/incidents/2453

Issues affecting the Ionic Zendesk instance appear to be resolved. Please do contact Ionic support in case you are seeing any issue with tickets or ticket responses. Thanks for your patience!

We have identified the issue and working towards resolving it. You can directly email support@ionic.io in the interim to create new tickets, or inquire on your existing tickets. We will keep you posted as soon as we have further information. Thank you for your patience.

The Ionic ticketing system and Knowledge Base are affected due to an issue with our Zendesk instance. Users may be unable to access the ticketing system or KB until the problem is resolved. We anticipate some delays when the service is restored to clear any backlog. Thanks for your patience!

This issue has been marked as resolved by Cocoapods team. Please do contact our support if you are still seeing any further issues. Thanks for your patience.

Cocoapods team has deployed a fix and the iOS builds are building fine. We will monitor the status for any reoccurrences but consider this resolved. Thanks again for your patience during this incident. If you are still seeing any further issues, please do contact our Ionic Support.

We are currently seeing reports of iOS build failures due to Unreliable CDN issue with Cocoapods. Users may have some difficulty building for iOS until the problem is resolved. We anticipate some delays when the service is restored to clear any backlog. Thanks for your patience! see: https://status.cocoapods.org/#

A fix has be released for this and the incident has been resolved now. Please contact our customer support if you are still seeing any issues.

A fix has been implemented for this issue and we are monitoring the results. Thanks for your patience.

We are currently investigating reports of degraded performance with iOS package builds which might cause delays or failures when triggering new iOS builds. We will update as soon as we have further information. Thanks for your patience.

This is now resolved by the Github team. The Github integration should work as expected. Please do contact support if you are seeing any issues. Thanks for your patience.

Appflow dashboard integration with GitHub is currently impacted by a widespread Github degraded performance. Users maybe unable to see new commits from Github during this incident. More info can be found here: https://www.githubstatus.com/ . Thanks for your patience!

This is now resolved by the Github team. The Github integration should work as expected. Please do contact support if you are seeing any issues. Thanks for your patience.

The Appflow dashboard integration with GitHub is currently impacted by a widespread Github degraded performance. Users maybe unable to see new commits from Github during this incident. We will keep you informed as soon as we have further information. Thanks for your patience!

This issue has been marked as resolved by Heroku team. Please do contact our support if you are still seeing any further issues. Thanks for your patience.

Impacted components have been restored by Heroku team and the Ionic dashboard is operational now. We will monitor the status for any reoccurrences but consider this resolved. Thanks again for your patience during this incident.

Ionic dashboard is affected by an Heroku outage which prevents users from logging into the Ionic Dashboard. Users already logged into the dashboard should have no issues. We will continue to monitor the status. More info can be found here: https://status.heroku.com/

Our Appflow team has deployed a fix for this and this issue should be resolved now. Please do contact Ionic support if you are seeing any further issues. Thanks for your patience.

The Appflow dashboard integration with Azure DevOps is currently affected by a widespread Microsoft API service outage. Users maybe unable to integrate with Azure DevOps during this incident. We will keep you informed as soon as we have further information. Thanks for your patience!

_Appflow was completely unavailable for approximately two hours between 12:11 UTC \(6:11am CT\) and 14:18 UTC \(8:18am CT\). The outage occurred when a Redis cache ran out of memory due to a task queue growing uncontrollably. We’ve added additional monitoring of the specific queue and fixed the bug causing the large number of tasks to get enqueued._

The incident has been resolved. Please do contact Ionic support if you are seeing any further issues. Thanks for your patience.

A fix has been implemented and the Appflow Dashboard service is now recovering. We will monitor the situation to ensure the problems are resolved. Thanks for your patience.

We are currently investigating an issue that is resulting in 504 errors for the Ionic Dashboard. This may result in users being unable to access the Dashboard or their applications.

The incident has been resolved by the Ionic team. We will monitor the status for any reoccurrences but consider this resolved. Thanks again for your patience during this incident.

Users are reporting that they are unable to download packages from registry.ionicframework.com such as packages from @ionic-enterprise. This issue is currently being investigated.

Appflow was affected by an AWS outage which prevented users from accessing the Appflow Dashboard, run new builds, and access their ionic git repos. https://status.aws.amazon.com/ Additionally, NPM was also experiencing a problem that prevented users from installing packages. https://status.npmjs.org/incidents/7klw65jd5f5r?u=7tz3rv8j6slz These incident have been resolved by the AWS and NPM teams. We will monitor the status for any reoccurrences but consider this resolved. Thanks again for your patience during this incident.

The incident has been resolved by the AWS team. No impact to Appflow build services. We will monitor the status for any reoccurrences but consider this resolved. Thanks again for your patience during this incident.

A fix has been implemented by the AWS team We'll continue monitoring until a formal resolution is called by the AWS team. Thanks for your patience!

The Appflow build system is affected by a widespread AWS outage. Users may be unable to build in Appflow until the problem is resolved. We anticipate some delays when the service is restored to clear any backlog. Thanks for your patience! see: https://status.aws.amazon.com/

The incident has been resolved by npm. All Ionic build services are functional. We will monitor the status for any reoccurrences but consider this resolved. Thanks again for your patience during this incident.

Issues affecting the Appflow bulids appear to be fixed by the npm team. We'll continue monitoring until a formal resolution is called by the npm team. Thanks for your patience!

The Appflow build system is affected by a widespread npm outage. Users may be unable to build in Appflow until the problem is resolved. We anticipate some delays when the service is restored to clear any backlog. Thanks for your patience! see: https://status.npmjs.org/

The incident has been resolved now. Please contact our customer support if you are still seeing any issues.

A fix has been deployed and we are currently monitoring it. If you are still facing any issues please do contact customer support. Thank you for your patience.

We are currently investigating failures to initialize builds using the Linux build stacks. We'll post an update as soon as we have new information to share. Thanks for your patience.

The incident has been resolved now. Please contact our customer support if you are still seeing any issues.

A fix has been deployed and we are currently monitoring it. If you are still facing any issues please do contact customer support. Thank you for your patience.

The issue has been identified and a fix is being implemented. Thanks for your patience.

We are investigating reports of iOS builds failure. We'll post an update as soon as we have new information to share. Thanks for your patience.

This incident is now resolved. If you are seeing any issues, please contact customer support.

A fix has been deployed and we are currently monitoring it. If you are still facing any issues please do contact customer support. Thank you for your patience.

We are investigating reports of failures during the compile step when creating a new app using the wizard on the appflow dashboard. We'll post an update as soon as we have new information to share. Thanks for your patience.

_One ECS container type recently began utilizing more memory which caused at least one of the EC2 instances to get into an invalid state. We have changed the configuration for the container type._

This incident has been resolved. Thanks for your patience, If you are seeing an issue please contact support.

We've released a preliminary fix which appears to be effective. Login should now behave as expected. We will continue to monitor for a recurrence.

We are currently investigating reports of login failing to properly display the Appflow dashboard. We'll post an update as soon as we have new information to share. Thanks for your patience.

All Ionic Support services have been functioning reliably for the last 2 hours. We will monitor the vendor status for a reoccurrence but consider this resolved. Thanks again for your patience during this incident.

Issues affecting the Ionic Zendesk instance appear to be resolved. We'll continue monitoring until a formal resolution is called by the vendor. Thanks for your patience!

We are continuing to investigate this issue.

The Ionic ticketing system and Knowledge Base are affected by a widespread Zendesk outage. Users may be unable to access the ticketing system or KB until the problem is resolved. There are currently no signs that ticket creation or delivery has been affected. We anticipate some delays when the service is restored to clear any backlog. Thanks for your patience! see: https://twitter.com/zendeskops

This incident has been resolved. Thanks for your patience.

The fix appears to have been effective. We will continue to monitor performance on all iOS build stacks.

We've identified the issue and are evaluating the solution.

We are continuing to investigate this issue.

We are investigating reports of failure to initialize and extremely slow performance affecting iOS builds across all stacks.

This issue is now fully resolved - please contact us if you have any further questions or issues.

A fix has been implemented and we are monitoring the results.

We've identified the underlying cause and are investigating solutions. iOS 2020.11 builds are now running after long delays while initializing.

We are currently investigating failures to initialize builds using the 2020.11 build stack. In the short term the 2020.09 build stack can be used as an alternative.

This incident has been resolved.

We're investigating reports of Appflow iOS builds failing with the error: ERROR: Job failed (system failure): The name 'runner-c93ac604-project-0-concurrent-0' already exists.

The Deploy usage counts have been fixed. This incident is now fully resolved - please contact us if you have any further questions or issues. Thank you for your patience!

Appflow builds have been working since yesterday as per the previous note. Our developers have also implemented a fix for updating Deploy counts and usage, which is slowly rolling out.

Customers are able to build in Appflow again. However, there is an issue with Deploy counts that is currently manifesting on the Dashboard (showing "0") that we are working on a fix for. Until that issue has been resolved, we will keep this incident open. It may be some time before the next update. If you have any questions in the meantime, please contact the Ionic Support team.

The Appflow Dashboard service is now recovering. We are continuing to monitor the situation to ensure the problems are resolved.

Our engineers have been working on identifying the root cause of the backend issues. Investigation is ongoing.

Our engineers are investigating an issue on our backend resulting in 504 errors on some network calls. This may result in users being unable to access the Appflow Dashboard or their applications.

The iOS build issues should now be resolved and builds should be functioning normally again. Note that due to a backlog of builds, some builds may take some time to queue up. Please contact us if you have any further issues.

We are continuing to monitor for any further issues.

The problem has been identified as a bad build server. The server has been restarted and builds are normalizing again. We are monitoring for any other issues, but should have a resolution shortly.

Our engineers are investigating potential iOS build errors with our Package build service. Some builds are still succeeding, while others are failing.

Our vendor has resolved our server issues and iOS builds should be working normally as of about 10:00am Central Time (USA); we waited to post a resolution until we saw improvements across the board. Thank you for your patience and please contact us if you have any more issues.

Our team has isolated the iOS build issue to a third-party server and attempted to mitigate the problem. We expect to see builds recovering and working again soon.

We've received reports that customers are run iOS Package builds in Appflow. Our team is investigating.

This incident has been resolved.

We've deployed a fix that should help to mitigate this issue. Be aware that there may still be intermittent problems for as long as AWS has an open issue. We'll continue to monitor the issue for any changes.

This issue appears to be related to trouble on AWS see: https://status.aws.amazon.com/

We are investigating failures to store and retrieve native build artifacts. This can results in failed builds or errors when attempting to download a build from the dashboard.

iOS build services have been restored.

We're investigating reports of Appflow iOS builds failing with the error: "ERROR: Preparation failed: The name 'runner-dc549c99-project-0-concurrent-0' already exists."

The Appflow team has identified the issue and deployed a fix.

We're investigating reports of Appflow iOS builds failing with the error: "ERROR: Preparation failed: The name 'runner-dc549c99-project-0-concurrent-0' already exists."

The timeout error that was occurring for Ionic Deploy and Android Package builds should now be resolved - please try your builds again and contact us using the links below if you continue having issues. Thank you for your patience!

Our developers have implemented a fix for the build issue and our runners should be working normally again. We are monitoring the situation to ensure the issue has been resolved.

We are continuing to investigate the issue with Deploy and Package builds seeing increased failure rates. This outage does *not* affect iOS Package builds - it is limited to Deploy builds and Android Package builds.

Our developers are investigating an increased number of pending and failed Ionic Appflow builds for some customers. This affects Ionic Deploy and Ionic Package.

The issue is resolved.

A fix has been implemented. Engineers will continue to monitor the service.

We are currently investigating 500 errors originating from the Appflow dashboard. Our engineers are currently working on a resolution.

This incident has been resolved.

We've identified the issue and builds are now progressing normally. We will continue to monitor the iOS builds service.

We are currently investigating reports of stalled ios builds in appflow. If you have builds queued please wait for a resolutions before triggering any additional builds. Android builds are unaffected but may be delayed in accounts that have reached their concurrent build limit.

Our team responded to and resolved an issue where the Appflow Dashboard was not allowing customers to login. The incident was fully resolved around 6:30am Central Time (USA). We are monitoring the situation for any further developments. Thank you for your patience and we apologize for the inconvenience.

We have received notice that the missing dependencies that were causing Android build errors should now be restored. Please try your Android builds again and reach out if you continue to have issues.

We have received notice that the missing dependencies that were causing Android build errors should now be restored. Please try your Android builds again and reach out if you continue to have issues. We are continuing to monitor the situation until we receive verification of successful dependency restoration and build success from our customers.

Our developers have implemented a temporary fix that should allow Android builds to complete successfully while a proper fix is implemented by Google. Please let us know if the issue continues.

Note: This outage is also affecting Creator Package builds.

Missing dependencies are in the process of being restored by Google and the dependency managers. It may still take some time before all dependencies are restored, so we are continuing to monitor the situation.

Over the weekend, we began receiving reports of Android build failures in Ionic Appflow. We believe the problem relates to the removal of some Android dependencies used for various Android services, plugins, etc. by Google. This issue is not specific to Ionic Appflow or any Ionic service, but it is preventing successful Android Package builds. Note: We have seen a subset of customers who were able to workaround this issue by upgrading their version of cordova-android to v7.1.4. We recommend customers try upgrading cordova-android to see if that resolves their build problem. We are monitoring the situation and investigating potential workarounds while awaiting any official updates.

Our developers were able to successfully resolve the issue and the errors should no longer be occurring. If you are still seeing errors, please log out and log back into your Dashboard. Thank you for your patience!

We have received reports of an issue with Ionic Deploy where users are seeing errors in the Dashboard when assigning or rolling back builds. Our developers have just implemented a fix, but we are monitoring the situation.

In addition to our failover, AWS has now resolved the incident that was causing 500 errors for some customer Deploy builds. Thank you for your patience while we awaited a resolution.

We've temporarily switched to a different Elastic Container Registry region. Builds now appear to be running normally. Engineers will continue to monitor the situation.

We are investigating an issue that appears to be related to degraded performance of the Amazon Elastic Container Registry service. Engineers are monitoring AWS status and looking into potential workarounds.

Our developers have resolved the issue with Deploy builds in Ionic Pro. Thank you for your patience and understanding. For more information about this incident, please see this article: https://bit.ly/2qO6k1o

Our developers are continuing to work on fixing Deploy builds. Please stay tuned for further information.

We've received reports from customers of their commits not showing up in the Ionic Pro dashboard. This means Deploy builds cannot be run at the moment. Our developers are currently working on the issue and we hope to have a resolution shortly.