EnderDevelopment - Notice history

The platform has now fully recovered and is operating in a stable state.

Following the mitigation and coordination with our main provider, we’ve achieved significant performance improvements across the system. Simple project generation times have been reduced from 1–2 minutes to ~15 seconds, with overall stability greatly enhanced.

The infrastructure is now capable of handling up to 800+ tasks per day with improved reliability and throughput.

The system is currently stronger and more efficient than before, with no active blocking issues detected.

All services are operational. Let's go !

We have contacted our main infrastructure provider, who has assisted in identifying and resolving the underlying issue affecting our systems. Together with the provider, we have also improved the handling of the affected components to prevent further instability.

The situation has significantly improved: services are no longer fully blocked. However, the system is still operating in a degraded state, with occasional latency and reduced reliability in task processing.

Engineering teams are actively monitoring recovery and continuing stabilization efforts.

Further updates will follow as performance returns to normal.

We are continuing to observe system instability affecting all project-related tasks.

The issue initially identified in the circuit breaker layer now appears to be propagating across additional services, leading to increased latency, degraded performance, and continued task blocking.

Engineering teams are actively containing the spread and working on mitigation steps to restore stability.

At this time, tasks remain slow or fully blocked in several areas of the system. No ETA is available yet.

Further updates will be provided as the situation evolves.

We are currently experiencing a system-wide block affecting all project-related tasks.

During the investigation, we have identified issues within our circuit breaker mechanisms, which are currently triggering and preventing normal task execution across services.

Engineering teams are actively working on stabilizing the affected components and restoring normal flow.

At this stage, services remain degraded and task processing is still blocked. No ETA is available yet.

Further updates will follow as soon as mitigation progresses.

The backend issues have been resolved.
The cause was a series of syntax errors introduced during a recent update, which resulted in service crashes.

All systems are now operational again. Thank you for your patience.

We have implemented a fix to address the degraded AI generation performance. The system is now stabilizing, and we are actively monitoring to ensure full recovery and prevent recurrence.

The issue has been fully resolved, and we’ve also deployed improvements affecting existing project refactoring.

This results in more consistent behavior and better overall reliability across projects.

Thank you for your patience

The misclassification issue has been fully resolved, and projects are now being handled correctly.

We are now actively investigating a separate issue related to plan generation, specifically around progressive iterations and quality degradation over time.

Our team is working to identify the root cause and ensure consistent performance across all iterations.

Thank you for your patience — further updates will follow.

The issue has been fully resolved.

Root cause was identified as blocking synchronous operations on remote storage, combined with locking mechanisms that caused backend stalls under load.

We have addressed these bottlenecks and implemented fixes to ensure smoother, non-blocking behavior.

The system is now stable and operating normally.

Thank you for your patience

The issue now appears to be resolved again, and the platform is returning to normal operation.

We are currently optimizing and fine-tuning the system to improve overall stability and prevent further occurrences.

We will continue monitoring closely.

The issue has unfortunately reoccurred and is again affecting the platform.

Our team is actively investigating the root cause and working toward a stable resolution.

We apologize for the continued inconvenience and will provide further updates shortly.

We’ve deployed a potentially definitive fix to address the recurring backend issue.

The system is now stable, and we are actively monitoring performance and behavior in real-time to ensure everything remains fully operational.

While early signals are positive, we’ll keep a close watch to confirm long-term stability.

Thank you again for your patience

The issue has been identified, monitored, and fully resolved.

We have taken immediate action to stabilize the system and ensure everything is now operating correctly.

We will continue to monitor closely and implement additional safeguards — we expect this not to occur again.

Thank you for your patience