Spiceworks 장애 기록

1. 2026년 10월 27일 오후 12:27 UTCinvestigating

   Cloud Help Desk를 로드할 수 없으므로 브라우저에서 "이 사이트는 도달 할 수 없습니다"(ERR TIMED OUT) 오류를 참조하십시오. 이 서비스는 대부분 사용자를 위해 정상적으로 실행되고. 문제는 특정 네트워크 또는 인터넷 공급자로 제한됩니다. Workaround: 영향을 받으면 모바일 핫스팟, 홈 연결 또는 VPN과 같은 다른 네트워크를 시도하십시오. 몇몇 영향을 받은 사용자는 이 방법을 복원했습니다. 우리는 우리의 네트워크 공급자와 함께 일하고 원인을 해결합니다. 조사를 돕기 위하여는, 지원에 접촉하십시오: - 귀하의 국가 및 인터넷 공급자 (또는 기업 또는 VPN 네트워크에 있는지 여부) - 처음 오류를 보았습니다. 우리는 우리가 더 알고 있기 때문에 또 다른 업데이트를 게시합니다.

2. 2026년 10월 27일 오후 1:27 UTCinvestigating

   이 문제를 조사하고 있습니다.

3. 2026년 10월 27일 오후 1:30 UTCinvestigating

   이 문제의 원인을 확인했습니다. Cloudflare, 우리의 네트워크 제공 업체, 최근 펌웨어 업그레이드 후 특정 공급 업체 방화벽에 영향을 미치는 타사 문제를 확인했습니다. 트래픽이 영향을받는 방화벽을 통과하면 방화벽은 연결을 차단하고, 브라우저는 "이 사이트를 도달 할 수 없습니다"(ERR TIMED OUT)를 보여줍니다. Cloud Help Desk와 Cloudflare의 네트워크는 일반적으로 작동하고 데이터가 영향을 미치지 않습니다. 이것은 왜 문제가 일부 사용자에 영향을 미치는지, 왜 네트워크가 액세스를 복원합니다. Cloudflare 사건 : https://www.cloudflarestatus.com/incidents/dk2obcyw2aew 당신은 무엇을 할 수: IT 팀이나 방화벽 공급 업체에 문의하고 위의 Cloudflare 사건을 공유하십시오. 방화벽이 최근에 펌웨어 업데이트를 받았을 경우, 다시 롤해야 할 수도 있고, 공급 업체 수정을 적용하거나, HTTPS / SSL 검사에서 on.spiceworks.com을 제외한다. Workaround : 모바일 핫스팟 또는 홈 연결과 같은 방화벽을 통해 이동하지 않는 네트워크에서 연결하십시오. 수정이 영향을받는 방화벽의 구성으로 만들어지기 때문에, 우리는 우리의 측에서 이것을 해결할 수 없습니다. 우리는 Cloudflare의 사건을 모니터링하고 여기에 업데이트를 게시합니다.

4. 2026년 10월 27일 오후 4:21 UTCmonitoring

   Cloudflare, 우리의 업스트림 제공 업체는 연결 타임 아웃 (ERR TIMED OUT / ERR EMPTY RESPONSE)이 10 월 27, 2026에 20:42 IST로 해결 된 것으로 확인했습니다. 서비스는 정상적으로 작동됩니다. 우리는 우리의 끝에서 감시를 지키고 모든 것을 안정되어 있다는 것을 확인합니다. 여전히 연결이 문제가 있다면 브라우저를 새로 고침하거나 캐시를 취소하십시오. 문제가 계속되면 지원 팀에 문의하십시오. 우리는 일단 우리가 모든 것을 안정되어 있는 확인한 일단 최종 갱신을 포스트할 것입니다.

5. 2026년 10월 27일 오후 6:52 UTCresolved

   우리는 지난 몇 시간 동안이 문제에 대한 더 많은 보고서를 보았고 해결을 고려하고있다. 문제가 발생하면 [email protected]으로 알려주세요

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 22일 오후 5:04 UTCinvestigating

   Cloud Help Desk에 영향을 미치는 Intermittent 오류 페이지 및 일반 성능 평가 보고서를 조사하고 있습니다. 우리의 엔지니어링 및 DevOps 팀은 뿌리 원인과 영향력의 범위를 적극적으로 결정하고 있습니다. 업데이트는 우리가 그(것)들을 갖기 때문에 여기에서 할 것입니다.

2. 2026년 7월 22일 오후 7:45 UTCresolved

   이 문제의 더 많은 증거를 본 적이 없습니다. 더 많은 작업은 이벤트의 그룹이이 조건을 일으킬 수 있는지 확인하기 위해 착수 될 것이며, 어떻게 그것을 완화합니다. Cloud Help Desk의 오류 페이지/메시지 또는 과도하게 느린 페이지로드를 볼 경우 [email protected] 을 참조하십시오.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 22일 오후 2:06 UTCinvestigating

   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일 오후 3:17 UTCmonitoring

   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일 오후 7:41 UTCresolved

   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일 오후 1:07 UTCinvestigating

   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일 오후 2:44 UTCidentified

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

3. 2026년 5월 27일 오후 3:45 UTCmonitoring

   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일 오후 7:51 UTCresolved

   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일 오후 3:14 UTCinvestigating

   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일 오후 7:07 UTCmonitoring

   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일 오후 6:03 UTCresolved

   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일 오후 2:09 UTCinvestigating

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

2. 2026년 3월 3일 오후 6:29 UTCmonitoring

   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일 오후 8:52 UTCresolved

   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일 오전 9:32 UTCinvestigating

   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일 오전 9:32 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 1월 2일 오후 7:26 UTCidentified

   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일 오전 2:40 UTCidentified

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

5. 2026년 1월 5일 오후 2:19 UTCidentified

   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일 오전 2:33 UTCidentified

   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일 오전 3:34 UTCidentified

   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일 오후 7:40 UTCidentified

   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일 오전 9:25 UTCmonitoring

   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일 오후 6:11 UTCresolved

    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일 오전 9:55 UTCmonitoring

   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일 오전 7:41 UTCresolved

   This has now been resolved.

1. 2025년 10월 8일 오후 2:10 UTCinvestigating

   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일 오후 2:52 UTCresolved

   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일 오후 1:29 UTCidentified

   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일 오후 7:44 UTCidentified

   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일 오전 7:20 UTCmonitoring

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

4. 2025년 10월 17일 오후 2:56 UTCidentified

   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일 오후 2:34 UTCresolved

   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일 오후 2:23 UTCinvestigating

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

2. 2025년 9월 8일 오후 3:13 UTCmonitoring

   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일 오후 6:08 UTCresolved

   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일 오전 11:24 UTCinvestigating

   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일 오후 3:32 UTCresolved

   The maintenance is complete and transactional email operational.

1. 2025년 5월 16일 오후 5:22 UTCinvestigating

   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일 오후 12:29 UTCresolved

   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일 오후 6:23 UTCinvestigating

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

2. 2025년 5월 5일 오후 7:15 UTCinvestigating

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

3. 2025년 5월 6일 오후 1:19 UTCinvestigating

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

4. 2025년 6월 2일 오후 6:33 UTCidentified

   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일 오후 4:45 UTCidentified

   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일 오후 1:57 UTCidentified

   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일 오후 3:33 UTCresolved

   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일 오후 1:57 UTCinvestigating

   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일 오후 1:16 UTCresolved

   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일 오후 2:22 UTCinvestigating

   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일 오후 3:00 UTCmonitoring

   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일 오후 4:16 UTCresolved

   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일 오후 1:50 UTCinvestigating

   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일 오후 3:19 UTCresolved

   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일 오후 3:59 UTCidentified

   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일 오후 5:14 UTCmonitoring

   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일 오후 8:13 UTCresolved

   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일 오후 9:59 UTCresolved

   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일 오후 1:23 UTCresolved

   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.