- Detected by Pingoru
- Jun 25, 2026, 12:52 PM UTC
- Resolved
- Jun 26, 2026, 08:37 AM UTC
- Duration
- 19h 44m
Affected: Activation
Timeline · 3 updates
-
investigating Jun 25, 2026, 12:52 PM UTC
⚒️ Degraded Activation experience - full service to be restored by 18:00 UTC
-
investigating Jun 25, 2026, 08:26 PM UTC
We have released substantial fixes to improve database read performance. We will continue to monitor proactively, before closing the incident.
-
resolved Jun 26, 2026, 08:37 AM UTC
We've completed the changes needed to restore performance to normal levels. While we'll continue active monitoring, we're confident the issue is resolved and are now closing this incident. Thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Jun 23, 2026, 12:50 PM UTC
- Resolved
- Jun 23, 2026, 02:14 PM UTC
- Duration
- 1h 24m
Affected: UIREST APIGraphQL API
Timeline · 6 updates
-
investigating Jun 23, 2026, 12:50 PM UTC
We are currently experiencing a major outage causing PIM instances to be completely inaccessible for a portion of our customers since 12:15 UTC. A subset of customers hosted in Western Continental Europe is affected, representing approximately 4% of our customer base. You are likely impacted if you encounter a "The server returned a 500 Internal Server Error" message when attempting to access your instance. We are actively investigating the root cause and will provide an update in 30 minutes.
-
investigating Jun 23, 2026, 01:20 PM UTC
We are still actively investigating the issue. We'll provide an update in 30 minutes.
-
investigating Jun 23, 2026, 01:50 PM UTC
We are still actively investigating the issue. We'll provide an update in 30 minutes.
-
monitoring Jun 23, 2026, 02:01 PM UTC
The issue has been identified, and a fix has been implemented. Service is getting back to normal. We are actively monitoring the recovery.
-
monitoring Jun 23, 2026, 02:02 PM UTC
We are continuing to monitor for any further issues.
-
resolved Jun 23, 2026, 02:14 PM UTC
This incident has been resolved. We sincerely apologize for the disruption, and thank you for your patience while we worked on this issue.
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2026, 03:21 PM UTC
- Resolved
- Jun 19, 2026, 06:27 PM UTC
- Duration
- 1d 3h
Affected: UIREST APIGraphQL API
Timeline · 7 updates
Read the full incident report →
- Detected by Pingoru
- Jun 11, 2026, 06:46 PM UTC
- Resolved
- Jun 11, 2026, 07:34 PM UTC
- Duration
- 48m
Affected: Akeneo App for Shopify
Timeline · 4 updates
-
investigating Jun 11, 2026, 06:46 PM UTC
Customers report not being able to access Apps since 6pm UTC, across all regions. You are impacted if you can see "App no longer listed on the Akeneo App Store" message on the Connected Apps page. Our team is actively working on identifying the root cause of the problems.
-
investigating Jun 11, 2026, 07:10 PM UTC
Synchronization jobs to third party systems are verified to be working properly. The incident is limited to listing the App from the App Store.
-
identified Jun 11, 2026, 07:29 PM UTC
The issue has been identified and a fix is being implemented.
-
resolved Jun 11, 2026, 07:34 PM UTC
The incident is now resolved. Access to apps is back and fully operational. We apologize for the inconvenience, and thank you for your patience while we were solving the issue.
Read the full incident report →
- Detected by Pingoru
- Jun 04, 2026, 09:01 AM UTC
- Resolved
- Jun 04, 2026, 11:03 AM UTC
- Duration
- 2h 1m
Affected: Supplier Data Manager
Timeline · 3 updates
-
identified Jun 04, 2026, 09:01 AM UTC
We are currently experiencing errors in AI-enabled SDM steps (Classification and Extraction) for all ongoing jobs. We are actively investigating the root cause of the issue.
-
identified Jun 04, 2026, 10:23 AM UTC
We are currently restoring the failed SDM jobs for Classification and Extraction.
-
resolved Jun 04, 2026, 11:03 AM UTC
The issue affecting AI-enabled SDM steps is now resolved. All affected jobs have been restarted. We sincerely apologize for this temporary disruption.
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2026, 03:06 PM UTC
- Resolved
- Jun 03, 2026, 03:53 PM UTC
- Duration
- 46m
Affected: Akeneo App for Shopify
Timeline · 2 updates
-
monitoring Jun 03, 2026, 03:06 PM UTC
We have identified an issue in which synchronizations aren't working for some merchants due to a partial outage of the Shopify API. The issue has been identified and mitigated by the Shopify team and is currently being monitored. You can follow the resolution of the issue directly on the Shopify Status Page: https://www.shopifystatus.com
-
resolved Jun 03, 2026, 03:53 PM UTC
This issue has been resolved and is being monitored by Shopify.
Read the full incident report →
- Detected by Pingoru
- Jun 01, 2026, 04:15 PM UTC
- Resolved
- Jun 01, 2026, 04:51 PM UTC
- Duration
- 35m
Affected: UI
Timeline · 2 updates
-
monitoring Jun 01, 2026, 04:15 PM UTC
We have implemented a fix for the issue affecting the delay in job execution for some customers in the Europe region. We are now monitoring our systems closely to confirm full recovery and stability. So far, we've seen positive results.
-
resolved Jun 01, 2026, 04:51 PM UTC
The issue affecting the delay in job execution is now resolved, and all services are operating normally. We sincerely apologize for the disruption this caused. Thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- May 26, 2026, 01:36 PM UTC
- Resolved
- May 26, 2026, 04:43 PM UTC
- Duration
- 3h 6m
Affected: UI
Timeline · 5 updates
-
identified May 26, 2026, 01:36 PM UTC
Users in Germany are currently experiencing degraded performance when progressing through collaboration workflows. Specifically, there is a noticeable delay between the start or completion of a workflow step, and the product loading on the next step. Who is affected: All users based in Germany using collaboration workflows in the PIM. You may be impacted if: You observe abnormal delays between completing a workflow step and the product appearing on the subsequent step. We are implementing a fix and will provide an update in 60 minutes.
-
identified May 26, 2026, 02:30 PM UTC
We are still working on implementing the fix. We will provide an update within 90 minutes.
-
identified May 26, 2026, 04:02 PM UTC
We are still working on implementing the fix. We will provide an update within 90 minutes.
-
identified May 26, 2026, 04:40 PM UTC
We are continuing to work on a fix for this issue.
-
resolved May 26, 2026, 04:43 PM UTC
A fix has been deployed, and after monitoring we have confirmed that Workflows have been restored to standard functionality. We apologise for the inconvenience caused by this temporary disruption.
Read the full incident report →
- Detected by Pingoru
- May 22, 2026, 08:04 AM UTC
- Resolved
- May 22, 2026, 11:31 AM UTC
- Duration
- 3h 26m
Affected: Supplier Data Manager
Timeline · 4 updates
-
identified May 22, 2026, 08:04 AM UTC
We are currently experiencing delays in job processing on Supplier Data Manager. Our team is actively investigating and working to restore normal performance. We sincerely apologize for the inconvenience caused by this service disruption.
-
identified May 22, 2026, 08:52 AM UTC
We are continuing to work on a fix for this issue.
-
monitoring May 22, 2026, 11:15 AM UTC
A fix has been implemented and we are monitoring the results. New SDM jobs are now processed as expected.
-
resolved May 22, 2026, 11:31 AM UTC
This incident has now been resolved. All affected jobs have been reset and new jobs are processed correctly. We apologise for the inconvenience caused by this temporary disruption.
Read the full incident report →
- Detected by Pingoru
- May 05, 2026, 09:54 AM UTC
- Resolved
- May 05, 2026, 09:54 AM UTC
- Duration
- —
Affected: Supplier Data Manager
Timeline · 1 update
-
resolved May 05, 2026, 09:54 AM UTC
We have experienced degraded performance for SDM jobs processed after 28th April, at Mapping and Normalization steps. The jobs were incorrectly marked as complete before the end of the workflow. The issue has been identified and resolved on production. The impacted jobs will be automatically reset today, resuming normal workflow operation. We sincerely apologize for the inconvenience caused by this service disruption.
Read the full incident report →
- Detected by Pingoru
- May 05, 2026, 08:11 AM UTC
- Resolved
- May 06, 2026, 05:28 PM UTC
- Duration
- 1d 9h
Affected: UIREST API
Timeline · 8 updates
-
investigating May 05, 2026, 08:11 AM UTC
Starting on May 4 at around 12:00 PM UTC, customers hosted in the Western European region are experiencing intermittent episodes of high response times within the PIM. The issue is ongoing and occurring episodically — normal performance resumes between episodes. During affected periods, pages and actions may take significantly longer than usual to load or complete. All customers in the Western European region may be affected, though not continuously. We are actively investigating and working to stabilize the platform. We will provide an update as soon as we have more information to share.
-
investigating May 05, 2026, 10:13 AM UTC
We are continuing to investigate this issue and will keep you updated on the situation within 2 hours. Thank you for your understanding
-
investigating May 05, 2026, 01:18 PM UTC
The investigation is still ongoing as our team is trying to analyse the root cause of the high latency episodes within our infrastructure. We will keep you updated in the next 3 hours. Thank you for your patience.
-
monitoring May 05, 2026, 02:39 PM UTC
Our engineers have identified a bottleneck and have performed an operation to release pressure on our infrastructure. We'll keep closely monitoring the situation and will provide an update within the next 2 hours. Thanks for your patience
-
monitoring May 05, 2026, 04:40 PM UTC
We are continuing to monitor for any further high-latency episodes. Thank you for your patience.
-
monitoring May 06, 2026, 12:26 PM UTC
We are currently implementing additional mitigations on our infrastructure to continue improving overall latency and PIM performance. We will make sure to keep you updated within the next 3 hours. Thank you for your patience
-
monitoring May 06, 2026, 04:30 PM UTC
The mitigation is still in progress, and the latency is going back to its expected level. We will inform you when the situation is fully resolved. Thank you for understanding.
-
resolved May 06, 2026, 05:28 PM UTC
This incident has been resolved, and the PIM is now performing within its expected parameters in the Western European region. Thank you for your patience
Read the full incident report →
- Detected by Pingoru
- Apr 23, 2026, 04:07 PM UTC
- Resolved
- Apr 23, 2026, 06:05 PM UTC
- Duration
- 1h 57m
Affected: UI
Timeline · 3 updates
-
identified Apr 23, 2026, 04:07 PM UTC
Since 12:30 UTC, users are experiencing performance issues with the Workflow feature. When performing enrichment operations, the Workflow UI may become completely unresponsive. All users of the Workflow feature are affected. API Workflow enrichment remains operational. We have identified the issue and are currently working on deploying the fix in production. We will update you within 60 minutes.
-
monitoring Apr 23, 2026, 05:45 PM UTC
A fix is being deployed for this issue and we are monitoring the results.
-
resolved Apr 23, 2026, 06:05 PM UTC
The fix has been deployed and we have confirmed that the Workflow feature is now working as expected. We apologize for the disruption.
Read the full incident report →
- Detected by Pingoru
- Apr 21, 2026, 02:38 PM UTC
- Resolved
- Apr 21, 2026, 03:01 PM UTC
- Duration
- 22m
Affected: UI
Timeline · 2 updates
-
monitoring Apr 21, 2026, 02:38 PM UTC
We have identified an issue in which some users in the Western European region are experiencing increased latency across all exports and all imports except product imports. The issue began around 2:00 PM CEST on April 21st, 2026. Our engineering team has identified the root cause within our infrastructure and has implemented a fix to mitigate the issue. We will continue monitoring the situation and provide an update within 1 hour.
-
resolved Apr 21, 2026, 03:01 PM UTC
The incident has been resolved, and all import and export jobs in Western Europe are now being processed as expected.
Read the full incident report →
- Detected by Pingoru
- Apr 17, 2026, 08:22 AM UTC
- Resolved
- Apr 17, 2026, 11:30 AM UTC
- Duration
- 3h 7m
Affected: UI
Timeline · 4 updates
-
investigating Apr 17, 2026, 08:22 AM UTC
We have identified an issue where a subset of customers in the Western European region is experiencing increased latency on product and product model imports. The issue began around 5:00 PM CEST on April 16th, 2026. Our engineering team is actively investigating the root cause. We will provide an update in 60 minutes.
-
identified Apr 17, 2026, 09:32 AM UTC
The issue has been identified, and a fix is being implemented to mitigate the latency on import jobs. We will provide another update within 60 minutes.
-
monitoring Apr 17, 2026, 09:52 AM UTC
The latency has decreased, and import jobs are now processing as expected. We will continue to monitor import jobs' performance to confirm the incident is resolved.
-
resolved Apr 17, 2026, 11:30 AM UTC
The issue affecting the latency is now resolved, and imports are operating at the expected level of performance. We apologize for any disruptions this issue may have caused. Thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Apr 09, 2026, 12:54 PM UTC
- Resolved
- Apr 09, 2026, 01:53 PM UTC
- Duration
- 59m
Affected: UI
Timeline · 3 updates
-
monitoring Apr 09, 2026, 12:54 PM UTC
We are currently experiencing a partial outage preventing users from logging in and browsing the PIM UI. Who is affected: All users located in Eastern Europe (approximately 20% of our customer base) are impacted. If you are in this region and cannot log in or navigate the PIM, you are affected by this incident. Workaround: PIM REST API and GraphQL API remain usable. A fix has been implemented and is being monitored. We will provide an update in 30 minutes.
-
monitoring Apr 09, 2026, 01:01 PM UTC
Traffic is getting back to normal. We continue monitoring the platform. We will provide an update in 60 minutes.
-
resolved Apr 09, 2026, 01:53 PM UTC
This incident has been resolved. The issue affecting login and navigation on the PIM for users in Eastern Europe has been fully addressed following a fix deployed at 12:45 UTC. We apologize for the disruption.
Read the full incident report →
- Detected by Pingoru
- Mar 26, 2026, 08:15 AM UTC
- Resolved
- Mar 26, 2026, 02:43 PM UTC
- Duration
- 6h 27m
Affected: UIREST APIGraphQL API
Timeline · 3 updates
-
investigating Mar 26, 2026, 10:08 AM UTC
We are currently observing increased response times when creating or updating several entities (product, product model, assets, reference entities and proposal) in europe west 1 region. Our team is actively investigating the issue and will provide additional updates as soon as more information becomes available.
-
monitoring Mar 26, 2026, 11:50 AM UTC
We have implemented a fix. We are now monitoring our systems closely to confirm full recovery and stability. So far, we've seen positive results.
-
resolved Mar 26, 2026, 02:43 PM UTC
The issue affecting the latency is now resolved, and all services are operating normally. The fix we deployed has proven effective. We sincerely apologize for the disruption this caused. Thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Mar 23, 2026, 08:42 AM UTC
- Resolved
- Mar 23, 2026, 02:20 PM UTC
- Duration
- 5h 38m
Affected: UI
Timeline · 4 updates
-
investigating Mar 23, 2026, 08:42 AM UTC
We are currently investigating an issue affecting product import jobs in the Australian region. Impacted jobs are abnormally remaining in a queued or failed state and are not being processed. All other regions are unaffected. Workaround: While we work on a fix, products can still be created using the PIM REST API or directly through the PIM UI. We will provide a further update along with the identification of the root cause. We apologize for the disruption.
-
identified Mar 23, 2026, 09:11 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Mar 23, 2026, 12:55 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 23, 2026, 02:20 PM UTC
The issue affecting product import jobs in the Australian region has been resolved. All import jobs are now processing normally. All pending jobs were processed. We apologize for the disruption this may have caused, and thank you for your patience while our engineering team worked on the resolution.
Read the full incident report →
- Detected by Pingoru
- Feb 18, 2026, 11:10 AM UTC
- Resolved
- Feb 18, 2026, 04:23 PM UTC
- Duration
- 5h 13m
Affected: GraphQL API
Timeline · 2 updates
-
identified Feb 18, 2026, 11:10 AM UTC
We are currently investigating an issue affecting GraphQL API pagination links specifically for reference entity records. This issue impacts all GraphQL API users worldwide, who include reference records in their products or product models (about 1% of our customer base), since Feb 17th, 6pm CET. Workaround: To obtain a valid URL, you can manually remove the #ref_entity suffix from the returned pagination link. We have identified the root cause, and are currently deploying a fix. We apologize for the disruption to your workflow.
-
resolved Feb 18, 2026, 04:23 PM UTC
The fix has been successfully deployed. All GraphQL pagination links generated since 4:30 PM CET are now fully functional. We appreciate your patience and understanding while we worked to resolve this issue.
Read the full incident report →
- Detected by Pingoru
- Feb 11, 2026, 10:08 AM UTC
- Resolved
- Feb 11, 2026, 01:43 PM UTC
- Duration
- 3h 34m
Affected: Supplier Data Manager
Timeline · 4 updates
-
investigating Feb 11, 2026, 10:08 AM UTC
We are currently investigating this issue.
-
identified Feb 11, 2026, 11:40 AM UTC
The slowness is caused by intermittent throttling/quotas from a third-party dependency. When these quotas are reached, some jobs may end in a failed state (only 1.6% of jobs in the last hours). We’re implementing a fix to increase the available quotas and reduce the risk of recurrence.
-
monitoring Feb 11, 2026, 01:07 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 11, 2026, 01:43 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 29, 2026, 08:42 AM UTC
- Resolved
- Jan 29, 2026, 09:04 AM UTC
- Duration
- 21m
Affected: Supplier Data Manager
Timeline · 2 updates
-
investigating Jan 29, 2026, 08:42 AM UTC
We are currently experiencing an increase in errors affecting job processing, especially on the Normalisation step. We are currently investigating this issue.
-
resolved Jan 29, 2026, 09:04 AM UTC
This incident has been resolved. A short-lived spike of internal errors was detected due to a sorting issue in the normalization step on a specific field. These errors were not noticeable by end users and did not impact job processing, execution, or customer data. The issue is resolved and monitoring remains in place.
Read the full incident report →
- Detected by Pingoru
- Jan 28, 2026, 02:59 PM UTC
- Resolved
- Jan 28, 2026, 03:53 PM UTC
- Duration
- 53m
Affected: UIREST API
Timeline · 3 updates
-
investigating Jan 28, 2026, 02:59 PM UTC
We have identified an issue where a subset of customers in the Americas region are experiencing increased latency and elevated error rates when using the PIM UI and API. The issue began around 1:00 PM CET and is currently affecting approximately 2.5% of customers in the Americas, with errors occurring on about 2% of requests. Our engineering team is actively investigating the root cause. We will provide updates as more information becomes available.
-
identified Jan 28, 2026, 03:18 PM UTC
The issue has been identified and a fix is being implemented.
-
resolved Jan 28, 2026, 03:53 PM UTC
The fix is implemented and PIM UI and API performance is now back to normal for all impacted customers. Thanks for your patience while the issue was being solved.
Read the full incident report →
- Detected by Pingoru
- Jan 26, 2026, 11:14 AM UTC
- Resolved
- Jan 24, 2026, 01:30 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jan 26, 2026, 11:14 AM UTC
We detected that some Americas customers were experiencing an unusual slowness, and errors in 20% of the cases, while using PIM UI and API. This affected about 2.5% of Americas customers. A fix was implemented by our engineering team and the performance is now back to its expected level. We apologize for any inconvenience during the resolution of this issue.
Read the full incident report →
- Detected by Pingoru
- Jan 18, 2026, 12:00 PM UTC
- Resolved
- Jan 18, 2026, 12:20 PM UTC
- Duration
- 20m
Affected: UIREST API
Timeline · 4 updates
-
investigating Jan 18, 2026, 12:00 PM UTC
We are currently investigating an outage affecting PIM UI and API for customers on Australian region since 11:55 CET. The root cause is under investigation. We will provide further updates as progress is made. We apologize for the inconvenience and appreciate your patience.
-
monitoring Jan 18, 2026, 12:08 PM UTC
A fix has been implemented, traffic is being monitored.
-
monitoring Jan 18, 2026, 12:10 PM UTC
We are continuing to monitor for any further issues.
-
resolved Jan 18, 2026, 12:20 PM UTC
PIM UI and API services are now up and running on the impacted Australian region. Thanks for your patience while we were solving the case.
Read the full incident report →
Critical January 18, 2026 - Detected by Pingoru
- Jan 18, 2026, 09:05 AM UTC
- Resolved
- Jan 18, 2026, 10:04 AM UTC
- Duration
- 58m
Affected: Supplier Data Manager
Timeline · 3 updates
-
identified Jan 18, 2026, 09:05 AM UTC
We are currently investigating an outage affecting SDM for all customers. The root cause has been identified, and our teams are actively implementing a fix to restore service. We will provide further updates as progress is made. We apologize for the inconvenience and appreciate your patience.
-
identified Jan 18, 2026, 10:03 AM UTC
We have identified and corrected a issue preventing access to SDM. All services are now back online. We have entered a monitoring phase to verify that all systems are responding correctly and that no residual connectivity issues remain.
-
resolved Jan 18, 2026, 10:04 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 15, 2026, 09:08 AM UTC
- Resolved
- Jan 15, 2026, 02:14 PM UTC
- Duration
- 5h 5m
Affected: UIREST API
Timeline · 2 updates
-
monitoring Jan 15, 2026, 09:08 AM UTC
We identified an issue causing some jobs to remain stuck in the “starting” state for customers located in Eastern Europe, since Jan 14th 21h CET. This delays also API event requests sending. A fix has been deployed, and we are actively monitoring the situation to ensure full recovery. We apologize for any inconvenience this delay may have caused.
-
resolved Jan 15, 2026, 02:14 PM UTC
We can observe that all jobs stuck in "starting" state were ran starting from 10am CET, with job activity getting back to a normal pace starting from 11am CET. Delayed API event requests sending followed the same pattern, with all events being processed and sent before 11am CET. The situation is back to normal since 11am CET. Thanks for your patience while this incident was being solved.
Read the full incident report →
