Eptura experienced a major incident on February 23, 2026 affecting Eptura Asset, lasting 7h 59m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Feb 23, 2026, 03:01 PM UTC
We are currently aware of reports that Asset is not accessible for some users. Our teams are actively investigating the issue and working to identify the root cause. We will provide updates as more information becomes available. Thank you for your patience as we work through this.
- investigating Feb 23, 2026, 03:05 PM UTC
We are continuing to investigate this issue.
- identified Feb 23, 2026, 03:59 PM UTC
Our engineers have identified the issue, isolated the affected servers, and redirected traffic to fully operational systems. At this time, service should be functioning normally. Thank you for your patience and understanding.
- monitoring Feb 23, 2026, 06:13 PM UTC
A fix has been implemented, and our engineering team is actively monitoring system performance to ensure full stability. We will provide further updates if conditions change. Thank you for your patience and understanding.
- monitoring Feb 23, 2026, 10:59 PM UTC
We’re pleased to share that the issue has now been resolved. Both our internal teams and external users have confirmed that all services are functioning as expected. We sincerely appreciate your patience and understanding while we worked to restore normal operations. Our team is preparing a detailed Root Cause Analysis, which will be published within the next 10 business days. Thank you for your continued trust and partnership.
- resolved Feb 23, 2026, 11:00 PM UTC
This incident has been resolved.
- postmortem Mar 18, 2026, 06:07 PM UTC
**Eptura Asset detailed Root Cause Analysis | Feb 23rd 2026** We are grateful for your continued support and loyalty. We value your feedback and appreciate your patience as we worked to resolve this incident. **Description:** Asset Service Unavailable **Type of Event:** Outage **Services/Modules impacted:** Asset Service **Timeline:** Feb 23rd 6:24am customers reporting that sites were unable to be reached Feb 23rd 7:30am Production Server down Feb 23rd 8:06am All Eptura Asset sites offline Feb 23rd 9:03am All sites back online **Total Duration of Event:** 2\.75hrs **Root Cause:** During a planned system update, a new major version of .NET was deployed as part of our Eptura Asset heritage process. This version introduced changes in how the application manages threading. Under certain conditions, these changes reduced the number of available threads, which led to intermittent 503 errors when the system couldn’t process requests as expected. **Remediation:** Existing automation helped keep the service running by restarting parts of the system when errors occurred. Once the underlying issue was identified, the team increased system capacity so incoming requests could be handled more reliably. We also updated the application to manage high‑demand scenarios more smoothly and improved several areas that were putting extra strain on the system, most notably the process used to create Exago REST sessions. To support ongoing reliability, the CloudOps team is now tracking thread‑related performance metrics in Prometheus. This gives visibility into early signs of resource pressure and enables more proactive monitoring. **Preventative Action:** Engineering will complete additional system updates during off‑hours on the weekend to further strengthen stability. We are also separating major system changes from regular releases and planning them during lower‑traffic periods to reduce the chance of customer impact. For future releases that involve more than routine code changes, CloudOps will participate in the Go/No‑Go process to ensure all operational steps are accounted for. CloudOps will also perform more strenuous load testing to identify potential high‑demand issues early and address them before they affect performance.