Resolved after 5 hours 5 minutes, affecting UI and REST API, on January 15, 2026.
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.
Affected components
Update timeline
- 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.
Your product runs on more than Akeneo
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services