← Go back to status.d-velop.cloud

Increased latency and HTTP 500 errors in d.velop documents

04. Mar 2026, 18:00

Viewing (AWS) Import (AWS) Search (AWS) Administration (AWS)

Resolved

(05. Mar, 08:41) Resolved - We are currently not observing any further errors. The problematic route has been blocked for all tenants. As previously stated, no customer impact is expected, as this route was intended for a future feature that is not yet active. We will continue investigating why this route caused the issue and will prepare an internal root cause RCA.

(05. Mar, 08:26) Disrupted - After blocking a potentially problematic route for the isolated tenant, we are no longer seeing any errors. We reviewed the possible negative effects of blocking this route and found there will be none, as it was intended for a future feature that is not currently active. We will continue to monitor the situation closely over the next minutes.

(05. Mar, 08:13) Disrupted - We have strong evidence that the issue has been successfully isolated to one tenant instance. We have identified the affected tenant and are continuing our investigation. In the past 30 minutes, errors have only occurred in this isolated tenant.

(05. Mar, 00:07) Disrupted - We have been able to narrow down and strongly isolate the issue. Only a small number of customers are affected, with an error rate of approximately 1.27%. The root cause is still under investigation. The next update will be provided in the morning.

(04. Mar, 21:40) Disrupted - We have identified tenants that were repeatedly active on affected server instances. We currently assume that at least one of these tenants may be contributing to the issue. As a mitigation measure, we are isolating these tenants on a separate cluster to prevent impact on other tenants.

(04. Mar, 20:44) Disrupted - Based on our current findings, the exact number of affected customers is unknown; many customers are impacted, but not concurrently. We are continuing our analysis and apologize for any inconvenience caused.

(04. Mar, 19:30) Disrupted - We are currently experiencing increased response times and HTTP 500 errors in d.velop documents, which may cause requests to fail or take longer than expected.