Is Akeneo down?

Since 14:17 UTC, some Serenity Edition customers have been unable to access a set of features from the PIM's UI and API, including collaboration workflows, proposals, shared assets, asset versioning, Agentic Ziggy, channel permissions, and product restorations. No data has been lost as a result of this issue. This issue affected approximately 10% of customer instances running Serenity Edition, across all regions. The root cause has been identified, and a fix is currently being rolled out to all impacted instances. We will provide an update within 60 minutes.

All customer configurations have been fixed, and we are now monitoring the situation. We will provide an update within 30 minutes

The issue is fully resolved, and all PIM features are available again. Thank you for your patience and understanding

We have had several reports of wrong or misleading error reports. This makes it harder for you to deep dive and correct marketplace synchronisation failures. We are seeing both false positive and false negative reports. We apologise for the inconvenience this may be causing you, but also to let you know - we are on the case! Since this is not an outage, updates may be slower than normal. But we will be doing our very best to get this experience working fully as fast as possible.

# 📢 Product Update: Enhanced Reporting, Better Error Resolution & Smoother Publishing We have rolled out key updates to your reporting and error-handling experience, designed to give you better visibility into your product data, eliminate export friction, and resolve channel publishing errors automatically. * **New 'All Messages' Tab:** Easily view item-level reporting messages in one unified place without having to click through separate category or catalog views first. Filter by severity (*Error*, *Warning*, *Info*) to quickly identify what needs your attention. * **Upgraded Product Filtering:** Finding specific product issues is now faster and more intuitive: * Filters now show **only** products present in the active report, rather than your entire catalog. * Search using human-readable product labels instead of internal IDs. * Filter updates apply instantly, saving you time during audits. ### 🛠️ Automatic Error Handling & Publishing Fixes * **Amazon Vendor Error Auto-Recovery (Code 101202):** Previously, invalid cost price errors could block entire product submissions from reaching Amazon Vendor. The system now automatically recovers by resubmitting valid product attributes while isolating the offending cost attribute for your review. Your products publish successfully without getting stuck. * **Expanded eBay Multi-Value Limits:** We’ve expanded the multi-value attribute limit from 5 to 30 values, aligning directly with eBay’s platform capabilities. This eliminates publish-time export failures for listings with extensive item specifications.

This incident has been resolved.

Some users in the US region may experience delays affecting job execution and triggered rule execution. We are currently investigating the issue and have applied an initial mitigation. Our team is actively monitoring the situation.

We have identified the infrastructure issue causing delays in job and rule execution. A mitigation has been applied, and performance is steadily returning to normal. We are continuing to monitor the recovery and will provide another update in 30 minutes.

Our changes made to restore performance to optimal levels are having the intended effect, and service is back to normal. We sincerely apologize for the disruption, and thank you for your patience while we worked on this issue.

Some users in the US region may experience delays affecting job execution and triggered rule execution. We are currently investigating the issue and have applied an initial mitigation. Our team is actively monitoring the situation.

We are currently investigating an issue affecting Shopify App synchronizations for some customers. Due to temporary errors from our cloud infrastructure providers, some synchronizations may fail or stop unexpectedly. Our team is actively investigating the issue and monitoring the situation. We will provide another update as soon as we have more information. We apologize for the inconvenience and appreciate your patience.

GCP have confirmed this is an internal issue and raised to the Google engineering teams for support. Pending further updates. If you are impacted by this issue please raise a support ticket so that we can collate and provide updates directly as well.

Google engineering teams released a fix, and we have confirmed that the issue is mitigated. We will leave this incident as open/monitoring for 24 hours before closing it if we have no new alerts.

We have unfortunately seen intermittent failures corresponding to the same issue. We are re-engaging with Google support and will continue to monitor and escalate as required. Once more we extend our apologies to you, our customers.

We are aware that some customers are still experiencing failures in shopify synchronisation. We are awaiting additional support from Google, while reviewing all options available to us to mitigate. If you are impacted by this issue please raise a support ticket. We apologize for the inconvenience and appreciate your continued patience.

Overnight Google have increased both capacity and memory allocation to our datastore fleets to reduce the impact to our Shopify customers. We are not aware of repeated instances of incidents since then but will continue monitoring. If you are impacted please reach out and raise a support ticket. Google will also share with us a full root cause analysis once the incident is declared closed.

Working closely with Google over the weekend, they isolated the root cause and restored capacity. The incident is now resolved. Given the impact on you and your customers, we are prioritising the steps needed to prevent a recurrence. Our first actions will be to produce a full postmortem and to work with Google to incorporate their own root cause analysis. We don't yet have an ETA for the follow-up actions, and will share more as soon as we do. If you have any questions, please raise a new ticket, update an existing one, or reach out to your CSM. We sincerely apologise for the disruption this caused you and your customers, and thank you for your patience.