Dixa status

Status verification pending

The latest official observation is not fresh enough to confirm current service health.

Official incident resolved

Dev API unavailable — ## Summary On October 23, 2026, at 11:15 AM CEST, all requests to the Dixa Public API \(dev.dixa.io\) began failing with an error. The outage was caused by a faulty deployment of the component that authenticates incoming API requests. Our team detected the issue at 11:16 AM CEST, identified the cause, and deployed a fix. Full service was restored at 11:31 AM CEST. ## Impact Between 11:15 AM and 11:31 AM CEST, the Dixa Public API was unavailable for all customers. Every API request in this window, across all API versions, received an HTTP 500 error, and no request succeeded. Requests were rejected before they reached our systems, so no request was partially processed, and no data was lost or changed. Integrations that retry failed requests automatically will have recovered on their own. Integrations that do not retry may need to resend any calls made during this window. ## Root Cause The outage was caused by a manual deployment of the component that authenticates every request to the Dixa Public API. The new version of this component was packaged incorrectly, so it could not start. Without a working authentication step, every incoming API request failed. The code itself was correct; the problem was only in how it was packaged for deployment. ## Resolution Our team detected the issue at 11:16 AM CEST and began investigating the affected services. By 11:26 AM CEST, the root cause had been traced to the faulty deployment. A correctly packaged version of the same code was deployed at 11:30 AM CEST, and API requests began succeeding again immediately. Error rates were back to normal levels by 11:32 AM CEST. ## Preventive Measures To help prevent similar incidents going forward, we are: * Replacing manual deployments of this component with an automated deployment pipeline * Testing every change in a staging environment before it reaches production * Improving versioned releases, so we can roll back to a known-good version immediately * Adding further automated alerts on API authentication errors and error rates to detect issues faster ## Closing Note We understand how important reliable access to the Dixa Public API is to your integrations and workflows. We apologize for any inconvenience caused during this period and are committed to strengthening the resilience of this service.