7shifts Outage History

18 incidents recorded over the last 365 days, 18 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Every Recorded 7shifts Incident

7shifts incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 23, 2026We will be performing planned database maintenance impacting 7shifts payroll onlyMaintenance has started15h 4mResolved
Oct 7, 2026Delays in schedule data updatingThe issue with schedule data updating in the app has been resolved. Schedule data and projected hours are updating normally. We appreciate your patience while our team worked on this.21 minResolved
Oct 3, 2026Delayed sales and labor integration dataSales, labor, and tips integrations should be back to normal.28h 54mResolved
Sep 14, 2026Regular MaintenanceMaintenance has started39h 48mResolved
Aug 31, 2026Login Unavailable for Some UsersThe login issue affecting some mobile users has been resolved. If you're still experiencing problems, please don't hesitate to reach out.21h 30mResolved
Jul 8, 2026Scheduling PageThe scheduling page is now fully operational.9 minResolved
Jul 1, 20267shifts iOS app content not loading on version 2026.27.0This issue is resolved in 7shifts iOS version 2026.27.2 which is available for download in the App Store. Thank you all for your patience.24h 45mResolved
Jun 30, 2026Some mobile customers may be experiencing a degraded experience with Clair servicesThe Clair endpoints are now returning expected status codes after resolving a bug in our cache. All systems should now be operational.30 minResolved
Jun 18, 20267shifts Payroll Delayed Employee PaymentsAll instant payments scheduled for yesterday have been successfully processed.21h 50mResolved
May 27, 2026Error Logging InService is back to normal.18 minResolved
May 21, 2026Our team is currently investigating an issue with 7shifts Messaging. In-app messaging will be temporarily unavailable while we work to restore service as quickly as possible.Our team has successfully resolved the issue with 7shifts Messaging. In-app messaging is now fully operational. We appreciate your patience!1h 30mResolved
Apr 6, 20267punches on iPad continuous loading / won't openThis incident has been marked as resolved by our Engineering Team18h 38mResolved
Apr 6, 2026Performance DegradationThe issue has been resolved. Performance in the application has been restored.13 minResolved
Feb 25, 2026Deactivating Employees – Error MessageThe issue affecting employee deactivations has now been resolved. You can proceed with deactivating employees as expected. If you continue to experience any issues, please reach out to our Support team for…17 minResolved
Jan 26, 2026W-2 Download Error**W-2s will begin appearing by the end of January 27th as processing completes.** During this time, some accounts may see an “unknown error” when attempting to download a W-2.5h 15mResolved
Jan 14, 2026Currently experiencing delays in SMS delivery to Verizon Wireless users No longer experiencing delays in SSM/MMS to Verizon Wireless customers16h 51mResolved
Nov 18, 2025Cloudflare DownCloudflare has confirmed that services are operating normally, and users should no longer experience access issues.3h 26mResolved
Nov 11, 2025Lightspeed Series-K Integration: Sales not importing into 7shifts for Canadian Customers The scope of affected accounts has been found to be very small (1-2). Therefore, no widespread issues are reported for sales impacting Lightspeed-K integrations and we will be marking this issue as resolved.21h 4mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next 7shifts incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This 7shifts Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before 7shifts acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single 7shifts outage in this window ran 1d 15h, against a mean recovery of 12h 15m. If you depend on 7shifts in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.