Koyeb - Notice history

We implemented a fix and are currently monitoring the result.

This was caused by an API update from one of our third party.

The incident is now resolved, we are sorry about the impact, and we are available to discuss the details if needed.

We implemented a fix and have re-scheduled most of the impacted failing service.

The initial incident triggering 404 was handled very shortly after it was detected, we noticed that some users were still experiencing some 503 due to an automatic garbage collection of some network resources.

Then we implemented a fix to recover the data that were garbage collected.

The recovery was done under 5m for most app, but a portion of user were still facing 503, we are currently trying to resolve this issue.

We are still monitoring the state of services on the platform but the issue should be fixed.

We are continuing to work on a fix for this incident. The 404 issue has been fixed.

New services deployed in Frankfurt are however still not accessible. Accessing their public URL ends up in HTTP 502.

We identified the root cause of the issue and are working on a fix.

The issue only affects services deployed in Frankfurt.

All services are confirmed to be back online.

All services are back online and we're monitoring to make sure everything is back to normal.

The root cause was identified and we're actively restarting all services.