Printix - The service is currently experiencing an issue

Incident Report for Tungsten Automation EMEA

Postmortem

Overview

On Monday, March 24, a large share of the connections to the Printix Service were lost at 06:45 UTC causing loss of the secure and remote print services (direct printing and admin portal access unaffected). This was caused by an incorrect memory setting within Printix following a service change the previous weekend.

Resolution

Memory settings were amended to the correct values allowing all users to reconnect to the service between 08:30 and 09:00UTC

Action Items

Monitoring adjustments made to give earlier warning of the out of memory events that occurred on this occasion

Update of documentation to reflect correct configurations to used in future

Investigation into reports that statuspage alerts were not received by many subscribed users

Posted Mar 25, 2025 - 15:48 GMT

Resolved

This incident has been resolved.
Posted Mar 24, 2025 - 09:08 GMT

Update

The Printix Service has now been restored.

Thank you for your patience, and we apologise for any inconvenience this may have caused.
Posted Mar 24, 2025 - 09:01 GMT

Update

The Printix Service is continuing to recover, and performance is improving. However, some users may still experience issues. Our team is actively monitoring and working to fully restore the service.
Posted Mar 24, 2025 - 08:55 GMT

Update

The Printix Service is now coming back online. You may experience some performance issues as the service is fully restored. Our team continues to monitor the situation to ensure stability.

We apologise for any inconvenience caused.
Posted Mar 24, 2025 - 07:49 GMT

Update

We are continuing to investigate this issue.
Posted Mar 24, 2025 - 07:47 GMT

Investigating

We are currently experiencing an issue causing the Printix Service to be unavailable. Our team is actively investigating and working to resolve the issue as quickly as possible.

We will provide updates as soon as we have more information.
Posted Mar 24, 2025 - 07:46 GMT
This incident affected: Printix.