Akeneo Outage History
Akeneo is up right nowPingoru has recorded 56 incidents for Akeneo: 42 in the last 12 months and 9 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 4 | 7 of 720 (1%) |
| May 2026 | 4 | 40 of 744 (5%) |
| June 2026 | 7 | 53 of 720 (7%) |
| July 2026 | 4 | 108 of 744 (14%) |
| August 2026 | 0 | 160 of 744 (22%) |
| September 2026 | 2 | 1 of 720 (0%) |
| October 2026 | 6 | 23 of 592 (4%) |
Incidents, newest first
Notice August 7, 2025 August 6, 2025 - Assets Export Returning Incomplete Data – UI
Started Aug 07, 2025, 07:53 AM UTC· resolved Aug 07, 2025, 07:53 AM UTC
- resolved Aug 07, 2025, 07:53 AM UTC
From 14:04 CET to 22:00 CET, the assets export feature was incorrectly limited, returning a maximum of ten assets instead of the complete dataset. This was due to a pagination issue introduced in a recent update. The problem has since been resolved, and the service is now fully operational. Important Information for Affected Users As a side effect of reverting the recent update, any export profiles that were created or updated during the incident period (14:04 CET - 22:00 CET) contain an extra fiters field in their configuration. This prevents these specific profiles from being launched or edited, resulting in a 400 error. To resolve this, please create a new export profile to resume normal operations. We apologize for any inconvenience this may have caused.
Minor August 1, 2025 Import and Export Jobs Experiencing Failures 3h 32m UI, REST API
Started Aug 01, 2025, 04:41 PM UTC· resolved Aug 01, 2025, 08:13 PM UTC
- investigating Aug 01, 2025, 04:41 PM UTC
We are currently investigating an issue causing degraded performance and failures in approximately 4% of import and export jobs. Our engineering team is actively working to identify the root cause and implement a fix. A mitigation has been implemented to reduce the impact while the full resolution is in progress.
- resolved Aug 01, 2025, 08:13 PM UTC
The root cause of this issue was identified, and a fix was deployed. After monitoring the situation, the issue has now been confirmed as resolved.