Is Tungsten Automation EMEA down?

We are investigating an issue where processing times are taking longer than usual.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are aware of an issue causing slow performance for some customers and are working to restore full service as quickly as possible. Further updates will be provided as more information becomes available.

We have identified the issue and are working on a resolution.

We have identified the reason for the issue, applied measures and restored normal service operation.

**Summary** On March 26, 2026, between approximately 13:00 and 14:15 UTC, the Printix EU service again experienced slow performance. Although symptoms were similar to the previous day's incident, the root cause was different. **Root Cause** The incident was caused by a period of unusually high database activity. Certain operations generated long-running queries that exceeded the database's processing capacity, leading to degraded performance and temporary service slowness. **Resolution** Our Operations team identified the source of the excessive database load and took immediate action to restore normal operation. The incident was resolved at approximately 14:15 UTC. **Preventive Measures** Product-level changes are being evaluated to introduce safeguards against operations that could place excessive load on shared infrastructure. Enhanced monitoring for unusual usage patterns and database load is also being implemented.

We are aware of an issue causing slow performance for our customers. We are working to restore full service as quickly as possible. We apologize for any inconvenience caused and appreciate your patience. Further updates will be provided as more information becomes available.

The issue has been identified and a fix is being implemented.

We are continuing to work on a fix for this issue.

We have applied a fix and seen improvements, the service is operational.

**Summary** On March 25, 2026, between approximately 11:46 and 16:30 UTC, the Printix EU service experienced slow performance. During this period, some customers experienced timeouts and errors when accessing the customer portal and partner portal.   **Root Cause** The incident was caused by a data processing issue in a key service component responsible for caching frequently accessed data. When certain datasets exceeded an internal size threshold, they were silently rejected from the cache, resulting in continuous expensive data regeneration. This significantly reduced cache efficiency and degraded performance across the service.   **Resolution** Our Operations team identified the issue through detailed analysis and applied a configuration change to increase the size threshold. The cache recovered immediately and the service returned to normal operation at approximately 16:30 UTC.   **Preventive Measures** Enhanced monitoring for cache performance metrics is being implemented to enable earlier detection of similar issues. Additional alerting is being introduced to identify unusual load patterns before they impact service availability.

We are currently experiencing a degradation of service affecting our operations in Poland. This may impact the clearance and retrieval of invoices from KSeF. Our teams are aware of the issue and are actively investigating the root cause. We are working to restore full service as quickly as possible. We apologize for any inconvenience caused and appreciate your patience. Further updates will be provided as more information becomes available.

We are continuing to monitor the situation. We have seen improvement in the clearance and retrieval of invoices, with normal flow beginning to resume. Our teams remain engaged and are closely monitoring service stability. Further updates will be provided as more information becomes available.

Normal service has been restored. The issue affecting clearance and retrieval of invoices has been addressed. We apologize for any inconvenience caused and thank you for your patience.