Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Deputy Outage History

Every past Deputy outage tracked by IsDown, with detection times, duration, and resolution details.

There were 126 Deputy outages since March 2014. The 28 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor April 23, 2026

April 2026: Unable to connect to Xero from Deputy.

Detected Apr 23, 2026 1:47 AM UTC · Resolved Apr 23, 2026 6:46 AM UTC · Duration about 5 hours

Deputy customers experienced an inability to connect to Xero, with some users also unable to reauthorize existing connections. The issue was identified as intermittent connection problems between Deputy and Xero's systems. The incident was resolved after 5 hours through a fix implemented on Xero's side in collaboration with their team.

Major April 6, 2026

April 2026: Schedules and Timesheets unable to approve or publish

Detected Apr 6, 2026 11:47 PM UTC · Resolved Apr 7, 2026 4:10 AM UTC · Duration about 4 hours

Deputy's AU service experienced a major incident where users were unable to approve or publish schedules and timesheets for 4.4 hours. The issue was identified and a fix was implemented, with the service being monitored before full resolution was confirmed.

Minor April 6, 2026

April 2026: Slow loading when publishing a shift

Detected Apr 6, 2026 2:07 AM UTC · Resolved Apr 6, 2026 5:09 AM UTC · Duration about 3 hours

Deputy experienced slow loading and stuck screens when users attempted to publish shifts, lasting 3 hours. Users reported being unable to publish shifts due to infinite loading states. The issue was resolved after implementing a fix and monitoring the results.

Major March 9, 2026

March 2026: Shifts not publishing

Detected Mar 9, 2026 4:27 AM UTC · Resolved Mar 9, 2026 7:20 AM UTC · Duration about 3 hours

Deputy experienced a major incident where shifts failed to publish, affecting the AU region. The issue was resolved after 8 minutes of investigation.