Spiceworks 中断历史

1. 2026年10月27日 UTC 12:27investigating

   我们意识到有些用户无法加载Cloud帮助台, 该服务对大多数用户来说是正常的。 这个问题似乎仅限于某些网络或互联网供应商。 工作:如果你受到影响,请尝试不同的网络,比如移动热点、家用连接或VPN。 一些受影响的用户恢复了这种访问方式。 我们正与网络供应商合作, 为了帮助我们进行调查,请与下列机构联系支助: - 贵国和互联网供应商(或你是否在公司或VPN网络上) - 你第一次看到错误的时候 只要我们知道更多情况.

2. 2026年10月27日 UTC 13:27investigating

   我们正在继续调查这一问题.

3. 2026年10月27日 UTC 13:30investigating

   我们已找出这个问题的原因。 我们的网络供应商Cloudflare证实,在最近一个固件升级后,第三方问题影响到某些供应商防火墙。 当流量通过受影响的防火墙时,防火墙在检查时会阻断连接,浏览器显示“这个站点无法到达”(ERR TIMED OUT). Cloud帮助台和Cloudflare的网络正常运行,您的数据不会受到影响。 这就是为什么这个问题只影响一些用户,以及切换网络恢复访问的原因. 云浮事件:https://www.cloudflarestatus.com/incicents/dk2obcyw2aew 你可以做点什么: 联系你的IT团队或防火墙供应商 分享上面的Cloudflare事件 如果你的防火墙最近有固件更新,他们可能需要将其回滚,应用一个供应商固定,或者从HTTPS/SSL检查中排除.spiceworks.com. 工作绕道:从一个不通过防火墙的网络连接,例如移动热点或家用连接。 我们无法解决此事。 并发布最新消息.

4. 2026年10月27日 UTC 16:21monitoring

   我们的上游供应商Cloudflare证实,2026年10月27日20:42 IST解决了导致部分用户连接超时的问题(ERR TIMED OUT /ERR EMPTY RESPONSE). 服务正常。 我们从头开始监控 确保一切稳定 如果您仍然无法连接, 请刷新您的浏览器或清除其缓存 。 如果问题继续存在,请联系我们的支助小组。 一旦我们确认一切稳定,我们将公布最后更新.

5. 2026年10月27日 UTC 18:52resolved

   在过去几个小时里,我们没有看到关于这个问题的进一步报告,并且正在考虑解决这个问题。 如果您仍在经历这个问题, 请让我们知道@spiceworks.com

自动翻译自官方事件更新。

1. 2026年7月22日 UTC 17:04investigating

   我们正在调查影响云端服务台的间歇性错误页和一般性能退化的报告。 我们的工程团队和DevOps团队正在积极确定影响的根源和程度. 我们一有消息就马上通知你.

2. 2026年7月22日 UTC 19:45resolved

   我们没有看到进一步的证据 这个问题。 将开展进一步工作,以确定一组事件是否会造成这种情况,以及如何减轻这种情况。 请让支持@ spiceworks.com 了解您是否在 Cloud 服务台看到错误的页面/消息或过慢的页面负载 .

自动翻译自官方事件更新。

1. 2026年6月22日 UTC 14:06investigating

   Our devops and engineering teams are investigating reports that some users are experiencing error pages when trying to access their help desk. Further updates to follow

2. 2026年6月22日 UTC 15:17monitoring

   We isolated the recent help desk access issues to a sudden spike in usage. To fix this, our team is rolling out capacity increases and performance optimizations. We're continuing to monitor closely though for the past 30 minutes global availability has been stable.

3. 2026年6月22日 UTC 19:41resolved

   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.

1. 2026年5月27日 UTC 13:07investigating

   Engineering and our ops team are investigating reports where an "oops" error page is displayed intermittently, along with the page loading but failing to display any tickets.

2. 2026年5月27日 UTC 14:44identified

   We're rolling back the underlying tech change from this morning as it is causing the performance issue.

3. 2026年5月27日 UTC 15:45monitoring

   The rollback is completed and performance has returned to normal. If you are still seeing the issue please let us know at [email protected]

4. 2026年5月27日 UTC 19:51resolved

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

1. 2026年4月28日 UTC 15:14investigating

   We're investigating reports of slow performance and timeouts on the Cloud Help Desk. We've confirmed this is a system-side issue and are working on a fix. Updates to follow.

2. 2026年4月28日 UTC 19:07monitoring

   We have successfully stabilized the Cloud Help Desk. Our teams will be monitoring for any further issues and investigating the root cause. Please submit a ticket via [email protected] if you still encounter excessive latency or timeouts.

3. 2026年4月30日 UTC 18:03resolved

   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].

1. 2026年3月3日 UTC 14:09investigating

   We've received reports of email notifications for tickets being delayed. Engineering are investigating the issue.

2. 2026年3月3日 UTC 18:29monitoring

   A fix has been deployed and the underlying issue is resolved. We are currently processing a backlog of delayed notifications. Delivery times will return to normal once the queue has cleared. Engineering is actively monitoring the recovery and has scaled resources to accelerate processing.

3. 2026年3月3日 UTC 20:52resolved

   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.

1. 2026年1月2日 UTC 09:32investigating

   The development team is currently investigating this issue. The following emails are impacted Ticket notifications New user invites Alert emails User portal access via email link

2. 2026年1月2日 UTC 09:32investigating

   We are continuing to investigate this issue.

3. 2026年1月2日 UTC 19:26identified

   We have identified the root cause of this issue and are actively working on getting the email functionality restored. We will update this status page as we make progress.

4. 2026年1月4日 UTC 02:40identified

   We are still actively working on getting this resolved at the earliest as our top priority.

5. 2026年1月5日 UTC 14:19identified

   Our team is continuing work on the restoration of all email services (notifications, invites, and alerts). Due to the complexity of the restoration process, we cannot provide an exact time for completion yet, but we are making steady progress. We are working closely with our email provider to finalize the necessary steps. We apologize for the frustration this outage is causing your team this morning. We are fully dedicated to restoring full service as quickly as possible.

6. 2026年1月6日 UTC 02:33identified

   We greatly appreciate your patience while we continue to work with our email provider to resolve this issue at the earliest. This remains a top priority for us and we will continue posting status updates here.

7. 2026年1月7日 UTC 03:34identified

   While the issue with our emails is still unsolved, we are making progress in reaching a resolution with our service provider. We will follow up with another update tomorrow.

8. 2026年1月7日 UTC 19:40identified

   Resolution in progress: Outbound email notification issue (external ESP issue) We are continuing to work towards a resolution for the outbound email notification issue in the Spiceworks Cloud Help Desk (CHD). The root cause has been identified within our external email service provider (ESP) rather than our internal systems. Because the issue is localized to the ESP, only outgoing email-related notifications are impacted, and the core CHD platform remains operational. We are working closely with our ESP to complete the restoration process, with the immediate priority of returning full email delivery functionality as quickly as possible. What’s working • The Cloud Help Desk is operational: The core ticketing system remains active and accessible. -- Ticket submissions: End-users can still submit new tickets via email and through the User Portal. Please note that email authentication is affected; see the current limitations below. -- Managing tickets: Admins and technicians can create, update, and resolve tickets within CHD. Current limitations -- Update notifications: Outbound email notifications are not being sent to end-users, admins, or technicians. -- Passwordless User Portal logins: Passwordless logins for end-users to submit tickets via the User Portal are not working -- Admin and technician invitations: New user invitations are not working. Workaround: Contact Spiceworks Support for assistance with onboarding new users (this does not apply to end-users). -- Report notifications. Report completion email notifications are not being sent. Workaround: You can still use exports, but you will not receive an email when they’re ready. Simply refresh the page, and the download button will activate when the export is available. We are finalizing the remaining steps with our ESP and believe a resolution is near. Another update will be provided shortly. We sincerely apologize for the disruption this has caused your team’s workflow. We understand the critical importance of email notifications in maintaining effective communication with your end-users, and we truly appreciate your patience and continued support as we work to restore full functionality.

9. 2026年1月8日 UTC 09:25monitoring

   Email services have been restored. Our engineering team is currently monitoring the situation closely to ensure continued stability across all systems as services return to normal. We understand that you may have questions about the cause of this disruption. We are currently conducting a full review of the incident and will share more information once our investigation is complete. Thank you for your patience while we worked to resolve this issue with our service provider.

10. 2026年1月8日 UTC 18:11resolved

    Following 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 officially moving this incident to "Resolved." All email-dependent features are now functioning as expected, including: • Ticket Notifications: End-users, admins, and technicians are receiving ticket update emails • User Access: Passwordless User Portal login links (magic links) are working • Onboarding: New admin and technician invitations are being sent successfully. • Reporting: Email notifications for report completions are being delivered correctly. We are now shifting our focus to a comprehensive review of the email service provider (ESP) disruption to ensure long-term stability and to prevent a recurrence. We sincerely apologize for the disruption this incident caused to your workflows and deeply appreciate your patience and understanding throughout the resolution process. Thank you for your continued support.

1. 2025年10月20日 UTC 09:55monitoring

   Cloud Help Desk has been affected by the issues with Amazon Web Services https://health.aws.amazon.com/health/status. Amazon has reported that most requests are now completing and in our testing Cloud Help Desk is back up and running. We are continuing to monitor the situtation.

2. 2025年10月21日 UTC 07:41resolved

   This has now been resolved.

1. 2025年10月8日 UTC 14:10investigating

   We're seeing reports that the management web page for connectivity dashboard is failing to load. Engineering have been made aware and are investigating.

2. 2025年10月8日 UTC 14:52resolved

   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]

1. 2025年10月7日 UTC 13:29identified

   Following reports of push notifications not being sent for the mobile app, engineering have identified the likely cause. Work is underway to fix this as soon as possible.

2. 2025年10月9日 UTC 19:44identified

   Our engineering team is actively working on resolving the issue with push notifications but we don't have an ETA for a fix yet. This remains a high priority, and we will provide another update as soon as more information is available. We apologize for the continued inconvenience.

3. 2025年10月10日 UTC 07:20monitoring

   Notifications are back up and running. We are continuing to monitor the situation.

4. 2025年10月17日 UTC 14:56identified

   We're seeing a small number of users reporting the issue started to happen again today. We reproduced it with an in house device and engineering are looking into the issue.

5. 2025年11月4日 UTC 14:34resolved

   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]

1. 2025年9月8日 UTC 14:23investigating

   Engineering are investigating reports of slow/failed page loads. We will update this page as information becomes available.

2. 2025年9月8日 UTC 15:13monitoring

   The page load issue is now resolved and our teams are monitoring to ensure stability continues. Please let us know at [email protected] if you're still experiencing this problem

3. 2025年9月8日 UTC 18:08resolved

   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.

1. 2025年7月19日 UTC 11:24investigating

   The maintenance, which began at 12:30AM EDT, did not proceed as planned, and our systems remain offline. Current Impact: * Multi-Factor Authentication (MFA) for login remains temporarily disabled. You will still be able to log in using your username and password, but the second authentication step will not be required. * New account registration remains suspended. * All transactional emails (e.g., password resets, change email address) are currently not being sent. Our engineering team is actively investigating the issue with the highest priority and is working to restore full service as quickly as possible.

2. 2025年7月19日 UTC 15:32resolved

   The maintenance is complete and transactional email operational.

1. 2025年5月16日 UTC 17:22investigating

   The engineering team is investigating. Users have mentioned this affecting chrome/chromium browsers but not Firefox. You may also be able to log into the community or cloud help desk first, and then navigate to https://apps.spiceworks.com/tools/device-inventory/ directly

2. 2025年5月21日 UTC 12:29resolved

   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.

1. 2025年5月5日 UTC 18:23investigating

   The engineering team has been notified and are investigating the issue.

2. 2025年5月5日 UTC 19:15investigating

   The backlog for reports has now cleared and it appears they are being processed normally.

3. 2025年5月6日 UTC 13:19investigating

   Investigation is still ongoing as we saw this issue for a period of time again this morning.

4. 2025年6月2日 UTC 18:33identified

   Engineering have a potential fix that will be applied late Wednesday June 4th (Central US time). The impact of this will be monitored to establish if additional work is required.

5. 2025年6月10日 UTC 16:45identified

   Monitoring indicates the potential fix did not improve the issue. Engineering are treating this as a priority and will deploy additional logging tomorrow, in order to better trap the root cause of the issue.

6. 2025年6月11日 UTC 13:57identified

   The root cause of this issue has been identified. A fix is being developed in the current sprint. A further update will be made once that code is tested and deployed.

7. 2025年6月25日 UTC 15:33resolved

   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]

1. 2025年3月20日 UTC 13:57investigating

   While trying to improve deliverability of these emails, we wanted to communicate two things to folks which may help. 1. If you are stuck with a locked account from retrying codes or getting MFA emails in the wrong order, doing a password reset from our login page and changing your password will also unlock the account. This will save you waiting on support to unlock your account. 2. If you use Mimecast, its "greylisting" feature may be delaying these new MFA emails. More on that here https://community.spiceworks.com/t/cloud-help-desk-release-notes-mar-19-2025-mfa-for-cloud-help-desk-employee-accounts-is-here/1186674/14?u=craig-spiceworks

2. 2025年3月21日 UTC 13:16resolved

   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]

1. 2025年3月13日 UTC 14:22investigating

   We have notified our ops team of an issue where the cloud help desk intermittently displays a "bad gateway" or similar error. An investigation is underway.

2. 2025年3月13日 UTC 15:00monitoring

   We're seeing stability restored to the app. Please let us know at [email protected] if you are still having this issue.

3. 2025年3月13日 UTC 16:16resolved

   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]

1. 2025年2月20日 UTC 13:50investigating

   Our engineering teams are investigating an issue where some Spiceworks emails are not being sent out. Cloud help desk emails for tickets are unaffected as these use a different system.

2. 2025年2月25日 UTC 15:19resolved

   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.

1. 2025年1月21日 UTC 15:59identified

   Our development team is working on a fix for this issue. New users may not be able to complete their Spiceworks profile during signup. We have reports that Cloud help desk logins will work via a web or mobile web browser, but you will see an error while trying to login to the mobile app.

2. 2025年1月21日 UTC 17:14monitoring

   A fix has been posted. If you're still seeing the error when signing up, please let us know by emailing [email protected]

3. 2025年1月21日 UTC 20:13resolved

   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.

1. 2025年1月7日 UTC 21:59resolved

   This is not an outage, just to inform folks of the change with multiple communication methods. To improve account security and align with industry best practices, we are introducing a 7-day expiration period for session tokens for the Spiceworks Cloud Help Desk (CHD). Why This Change? This update reduces the risk of unauthorized access from stale or compromised tokens, ensuring enhanced protection for your accounts and data. What You Need to Know This update will take effect on January 8, 2025, and you will be required to log in on your first session after that update. Active sessions will remain valid for up to 7 days from the time of issuance. Expired tokens will trigger a logout, and you’ll be prompted to log in again. After expiration, users will be required to log in again to authenticate and obtain a new session token. This is specifically for CHD and our other IT tools; this will not affect your Spiceworks Community session token. This will only affect users who need to log into Cloud Help Desk and should not affect the end-users that you support. If you do not remember your password, you can reset it by going to your Spiceworks Account Management page. https://accounts.spiceworks.com/ If you have questions or need assistance with this change, please contact our Support Team by posting in the Cloud Help Desk support area or opening a support ticket by emailing [email protected]. Thank you for helping us maintain a secure environment for all members and users.

1. 2025年1月6日 UTC 13:23resolved

   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.