Eptura experienced a minor incident on February 24, 2026 affecting Eptura Asset, lasting 19h 2m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Feb 24, 2026, 09:52 PM UTC
We are currently investigating reports of intermittent issues affecting Eptura Asset returning Server Connection error messages. Our engineering team is actively working to identify the root cause. We will continue to closely monitor the situation and provide further updates as they become available
- monitoring Feb 24, 2026, 11:00 PM UTC
We have implemented mitigation measures and the service has stabilized. At this time, we are no longer observing server connection errors impacting Eptura Asset. Our engineering team will continue to closely monitor the environment to ensure continued stability and to confirm the issue is fully resolved. We will provide additional updates if there are any changes. Thank you for your patience.
- monitoring Feb 25, 2026, 08:36 AM UTC
Service performance has returned to expected levels following the mitigation steps taken by our teams. We are not currently seeing server connection errors affecting Eptura Asset. We will maintain monitoring of the environment to ensure stability is sustained. Should there be any notable changes, we will share further updates. Thank you for your continued patience.
- resolved Feb 25, 2026, 04:54 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.
- postmortem Mar 18, 2026, 10:48 PM UTC
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:** Eptura Asset 503 Connection Error **Type of Event:** Outage **Services/Modules impacted:** Asset Inventory Module **Timeline:** Feb 25th 21:52 UTC Customers reporting intermittent 503 Connection Error Feb 25th 23:00 UTC Hotfix in place for Quality Assurance Testing Feb 26th 8:36 UTC Hotfix Applied to Production Feb 26th 16:54 UTC Customers confirming back online **Total Duration of Event:** 19 hrs **Root Cause:** Our reporting service \(Exago\) was experiencing slow or unresponsive behavior. Because our application relied on this service for certain requests, these delays caused system‑wide slowdowns and, in some cases, 503 errors. When Exago became overloaded, it affected the performance of unrelated areas like Work Orders, Assets, and other core features. **Remediation:** We implemented several backend improvements to ensure reporting issues stay isolated and no longer impact the rest of the application. * **Asynchronous request handling** Reporting requests now run asynchronously, allowing the system to stay responsive even if individual reporting calls are slow. * **Circuit breaker pattern** If the reporting service becomes unhealthy, the system automatically detects this and temporarily stops sending new requests. This prevents slowdowns from spreading across the application. * **Session deduplication** Multiple tabs or browser refreshes no longer create duplicate reporting sessions. All repeated user actions are consolidated into a single backend request. * **Session caching** Newly created reporting sessions are briefly cached \(30 seconds\), reducing unnecessary repeat calls during login bursts or fast navigation. * **Strict timeout controls** All reporting requests follow a consistent end‑to‑end timeout \(up to 270 seconds\). This ensures system resources are promptly released even when Exago is slow or unresponsive. * **Improved telemetry and monitoring** New Prometheus metrics provide better visibility into thread usage, allowing the team to detect early warning signs before they impact customers. **Preventative Action:** These updates ensure that reporting issues no longer affect critical areas of the application. If Exago becomes slow, the impact is now contained, other features are expected to continue working normally. New Behavior Summary · Backend timeout: 270 seconds max per attempt · Frontend retries: 8 attempts over 3 minutes max · Session caching: 30 seconds \(reduces duplicate requests from multiple user tabs\) · Circuit breaker: Opens after 20% failure rate, pauses attempts for 30 seconds, Users get fast failure responses during this window rather than long waits