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

The issue has been identified.

Our services are currently experiencing degraded performance as a result of an outage on service provider Google Cloud Services(https://status.cloud.google.com/).

This incident has now been resolved.

A fix has been implemented, and we are monitoring the situation.

We are continuing to work on a fix for this issue.

We are currently experiencing a service disruption with Generative AI functionality.Our team is working to identify the root cause and implement a solution. Serenity, and Growth users may be affected.We will send an additional update as soon as possible. We apologize for the inconvenience, and thank you for your patience while we resolve the matter.

This incident has now been resolved.

A fix has been implemented, and we are monitoring the situation.

We are continuing to work on a fix for this issue.

We are currently experiencing a service disruption with Generative AI functionality. Our team is working to identify the root cause and implement a solution. Serenity, and Growth users may be affected. We will send an additional update as soon as possible. We apologize for the inconvenience, and thank you for your patience while we resolve the matter.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We would like to inform you of an upcoming scheduled maintenance on May 22nd, 8:00 PM (UTC). This maintenance will include a brief downtime period, during which Akeneo PIM will be temporarily unavailable.Please complete any critical operations involving Akeneo PIM before the maintenance begins.If you have scheduled jobs or automated tasks dependent on the system, we recommend rescheduling them accordingly.Thank you for your patience and understanding.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We would like to inform you of an upcoming scheduled maintenance on May 22nd, 6:00 AM (UTC). This maintenance will include a brief downtime period, during which Akeneo PIM will be temporarily unavailable.Please complete any critical operations involving Akeneo PIM before the maintenance begins.If you have scheduled jobs or automated tasks dependent on the system, we recommend rescheduling them accordingly.Thank you for your patience and understanding.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We would like to inform you of an upcoming scheduled maintenance on May 21st, 2:00 PM (UTC). This maintenance will include a brief downtime period, during which Akeneo PIM will be temporarily unavailable.Please complete any critical operations involving Akeneo PIM before the maintenance begins.If you have scheduled jobs or automated tasks dependent on the system, we recommend rescheduling them accordingly.Thank you for your patience and understanding.

The incident has been resolved, and the scheduled differential product synchronization has been relaunched on all impacted apps.

The incident has been mitigated by Google Cloud Platform, all apps are now accessible. We are monitoring the status of our services before closing this issue.

We are currently investigating network errors on Google Cloud Platform (GCP) impacting our Akeneo BigCommerce and Shopify Apps. All environments and customers are affected. We are working with GCP to identify potential mitigations. Further updates will be provided as they become available. We apologize for any inconvenience this may cause.

Incident is now resolved.

The incident is now resolved, as job execution times are back to normal levels. We apologize for any inconvenience caused and appreciate your patience while we worked on the resolution.

A fix has been implemented and deployed yesterday at 11pm CET. We are monitoring the wait time returning to normal for jobs. This degraded performance on jobs is currently impacting 31% of our European customers, mostly on Eastern Europe. We apologize for any inconvenience caused and appreciate your patience while we worked on the resolution.

We are currently experiencing an issue that is causing delays in execution for background jobs (internal and data cleanup processes) for SaaS PIM clients on the Europe-West3 cluster. The root cause has been identified, some mitigating adjustments have been applied, and a full fix is being developed. We will send an additional update as soon as possible.

Incident is now resolved.

Starting at 1:55 PM CET, some customers experienced errors when accessing Akeneo PIM via the UI. Our investigation determined that 1.6% of incoming requests were affected, across all regions and various use cases. We identified the root cause and deployed a fix, fully resolving the issue by 3:00 PM CET. Throughout the incident, customer data remained safe and unaffected. We apologize for any inconvenience caused and appreciate your patience while we worked on the resolution.

The Event Platform encountered a partial outage between 2:15 pm and 3:15 pm, which may have led to some loss in Events delivery to all subscribers.

Our team has been actively investigating the root cause of this issue. While the analysis is still ongoing, we have determined that the impact remains minimal, with less than 0.05% of API calls affected. Given the limited scope and low impact, we are closing this incident. However, our teams will continue to investigate to ensure a full resolution and prevent recurrence. We appreciate your patience and will provide further updates if necessary. If you experience any issues, please contact our Support team.

There was another increase in API calls returning 500 status codes on January 29th between 4.45 AM CET and 9.20 AM CET, mainly impacting instances on European clusters. We sincerely apologize for the inconvenience caused and appreciate your patience as we continue investigating the root cause of the issue.

We have identified an increase in 500 errors on API endpoints. The incident happened on January 28th between 4.40 AM and 9.30 AM. Some API calls have been returned with a 500 status code. The incident is now over, we are currently investigating the root cause of the issue.

After thorough investigation, we have determined that PIM job performance has been operating as usual, without any actual degradation. The delays initially reported were due to improvable performance indicators, which incorrectly suggested performance issues. These indicators will be reviewed and refined to prevent similar misinterpretations in the future. We apologize for any confusion caused and thank you for your patience and understanding as we worked to resolve this matter.

Users are reporting a performance degradation on PIM jobs. We can observe signs of such delays for a small portion of our customers, in all regions. We are investigating and will send an additional update as soon as possible. Diagnosis: impacted users may observe extended job execution time in comparison to expected execution time. Thank you for your understanding and your patience while we are processing this issue.

We have identified an issue affecting customers in the Europe and US regions, where jobs were stuck in a "queued" status. This incident impacted jobs created between 3:15 PM GMT and 3:34 PM GMT. As a workaround, affected jobs can be relaunched to ensure processing. We sincerely apologize for the inconvenience caused and appreciate your patience as we address this issue.

The issue affecting job execution has been fully resolved. All systems are now functioning as expected. Thank you for your patience and understanding while we worked to address this matter.

Job execution is now being resumed across all regions. We are closely monitoring the situation to ensure stability and will provide further updates if necessary. Thank you for your understanding.

The problem has been identified and a fix is being implemented. It impacts all regions, preventing jobs from being executed.

Customers are reporting jobs not being executed, on europe region. We are investigating and will provide further information as soon as we have them.

This incident has been resolved.

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

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.

The App Store should now be fully operational. We are monitoring it.

Our App Store may be unreachable. We are investigating.

This incident has been resolved.

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

We are currently investigating this issue.

Every action made on subscriptions through our API (create/update/delete/suspension/resumption) were persisted but not correctly propagated throughout our system. Examples of behaviour encountered: * Action: You created a subscription. During the incident: Events were not sent to your destination. Now: Events are correctly sent. * Action: You updated a subscription to target a different destination. During the incident: Events were still sent to the previous destination. Now: Events are sent to the configured destination. * Action: You deleted a subscription. During the incident: Events were still sent to the destination. Now: Events are not sent to the destination anymore.

The issue has been identified and a fix is being implemented.

Resolved on 2024-11-08 10:30 UTC

This incident has been resolved.

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

We are continuing to work on a fix for this issue.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

We currently are experiencing an issue with attributes not showing in the Product edit Forms. Investigations are ongoing to identify the root cause of this error. Product imports are also impacted by this incident, and some import profiles cannot be edited.

This incident has been resolved.

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

The issue has been identified and a fix is being implemented.

We can observe a raise of errors on 2% of our customer base, on save products and product models use case, when an identifier generator is applied. We are currently investigating.

This incident has been resolved.

We are continuing to monitor for any further issues.

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

We can observe some delays today for product model indexation, still in Europe region.

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

We identified one slow query as the source of the observed delay. We are currently working on the best strategy to handle this query without impacting indexation performance. The incident is impacting only Europe region.

We are currently observing some errors, especially on Europe region, on product models indexation. We are digging into these failing cases and will post an update when the root cause is identified.

This incident has been resolved.

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

The issue has been identified and a fix is currently being deployed. We will then monitor the evolution for the impacted customers.

We discovered a problem preventing indexation of product models, impacting 1% of our customers mostly on US region. We are currently investigating to find the root cause.

This incident has been resolved.

We are continuing to monitor for any further issues.

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

We are continuing to investigate this issue.

We are currently investigating this issue.

The PIM availability is back to normal since 10:15am CET. An infrastructure change caused the unavailability of the PIM UI during this incident. PIM API remained available in the meantime.

We are continuing to monitor for any further issues.

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

PIM instances are unavailable for some customers on Europe region. We are currently investigating.

This incident has been resolved.

After applying the mitigation actions, we do not observe slowness on the PIM now. We are continuing to monitor for any further issues.

We were able to observe new slowdown on the same cluster. We are taking mitigation actions again.

We are continuing to monitor for any further issues.

Slowness was observed on one cluster, representing ~1% of our customer base. Root cause is identified, mitigation actions were taken, and we are currently monitoring the situation. We'll keep updating this page when status evolves.

The issue has been identified and resolved. Customers should be able to activate and deactivate the Shared Assets feature.

We are currently experiencing an issue with Digital Asset Management - the "Share Asset" feature cannot be enabled or disabled. Our team is working to identify the root cause and implement a solution. We will send an additional update as soon as possible.

A fix has been deployed and validated. This incident is now closed.

New images added since 08/22 cannot be downloaded in the Shared Catalogs. Only "pim_catalog_image" attributes are impacted, no issue with the asset attributes. We are working on a fix and aim to get back to normal on Monday 09/02.

This incident has been resolved.

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

We are currently investigating this issue.

This incident has been solved.

A fix has been made. We are monitoring the service.

We are currently investigating this issue.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

We have identified an issue affecting scheduled jobs that haven't been launched. The root cause has been identified and a fix will be released shortly.

The incident was mitigated and performance was restored.

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

Incident start time: July 16th, 4:55 pm EST Affected Locations: US region Description: We identified a performance issue affecting the launch of UI jobs in the PIM. The issue was identified and mitigated.

The incident was mitigated and performance was restored.

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

Incident start time: July 12th, 2:50 pm EST Affected Locations: US region Description: We identified a performance issue affecting job execution or connectivity to PIM instances. We are working on a solution to mitigate this issue.

The performance issue affecting job execution times has been resolved. All job executions are back to normal.

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

We have identified the problem and are working on a fix.

We are currently investigating a performance issue affecting job execution times. Please note: - Import, export, and mass edit jobs are not impacted. - This issue is limited to customers based in the Americas.

This incident has been resolved.

The App Store is now operational.

Akeneo AppStore is currently unavailable. Our team is working on it.

This incident has been resolved.

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

The issue has been identified as related to a specific change in the table attributes. The problem appears only from product model save initiated from the UI and does not impact API save or import jobs. Our team is working on implementing a fix. We appreciate your patience and will provide further updates as soon as possible.

Between 2:50 and 3:12PM CEST, on the US region, one of our backend servers encountered a DNS resolution issue and could not handle properly the requests it received. Querying the server resulted in an HTTP 500 error. This affected about 0.6% of the web traffic, and about 0.05% of the API traffic, in this region during this period. The server was fixed, and the traffic is handled normally now.

This incident has been resolved.

We found a quick fix and been able to restore the service. Synchronizations for all regions should be back to normal. We will keep monitoring during the weekend. Next update on Tuesday 21st at 10:00 am CET.

The issue is still ongoing. We deployed several fixes to mitigate the issue and plan to get back to normal by Tuesday morning. Affected Location: Shared Catalog hosted in Europe (eu.shared-catalogs.app.akeneo.cloud) Next update on Tuesday 21st at 10:00 am CET.

Products on existing Shared Catalogs are temporarily not synchronized from the PIM (limited to Europe). The issue has been identified and a mitigation plan is already in place. The creation and deletion of new catalogs are not impacted. All other features working smoothly.

We would like to inform you that our PIM APIs in the Asia region experienced intermittent 503 errors & latency from: . Friday, May 10th 7:00 AM to 3:00 PM CEST . Monday, May 13th from 8:00 AM to 10:00 PM CEST Our team investigated the issue and implemented the necessary measures to address and resolve the problem.

This incident has been resolved.

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

The issue has been identified and a fix is being implemented.

The synchronization of products between the Onboarder and the PIM is broken.

We are currently experiencing an issue related to a certificate problem when accessing our services using Firefox. A fix is underway to resolve this issue. In the meantime, we recommend using Chrome to access our services without interruption. Thanks for your understanding and patience.

This incident has been resolved.

The fix has been deployed on Flexibility.

The fix is in progress on Flexibility. The incident is resolved on Serenity & Growth edition.

We are continuing to work on a fix for this issue.

The incident affecting our APIs is still ongoing. Our team is actively working on resolving the issue to restore full functionality as soon as possible. Shared Catalogs, Akeneo Apps for BigCommerce and Shopify cannot synchronize product data due to the unavailability of the API.

The incident is resolved on Serenity & Growth edition. Do not hesitate to refresh your browser if the propagation is not fast enough. The fix is in progress on Flexibility.

We are currently experiencing an issue related to a certificate problem when accessing our services using API. Investigations are underway. Thanks for your understanding and patience.

We experienced a partial outage of 20 minutes from 15:50 UTC to 16:10 UTC. During this time, around 4% of the whole API calls and log-in attempts in the PIM were failing. During this period the root cause has been identified and resolved.

This incident have been resolved.

The email service is now available, and we are currently monitoring the situation.

Actions have been taken, we are waiting for our provider

Our email delivery is impacted due to issues with our mail provider. We appreciate your patience as we work to resolve this.

This incident has been resolved.

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

Our teams has implemented mitigation measures to address degraded response time on our API.

We are observing degraded response time on our API. Our teams are currently running investigations.

This incident has been resolved.

A fix has been created and is being deployed in production.

We identified a misarrangement of assets at the product level for some asset collections. We are implementing a fix in order to put them back in their original order.

This incident has been resolved.

A hotfix has been implemented and deployed in production.

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.

We would like to inform you that our PIM APIs in the Europe region experienced intermittent 503 errors from 4:40 AM to 5:00 AM (GMT+2). Our team immediately investigated the issue and implemented the necessary measures to address and resolve the problem.

We would like to inform you that our PIM APIs in the Europe region experienced intermittent 503 errors from 4:40 AM to 5:00 AM (GMT+2). Our team immediately investigated the issue and implemented the necessary measures to address and resolve the problem.

This incident has been resolved.

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

The issue has been identified and a fix is being implemented.

Shared Catalogs web application is slow because of degraded performance on our internal API. We are currently investigating the issue.

We are currently experiencing intermittent issues. Some users may experience slow loading times or difficulty accessing certain pages, API or Search Grid. Our team is aware of the issue and is working to resolve it as soon as possible. We apologize for any inconvenience this may cause and appreciate your patience while we resolve the issue. Impacted region: - Australia - Asia - US

This incident has been resolved

The issue has been identified and a mitigation has been applied. Further investigation is ongoing.

We're investigating a service disruption in APAC with our Cloud provider.

This incident has been resolved.

We are continuing to monitor for any further issues.

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

New products or existing products already in Shared Catalogs are temporarily not synchronized from the PIM (limited to Europe). The issue has been identified and a mitigation plan is already in place. All other features working smoothly.