PaperCut incident

PaperCut Hive printing and scanning errors

Major Resolved View vendor source →

PaperCut experienced a major incident on April 23, 2025 affecting AU hosting region - PaperCut Hive & Pocket, lasting 1d. The incident has been resolved; the full update timeline is below.

Started
Apr 23, 2025, 03:39 AM UTC
Resolved
Apr 24, 2025, 03:50 AM UTC
Duration
1d
Detected by Pingoru
Apr 23, 2025, 03:39 AM UTC

Affected components

AU hosting region - PaperCut Hive & Pocket

Update timeline

  1. investigating May 07, 2025, 02:56 AM UTC

    We're currently investigating an intermittent issue affecting PaperCut Hive's printing and scanning functionality for the AU data center only. The impacted features are: Integrated Scanning: Users may see errors such as “Failed to get scan destination URL” or “Something went wrong” when performing scan actions. This may affect all or any scan destinations. Print Job Release: Print jobs are being released, but the following error message is shown: “Something went wrong and the jobs weren't able to be printed: Error 502”. We’re actively working with our data center providers to resolve the issues and will provide updates as they become available.

  2. investigating May 07, 2025, 02:57 AM UTC

    Our cloud service provider has identified an issue in their services that is affecting PaperCut Hive and PaperCut Pocket services, with the help of PaperCut engineers. PaperCut engineers will attempt to mitigate the issue while our cloud service provider resolves the issue on their end.

  3. monitoring May 07, 2025, 02:58 AM UTC

    Our Cloud Service Provider has performed mitigations to provide a partial resolution, resulting in stability. We are awaiting a permanent fix and will continue to monitor the situation. Should you experience any latency or loss of functionality, please report this via https://www.papercut.com/support/

  4. monitoring May 07, 2025, 02:59 AM UTC

    Our cloud provider has resolved the platform issue, and full functionality has now been restored.

  5. resolved May 07, 2025, 03:00 AM UTC

    This incident has been resolved.