All Systems Operational

About This Site

Find out about service interruptions and maintenance windows for PaperCut's online services. For issues not directly related to a service outage, take a look at our Known Issues page. If you're looking for general help with any of our products, our Help Center can hopefully answer your questions!

Uptime over the past 90 days. View historical uptime.
PaperCut Pocket & PaperCut Hive Operational
90 days ago
99.61 % uptime
Today
Scan to Cloud for PaperCut MF Operational
90 days ago
100.0 % uptime
Today
Cloud Document Processing for PaperCut MF Operational
90 days ago
99.87 % uptime
Today
Cloud Print for PaperCut Mobility Print Operational
90 days ago
99.83 % uptime
Today
Multiverse Operational
90 days ago
100.0 % uptime
Today
Public Website (www.papercut.com) Operational
90 days ago
99.87 % uptime
Today
Order System (buy.papercut.com) Operational
90 days ago
100.0 % uptime
Today
Partner Portal (portal.papercut.com) Operational
90 days ago
99.89 % uptime
Today
Training (learn.papercut.com) Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Past Incidents
May 26, 2022

No incidents reported today.

May 25, 2022

No incidents reported.

May 24, 2022
PaperCut Pocket and Hive - Performance Degradation
Resolved - Customers experienced intermittent performance issues when using Integrated Scanning and Print Release. This was caused by an incident on Google App Engine. More information on this can be found here https://status.cloud.google.com/incidents/rrmfPRaESXcrpfxPo5y6
May 24, 02:00 UTC
May 23, 2022

No incidents reported.

May 22, 2022

No incidents reported.

May 21, 2022

No incidents reported.

May 20, 2022

No incidents reported.

May 19, 2022

No incidents reported.

May 18, 2022

No incidents reported.

May 17, 2022
PaperCut Hive - print release not working on embedded devices
Resolved - Customers using print release from embedded devices were not able to release print jobs. This incident impacted the release of jobs from embedded devices only, and did not impact the release of jobs from the mobile app. Scanning and other device functions were also not impacted by this incident.

Users would have received 'error 502' at the device when trying to release print job(s).

This incident has now been resolved, and print release functionality has been fully restored.
May 17, 02:45 UTC
May 16, 2022

No incidents reported.

May 15, 2022

No incidents reported.

May 14, 2022

No incidents reported.

May 13, 2022

No incidents reported.

May 12, 2022
PaperCut Pocket and Hive - Performance Degradation
Resolved - While we continue to improve the performance of PaperCut Pocket & Hive, we have returned the system to full functionality.

Until the root cause is resolved, there is potential for slower than usual printing performance to return, however we have identified changes and optimisations to the product to improve overall stability and latency.

Even though this specific incident is now closed, our work with Google and our cloud provider continues with the same urgency.

[Update 13th May AEST] The root cause of the issue has been resolved by Google and all systems are back to normal.
May 12, 03:30 UTC
Update - We are working closely with Google to identify the root cause of the performance issue and continue to deploy updates to PaperCut Pocket and Hive to minimise customer impact.
May 10, 23:09 UTC
Identified - We are continuing to work with Google and our cloud provider to determine the root cause of this performance issue.

In the meantime, the team is updating the PaperCut Pocket and Hive services to make them more resilient - and minimise the effect of these upstream provider issues.
May 9, 06:37 UTC
Investigating - PaperCut Pocket and Hive are experiencing intermittent timeouts in printing and within the admin interface.

We are working with our cloud provider to identify the root cause.
May 9, 00:00 UTC
← Incident History Powered by Atlassian Statuspage