Elastx is currently experiencing a major incident affecting DBaaS and Application Monitoring (STO1 - Stockholm South) and 1 more component, which began 1d ago. The vendor's full update timeline is below.
Affected components
Update timeline
- investigating May 19, 2026, 02:01 PM UTC
There are issues after the planned maintenance of the DBaaS management system. Connections to your databases are not affected. The issues are purely in the management system. Management functionality might come and go while we are fixing the issues. Backups and other jobs handled by the management system might be delayed. Avoid doing any changes to your setup until the issues are solved.
- investigating May 19, 2026, 03:47 PM UTC
We have discovered a few selected data stores that are experiencing connectivity issues. Investigation ongoing
- identified May 19, 2026, 06:08 PM UTC
Scope has been narrowed and focus has shifted to building and implementing a potential fix. Currently we are still seeing a small amount of datastores impacted. We still advice to not perform any changes or scheduled work with datastores until this incident is resolved. New update will be approx. 21:30 CEST.
- investigating May 19, 2026, 07:30 PM UTC
The implementation of the fix has not had expected results and we are moving back the status to investigating and are analyzing the results to find a new solution. We still advice to not perform any changes or scheduled work with datastores until this incident is resolved. New update will be approx. 23:00 CEST.
- identified May 19, 2026, 09:01 PM UTC
More work on a fix is in progress from findings and is being tested and evaluated at the moment. For now we need to re-run multiple tests in parallel and will send out a new update once we have a more clear picture of a solution-ETA. We continue to advice against modifying or doing changes to the datastore configuration(s) at the moment.
- investigating May 19, 2026, 11:15 PM UTC
Update: Problem trigged by earlier maintenance requires rebuilding and code-reviews for a stable fix; to avoid issues with changes being done to datastores the management-ui is currently disabled externally. We will continue working on this and schedule a sit-rep tomorrow at 0900 internally with external resources and re-asses at that time.
- identified May 20, 2026, 07:26 AM UTC
Morning update: currently moving forward with 2 parallel possible solutions and are evaluating both in test-environments at the moment. We will re-assess both options and provide an update at 1200 at the latest.
- identified May 20, 2026, 09:58 AM UTC
Mid-day update: The database-management service has been partially restored however we are still seeing unknown/unstable states and issues connecting to datastores intermittently. Status changed to Status Disruption and our current focus is restoring services to stable state for all datastores. We still advice against doing modifications on datastores until incident is set to resolved.
- identified May 20, 2026, 11:33 AM UTC
Update: Issues reaching multiple data-stores has just been resolved by a manual fix and we will continue to monitor it as we are still continuing with the service-disruption on the management-system. If you still have issues connecting to your datastore we advice you to reach out with as much information as possible in order for us to assist. Incident remains open and we continue working on the underlying issue with the management-service.
- monitoring May 20, 2026, 08:38 PM UTC
Currently datastores are in a stable state and we are moving down to monitoring in terms of incident-status. Our 24/7 staffing remains available and developers will work on analyzing logs and results of todays work throughout the night for a handover tomorrow at 0900. A new update will be provided in the morning with next expected steps and actions to be done in regards to fully stabilize the management-service.