Sevalla incident
Application deployments may remain stuck in in-progress state
Sevalla experienced a minor incident on April 28, 2026 affecting Applications, lasting 54m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Apr 28, 2026, 08:31 PM UTC
We are currently investigating an issue where application deployments are getting stuck in an "in-progress" state. Because of this, subsequent deployment requests are being queued and are currently blocked. Our engineering team is actively identifying the root cause and working toward a resolution to clear the queue and restore deployment functionality.
- identified Apr 28, 2026, 08:54 PM UTC
We have identified the root cause of the issue preventing application deployments from completing and causing subsequent deployments to be blocked. Our engineering team is currently working on implementing a fix to resolve the underlying issue and clear the backlog of queued deployments.
- monitoring Apr 28, 2026, 09:10 PM UTC
We have implemented a fix and are monitoring system performance to ensure stability. As part of our recovery process, pending deployment tasks have been marked as "Skipped" to safely restore normal operations to the platform. The system is now accepting new deployment requests. If you have an urgent change for an application that was affected by this incident, please initiate a new deployment. We apologize for the inconvenience and appreciate your patience while we restored service.
- resolved Apr 28, 2026, 09:25 PM UTC
We have confirmed that our deployment systems are fully stabilized and operating as expected. Following our earlier fix and the subsequent monitoring period, no further issues have been detected. Thank you for your patience during this incident. If you continue to experience any difficulties with your deployments, please reach out to our support team for further assistance.