Spiceworks Outage History

We 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 [email protected] know if you are seeing error pages/messages or excessively slow page load in Cloud Help Desk.

No further instances of page load issues have been reported or reproduced so we're considering this issue resolved. Please let [email protected] know if you are still seeing this issue.

No further issues have been detected. The engineering team is analyzing the root cause to ensure future stability before the code change is redeployed.

We 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 a high-volume surge of API requests from a third-party data tool. This created an unexpected load on our database, specifically impacting the ticket queue and reporting sections. Prevention: To prevent a recurrence, we have implemented new traffic controls and rate-limiting measures. We will continue to monitor these systems to ensure long-term stability. If you are still experiencing any issues, please let our team know at [email protected].

We 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 delays, some users may receive 1-2 duplicate notifications for older tickets. We appreciate your patience with this temporary "noise". If you continue to experience new delays, please contact us at [email protected] so we can investigate further.

This has now been resolved.

Engineering were able to establish the root cause of this issue and implement a fix. Testing shows normal service is restored. If you're still seeing issues, try clearing your browser cache first. If the error still occurs, please open a ticket at [email protected]

We kept this open to ensure the issue did not affect even a small number of users. The issue is now resolved and we've seen no further reports. If you are still seeing an issue with your mobile app notifications, please open a ticket at [email protected]

We're seeing no further issues and are considering this resolved. Please reach out to [email protected] if you're still seeing page load/timeout issues with cloud help desk.

The maintenance is complete and transactional email operational.

Code has been rolled back that was causing this issue. Our engineering team will establish a suitable fix so that the code can be redeployed at a later date.

A fix has been implemented and affected users with support tickets have confirmed it is effective. If you are still seeing this issue please submit a ticket with [email protected]

We're seeing lower ticket volumes today and it appears email filters are getting "used" to the new emails. If you are still having issues, let us know at [email protected]

Testing here and feedback from users is that we're back to full strength. The root cause appears to have been a network related issue causing the pods running cloud help desk to fail. We're altering the alerting mechanisms to give us more advance notice of this in future, so we can further avoid or minimize disruption. Apologies for the hassle! If you are still seeing issues, please get in touch with us at [email protected]

We have been monitoring a fix for this issue which appears to have been successful. Please email [email protected] if you are still having issues.

Feedback from affected folks indicate this issue has been resolved. If you were affected by this issue, our dev team would really like to get the results of the following URL's to ensure we prevent it in future. Results from visiting https://community.spiceworks.com/.well-known/conninfo IPv4 address from ip4.discourse.org IPv6 address from ip6.discourse.org Please send those results to [email protected] with the subject line "Registration Issue IP information". Thank you and sorry for the hassle.

Our dev ops team has resolved this issue and feedback from the community shows access is restored. We apologize for the inconvenience. If you are still seeing the SSL error when logging into the help desk or browsing help desk pages, please let [email protected] know.

Indications from users testing, and our internal tests show the fix is effective.

Agent updates are now flowing through normally. No action should be necessary on devices running the agent. Agents automatically retry on a set interval, so any failed attempts to push data will simply resend. You should see Connectivity Dashboard stats for online devices, now. Inventory online data updates should recover on the normal refresh interval.