История сбоев Spiceworks

1. 27 октября 2026 г. в 12:27 UTCinvestigating

   Мы знаем, что некоторые пользователи не могут загрузить Cloud Help Desk и увидеть ошибку «Этот сайт не может быть достигнут» (ERR TIMED OUT) в своем браузере. Сервис работает и работает нормально для большинства пользователей. Проблема ограничивается определенными сетями или интернет-провайдерами. Обработка: если вы пострадали, попробуйте другую сеть, такую как мобильная точка доступа, домашнее соединение или VPN. Несколько пострадавших пользователей восстановили доступ таким образом. Мы работаем с нашим сетевым провайдером, чтобы найти и устранить причину. Чтобы помочь нам в расследовании, пожалуйста, свяжитесь со службой поддержки: Ваша страна и интернет-провайдер (или вы находитесь в корпоративной или VPN-сети) Когда вы впервые увидели ошибку Мы опубликуем еще одно обновление, как только узнаем больше.

2. 27 октября 2026 г. в 13:27 UTCinvestigating

   Мы продолжаем расследование этого вопроса.

3. 27 октября 2026 г. в 13:30 UTCinvestigating

   Мы определили причину этого вопроса. Cloudflare, наш сетевой провайдер, подтвердил сторонние проблемы, влияющие на некоторые брандмауэры поставщиков после недавнего обновления прошивки. Когда трафик проходит через затронутый брандмауэр, брандмауэр блокирует соединение при его проверке, и браузер показывает «Этот сайт не может быть достигнут» (ERR TIMED OUT). Сеть Cloud Help Desk и Cloudflare работает нормально, и ваши данные не затронуты. Вот почему проблема затрагивает только некоторых пользователей и почему коммутационные сети восстанавливают доступ. Инцидент с облачными вспышками: https://www.cloudflarestatus.com/incidents/dk2obcyw2aew Что вы можете сделать: Свяжитесь с вашей ИТ-командой или поставщиком брандмауэра и поделитесь инцидентом Cloudflare выше. Если ваш брандмауэр недавно получил обновление прошивки, ему может потребоваться откатить его, применить исправление поставщика или исключить on.spiceworks.com из проверки HTTPS / SSL. Обход: Подключение из сети, которая не проходит через этот брандмауэр, например, мобильная точка доступа или домашнее соединение. Поскольку исправление должно быть сделано в конфигурации затронутого брандмауэра, мы не можем решить эту проблему с нашей стороны. Мы отслеживаем инцидент с Cloudflare и будем публиковать обновления здесь.

4. 27 октября 2026 г. в 16:21 UTCmonitoring

   Cloudflare подтвердила, что проблема, вызывающая тайм-ауты соединения (ERR TIMED OUT/ERR EMPTY RESPONSE) для некоторых пользователей, была решена по состоянию на 20:42 IST 27 октября 2026 года. Услуги работают нормально. Мы будем следить с нашей стороны, чтобы все оставалось стабильным. Если у вас все еще есть проблемы с подключением, пожалуйста, обновите свой браузер или очистите его кэш. Свяжитесь с нашей службой поддержки, если проблема продолжится. Мы опубликуем окончательное обновление, как только подтвердим, что все стабильно.

5. 27 октября 2026 г. в 18:52 UTCresolved

   За последние несколько часов мы не видели никаких дальнейших сообщений по этому вопросу и рассматриваем возможность его решения. Если вы все еще испытываете проблему, сообщите нам об этом по адресу [email protected]

Автоматический перевод официального обновления инцидента.

1. 22 июля 2026 г. в 17:04 UTCinvestigating

   Мы изучаем сообщения о периодических страницах ошибок и общей деградации производительности, влияющих на Cloud Help Desk. Наши инженеры и команды DevOps активно определяют первопричину и степень воздействия. Обновления будут сделаны здесь, как только они появятся.

2. 22 июля 2026 г. в 19:45 UTCresolved

   Мы не видели дополнительных доказательств этого вопроса. Будет проведена дальнейшая работа по определению того, может ли группа событий вызвать это состояние и как смягчить его. Пожалуйста, сообщите [email protected], если вы видите страницы ошибок / сообщения или чрезмерно медленную загрузку страницы в Cloud Help Desk.

Автоматический перевод официального обновления инцидента.

1. 22 июня 2026 г. в 14: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. 22 июня 2026 г. в 15: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. 22 июня 2026 г. в 19: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. 27 мая 2026 г. в 13: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. 27 мая 2026 г. в 14:44 UTCidentified

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

3. 27 мая 2026 г. в 15: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. 27 мая 2026 г. в 19: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. 28 апреля 2026 г. в 15: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. 28 апреля 2026 г. в 19: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. 30 апреля 2026 г. в 18: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. 3 марта 2026 г. в 14:09 UTCinvestigating

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

2. 3 марта 2026 г. в 18: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. 3 марта 2026 г. в 20: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. 2 января 2026 г. в 09: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. 2 января 2026 г. в 09:32 UTCinvestigating

   We are continuing to investigate this issue.

3. 2 января 2026 г. в 19: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. 4 января 2026 г. в 02:40 UTCidentified

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

5. 5 января 2026 г. в 14: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. 6 января 2026 г. в 02: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. 7 января 2026 г. в 03: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. 7 января 2026 г. в 19: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. 8 января 2026 г. в 09: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. 8 января 2026 г. в 18: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. 20 октября 2025 г. в 09: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. 21 октября 2025 г. в 07:41 UTCresolved

   This has now been resolved.

1. 8 октября 2025 г. в 14: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. 8 октября 2025 г. в 14: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. 7 октября 2025 г. в 13: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. 9 октября 2025 г. в 19: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. 10 октября 2025 г. в 07:20 UTCmonitoring

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

4. 17 октября 2025 г. в 14: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. 4 ноября 2025 г. в 14: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. 8 сентября 2025 г. в 14:23 UTCinvestigating

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

2. 8 сентября 2025 г. в 15: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. 8 сентября 2025 г. в 18: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. 19 июля 2025 г. в 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. 19 июля 2025 г. в 15:32 UTCresolved

   The maintenance is complete and transactional email operational.

1. 16 мая 2025 г. в 17: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. 21 мая 2025 г. в 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. 5 мая 2025 г. в 18:23 UTCinvestigating

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

2. 5 мая 2025 г. в 19:15 UTCinvestigating

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

3. 6 мая 2025 г. в 13:19 UTCinvestigating

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

4. 2 июня 2025 г. в 18: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. 10 июня 2025 г. в 16: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. 11 июня 2025 г. в 13: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. 25 июня 2025 г. в 15: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. 20 марта 2025 г. в 13: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. 21 марта 2025 г. в 13: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. 13 марта 2025 г. в 14: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. 13 марта 2025 г. в 15: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. 13 марта 2025 г. в 16: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. 20 февраля 2025 г. в 13: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. 25 февраля 2025 г. в 15: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. 21 января 2025 г. в 15: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. 21 января 2025 г. в 17: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. 21 января 2025 г. в 20: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. 7 января 2025 г. в 21: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. 6 января 2025 г. в 13: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.