Spiceworks Outage History

16 incidents recorded over the last 365 days, 7 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.

Live Spiceworks status100.00% uptime history

Every Recorded Spiceworks Incident

Spiceworks incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 27, 2026Some users unable to reach Cloud Help DeskWe've seen no further reports of this issue in the past few hours and are considering it resolved. If you are still experiencing the problem, please let us know at support@spiceworks.com6h 24mResolved
Oct 24, 2026Spiceworks Maintenance on Saturday, October 24, 2026 - Cloud Help Desk, Inventory, Connectivity Dashboard, Daily Challenge and User LoginScheduled maintenance is currently in progress. We will provide updates as necessary.2h 0mScheduled
Oct 20, 2026Spiceworks Maintenance on Monday, [October 19, 2026] - www.spiceworks.com Hosting MigrationWe will be undergoing scheduled maintenance during this time.1h 0mScheduled
Oct 20, 2026Spiceworks Maintenance on Monday, [October 19, 2026] - www.spiceworks.com Hosting MigrationStarting at approximately [22:30 PM CST] on Monday, [October 19, 2026], we will migrate www.spiceworks.com to a new hosting platform. We expect the maintenance to last up to [one (1) hour], concluding no later than…1h 0mScheduled
Oct 1, 2026Cloud Help Desk Settings page Maintenance (Settings page only)Scheduled maintenance is currently in progress. We will provide updates as necessary.3h 0mScheduled
Aug 1, 2026Planned Maintenance for Infrastructure - 31st July 2026 - 11:00 PM CDTThe scheduled maintenance has been completed.4h 0mScheduled
Jul 22, 2026Cloud Help Desk - Performance issues, slow page loading and error messagesWe haven't seen further evidence of this issue. Further work will be undertaken to identify whether a group of events can cause this condition, and how to mitigate that. Please let support@spiceworks.com know if you are…2h 41mResolved
Jun 22, 2026Cloud Help Desk - Error page when loading ticketsNo further instances of page load issues have been reported or reproduced so we're considering this issue resolved. Please let support@spiceworks.com know if you are still seeing this issue.5h 34mResolved
Jun 6, 2026Planned Maintenance for Infrastructure - Phase 2 - 6th June 2026 - 8:30 AM CDTThe scheduled maintenance has been completed.30 minScheduled
Jun 6, 2026Planned Maintenance for Infrastructure - Phase 1 - 6th June 2026 - 3:30 AM CDTThe scheduled maintenance has been completed.30 minScheduled
May 27, 2026Cloud Help Desk - Ticket queues not loading or server error pageNo further issues have been detected. The engineering team is analyzing the root cause to ensure future stability before the code change is redeployed.6h 43mResolved
Apr 28, 2026Cloud Help Desk Intermittent slow page loadingWe have seen no further reports of latency or timeouts, and our internal testing confirms that performance remains stable. We are now officially marking this incident as Resolved. Root Cause: The issue was triggered by…50h 48mResolved
Mar 21, 2026Scheduled Maintenance: Spiceworks Cloud Help Desk (CHD) on Saturday March 21, 2026Service Restored: Systems Fully Operational We are pleased to report that the database migration and maintenance for the Spiceworks Cloud Help Desk (CHD) have been completed successfully. All systems are now back…27h 0mScheduled
Mar 3, 2026Cloud Help Desk Delayed email notificationsWe have monitored the system and confirmed that notification delivery has returned to normal. As a result, we are marking this issue resolved. Note on Duplicates: Because of the way our retry logic handled the initial…6h 43mResolved
Jan 31, 2026Scheduled database maintenance on Jan 31, 2026The scheduled maintenance has been completed.2h 0mScheduled
Jan 2, 2026Cloud Help Desk - Outbound email notifications not being sentFollowing a period of stable monitoring, we have confirmed that the outbound email notification issue affecting the Spiceworks Cloud Help Desk (CHD) is fully resolved. All systems are operating normally, and we are…152h 39mResolved

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 Spiceworks 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 Spiceworks 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 Spiceworks 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 Spiceworks outage in this window ran 6d 8h, against a mean recovery of 17h 2m. If you depend on Spiceworks 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.