Salv had 15 outages in the last 2 years totaling 18h 48m of downtime — averaging 0.6 incidents per month.
There were 15 Salv outages since June 18, 2024 totaling 18h 48m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are reverting the changes to scenarios at the moment.
The affected scenarios were reverted.
This incident has been resolved.
Users may experience errors when trying to upload files to Salv Platform.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved. Our engineering team identified the root cause as a resource allocation issue within our data processing tier. Remediation steps have been applied to optimize these workloads, and we have verified that all services have returned to normal performance levels.
Our DNS provider is experiencing service/network issues.
DNS provider outage details https://www.cloudflarestatus.com/incidents/8gmgl950y3h7
We are actively investigating the issue in collaboration with our DNS provider. Intermittent recovery of services has been observed; however, a permanent resolution is still in progress. We continue to monitor the situation closely and will provide updates as we make progress.
We are seeing positive progress, with intermittent recoveries becoming more consistent and system performance showing signs of stabilization. Our team continues to monitor the environment closely and will notify you once full recovery has been confirmed.
We are continuing to monitor for any further issues.
This incident has been resolved.
Between approximately 12:14 UTC and 12:19 UTC today and 12:26 UTC and 12:33 UTC today, our platform experienced a brief, partial service disruption. During this time, some users may have encountered failed API requests. The issue was caused by an internal service failure that led to a temporary overload on our systems. Our monitoring automatically detected the issue, and services recovered fully.
Background event processing experienced performance delays, which in turn caused a delay in webhooks being delivered to downstream systems.
We observed an issue where some requests were not answered (received 503 error) between 2:39 PM (GMT +3) and 3:04 PM (GMT +3). The root cause was a node malfunction. The issue has been mitigated and we are monitoring to ensure full recovery.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We identified an issue with a synthetic check that temporarily reported an incorrect system status. The underlying services remained operational throughout. The check has since been corrected, and we’re monitoring to ensure continued accuracy.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investing the cause of delays in webhooks processing.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
Our DNS provider is experiencing service/network issues. We are looking into alternative solutions to resolve issue on our side. Public API-s are not affected.
We have implemented a fix that should resolve the ongoing issue. Our team will continue to closely monitor the situation to ensure the system is functioning as expected.
No new issues have arisen during our monitoring, and we are concluding this incident as resolved. We will follow up with a detailed incident report shortly.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
Salv demo environment experienced an outage, rendering it unavailable for users. The outage lasted for approximately 1 hour.
Problem identified, we are rolling back to last known good version.
We are continuing to work on a fix for this issue.
Last good known version deployed and problem has resolved.