Deskpro Status

All Systems Operational

Admin Interface Operational

Agent Interface Operational

User Interface / Portal Operational

Reports Interface Operational

Billing Interface Operational

API Operational

Incoming Email Operational

Outgoing Email Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Past Incidents

Jul 27, 2026

Potential authentication issues with Google Auth on cloud sites

Resolved - This incident has been resolved.
Jul 27, 14:42 BST

Monitoring - A temporary fix has been implemented for those who have been affected. We are currently working on a longer term fix.
Jul 24, 12:46 BST

Identified - The issue has been identified an we are working on a fix.
Jul 24, 11:26 BST

Investigating - We are currently investigating reports of authentication issues using Google SSO. Other methods of authentication seem to be unaffected.
Jul 24, 10:27 BST

Jul 26, 2026

No incidents reported.

Jul 25, 2026

No incidents reported.

Jul 24, 2026

Jul 23, 2026

No incidents reported.

Jul 22, 2026

No incidents reported.

Jul 21, 2026

No incidents reported.

Jul 20, 2026

No incidents reported.

Jul 19, 2026

No incidents reported.

Jul 18, 2026

No incidents reported.

Jul 17, 2026

No incidents reported.

Jul 16, 2026

No incidents reported.

Jul 15, 2026

Service disruption during scheduled maintenance

Resolved - Between 7:30am and 7:44am BST this morning, access to Deskpro was degraded for approximately 14 minutes. The disruption occurred during scheduled infrastructure maintenance, part of our ongoing hardening work following the recent service incident. The maintenance took longer to apply than anticipated. Service was fully restored at 7:44am and all systems are operating normally. No data was lost or affected.
Jul 15, 07:30 BST

Jul 14, 2026

No incidents reported.

Jul 13, 2026

Intermittent errors and slow performance

Resolved - Between approximately 13:36 and 14:15 BST, some customers experienced errors and slow performance when using Deskpro. This was caused by an issue with one of our database servers. Our team identified the affected server and rerouted traffic away from it, restoring normal performance. We've opened an investigation with our infrastructure provider to determine the root cause.
Jul 13, 13:30 BST