The service disruption / connection issues within Winsolvenz cloud (incl. LegalTwin: Forderungserfassung & LegalTwin: IK-Verfahrensanlage Plus as well as the Deutsche Bank integration) are resolved. We’re sorry for any disruption and inconvenience users may have experienced. We continued to monitor the situation and have not observed any further issues over the course of the week. Please reach out to support@stp.one for any questions.
Die Service-Störung / Verbindungsprobleme innerhalb der Winsolvenz-Cloud (einschließlich LegalTwin: Forderungserfassung & LegalTwin: IK-Verfahrensanlage Plus sowie der Deutschen Bank Integration) sind behoben. Wir entschuldigen uns für die Beeinträchtigungen und Unannehmlichkeiten, die bei den Benutzern entstanden sein könnten. Wir haben die Situation weiter beobachtet und im Lauf der Woche keine Probleme mehr festgestellt. Bei Fragen wenden Sie sich bitte an support@stp.one.
We’ve deployed a fix that stabilizes the connection issues. Users should now be able to work with the corresponding systems again. We’re monitoring to ensure the problem is solved and work on a final solution. Please reach out to support@stp.one
for any questions.
Wir haben einen temporären Fix implementiert, der die Verbindungsprobleme stabilisiert. Die Benutzer sollten nun wieder mit den entsprechenden Systemen arbeiten können. Wir überwachen die Situation, um sicherzustellen, dass das Problem gelöst ist, und arbeiten an einer endgültigen Lösung. Bei Fragen wenden Sie sich bitte an support@stp.one.
We are currently experiencing several problems within Winsolvenz cloud (incl. LegalTwin: Forderungserfassung & LegalTwin: IK-Verfahrensanlage Plus as well as the Deutsche Bank integration). Our team is working to identify the root cause and fix the issue. Users may be experiencing problems in the document processing and integration. Please reach out to support@stp.one for any questions.
Derzeit treten mehrere Probleme innerhalb der Winsolvenz-Cloud auf (einschließlich LegalTwin: Forderungserfassung & LegalTwin: IK-Verfahrensanlage Plus sowie der Deutschen Bank Integration). Unser Team arbeitet daran, die Ursache zu ermitteln und das Problem zu beheben. Bei den Benutzern können Probleme bei der Dokumentenverarbeitung und -integration auftreten. Bei Fragen wenden Sie sich bitte an support@stp.one.
The service disruption / connection issues within Winsolvenz cloud (incl. LegalTwin: Forderungserfassung & LegalTwin: IK-Verfahrensanlage Plus as well as the Deutsche Bank integration) are resolved. We’re sorry for any disruption and inconvenience users may have experienced. We continued to monitor the situation and have not observed any further issues over the course of the week. Please reach out to support@stp.one for any questions.
Die Service-Störung / Verbindungsprobleme innerhalb der Winsolvenz-Cloud (einschließlich LegalTwin: Forderungserfassung & LegalTwin: IK-Verfahrensanlage Plus sowie der Deutschen Bank Integration) sind behoben. Wir entschuldigen uns für die Beeinträchtigungen und Unannehmlichkeiten, die bei den Benutzern entstanden sein könnten. Wir haben die Situation weiter beobachtet und im Lauf der Woche keine Probleme mehr festgestellt. Bei Fragen wenden Sie sich bitte an support@stp.one.
We’ve deployed a fix that stabilizes the connection issues. Users should now be able to work with the corresponding systems again. We’re monitoring to ensure the problem is solved and work on a final solution. Please reach out to support@stp.one
for any questions.
Wir haben einen temporären Fix implementiert, der die Verbindungsprobleme stabilisiert. Die Benutzer sollten nun wieder mit den entsprechenden Systemen arbeiten können. Wir überwachen die Situation, um sicherzustellen, dass das Problem gelöst ist, und arbeiten an einer endgültigen Lösung. Bei Fragen wenden Sie sich bitte an support@stp.one.
We are currently experiencing several problems within Winsolvenz cloud (incl. LegalTwin: Forderungserfassung & LegalTwin: IK-Verfahrensanlage Plus as well as the Deutsche Bank integration). Our team is working to identify the root cause and fix the issue. Users may be experiencing problems in the document processing and integration. Please reach out to support@stp.one for any questions.
Derzeit treten mehrere Probleme innerhalb der Winsolvenz-Cloud auf (einschließlich LegalTwin: Forderungserfassung & LegalTwin: IK-Verfahrensanlage Plus sowie der Deutschen Bank Integration). Unser Team arbeitet daran, die Ursache zu ermitteln und das Problem zu beheben. Bei den Benutzern können Probleme bei der Dokumentenverarbeitung und -integration auftreten. Bei Fragen wenden Sie sich bitte an support@stp.one.
We have made additional debug information available for you under Tenant Admin --> On-Premises within your STP Cloud Tenant UI.
It shows the currently configured connection limit of your tenant and the number of open connections. This information was previously not available for you.
If you are exceeding your configured connection limit, you'll be pointed to our HelpCenter article with the workaround of how to reset your STP OnPremise Connector, that we also shared earlier: https://support.stp.one/hc/de/articles/33409788989085-Erneutes-Aufbauen-einer-OnPremise-zu-Cloud-Verbindung-mit-dem-STP-OnPremise-Connector
We recommend applying the workaround also if you currently are using more than 2 connections as this may indicate a potential issue.
We're going to close this status page incident and kindly ask you to reach out to support@stp.one in case you still experience any issues. Please ensure you have checked above mentioned and newly provided information under Tenant Admin --> On-Premises to exclude this as a root cause.
As outlined before, we're further planning to release an updated version of the STP OnPremise Connector as part of our soon to happen Launch Day in February, that'll further address the root cause identified.
We have identified the root cause of the issue and successfully reproduced the incident in a controlled environment. It originates from an edge case in the connection self healing protocol of the STP OnPremise Connector. We are working on releasing an updated version.
The mechanism responsible for re-establishing the connection to stp.cloud after a connection loss contained an issue that, under certain conditions, could trigger a reconnection storm toward our cloud. Last week, this led to a cascading, self amplifying effect that overloaded the cloud service until we mitigated the situation by introducing additional connection limits on the cloud side. The issue does not occur in all cases of lost connectivity to stp.cloud, but only under specific technical circumstances.
In this particular incident, the type of the initial cloud service interruption created exactly the conditions in which the self-amplifying issue could occur. The outage lasted long enough for the self amplifying error cascade to unfold, ultimately resulting in the long service disruption we observed.
Regarding the initial interruption of our cloud services, we have identified opportunities for operational improvements and are in the process of implementing them.
We see more and more customer's applying the workaround mentioned in our last update and re-establish the connections.
We set the status of our systems back to operational, but we keep monitoring the situation closely.
Please reach out to support@stp.one for any questions.
The previously mentioned workaround was succesfully verified and described in a HelpCenter article: https://support.stp.one/hc/de/articles/33409788989085-Erneutes-Aufbauen-einer-OnPremise-zu-Cloud-Verbindung-mit-dem-STP-OnPremise-Connector
All customers that have reached out to support@stp.one have also received these instructions as a response to their raised incident ticket.
In case your system is still having connection issues, please apply the desribed workaround to ensure the connections are working again.
Please reach out to support@stp.one for any questions.
We’ve seen successfully reconnecting customer on-premise systems since our last update. However, not all customers are reconnecting succesfully as desired. We have identified a potential root cause related to our on-premise connector client that has initially lead to the incident and prevents those systems from connecting right now. We are approaching some selective customers to further verify a workaround to enable recovery for them. We tested that workaround on our internal demo environments systems that were also effected by the issue. As soon as we have verified this workaround, we'll share in here and our support will hand out further instructions. Please reach out to support@stp.one for any questions.
We’ve allowed connections from on-premise systems this morning and are closely monitoring the situation. We applied throttling mechanisms. Your on-premise connectors may indicate in their logfiles that they are refused to connect due to a connection limit being applied. We are working on allowing every system to connect safely. Please reach out to support@stp.one for any questions.
We’ve been facing another incident as a consequence of the high load, which has lead to corrupted data we had to identify and recover first. Afterwards we have restored the on-premise connector cloud service and our internal systems are working within regular parameters with the extended capacity. At ~19:15 we have temporarily re-allowed connections from on-premise customer systems for about 10 minutes that you may have seen in your logging. We have seen again a massive load spike and are evaluating the data of this test, to ensure that we're not suffering the same situation again before moving back to regular operations. Please reach out to support@stp.one for any questions.
We’ve determined that there's an issue with our cloud based endpoint for the on-premise connectors that started to materialize at around ~10:45 CET. We saw a continuously increasing load exceeding the applied safety thresholds on spare capacity. It was detected by our monitoring and further alerted our operators. We’re working to recover the endpoint's availability by adding additional capacity to handle the load situation to restore the service. Please reach out to support@stp.one for any questions.
We are currently experiencing a connectivity issue for various services related to our on-premise connectors. Our team is working to identify the root cause and fix the issue. Users may be experiencing delays and data not being submitted to the cloud. Please reach out to support@stp.one for any questions.
