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

Spiceworks Outage History

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

There were 103 Spiceworks outages since March 2019. The 9 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Major May 27, 2026

May 2026: Cloud Help Desk - Ticket queues not loading or server error page

Detected May 27, 2026 9:07 AM EDT · Resolved May 27, 2026 3:53 PM EDT · Duration about 7 hours

Spiceworks Cloud Help Desk experienced a major outage for 6.8 hours where users encountered intermittent "oops" error pages and ticket queues that failed to load or display tickets. The issue was caused by an underlying technology change deployed that morning, which the engineering team identified and rolled back to restore normal performance. The incident was fully resolved after monitoring confirmed no further issues were detected.

Minor April 28, 2026

April 2026: Cloud Help Desk Intermittent slow page loading

Detected Apr 28, 2026 11:14 AM EDT · Resolved Apr 30, 2026 2:05 PM EDT · Duration 2 days

Spiceworks Cloud Help Desk experienced intermittent slow page loading and timeouts for 50.8 hours due to a high-volume surge of API requests from a third-party data tool that overloaded the database. The excessive load specifically impacted ticket queue and reporting sections, causing performance degradation for users. The service was stabilized and the incident resolved after implementing new traffic controls and rate-limiting measures to prevent future occurrences.

Minor March 3, 2026

March 2026: Cloud Help Desk Delayed email notifications

Detected Mar 3, 2026 9:09 AM EST · Resolved Mar 3, 2026 4:04 PM EST · Duration about 7 hours

Spiceworks Cloud Help Desk experienced delayed email notifications for tickets over a 6.8-hour period. Engineering deployed a fix and scaled resources to process the backlog of delayed notifications. The issue was resolved with notification delivery returning to normal, though some users may receive 1-2 duplicate notifications for older tickets due to the retry logic handling the initial delays.