Is Spiceworks Down Right Now? Check if there is a current outage ongoing.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We will be undergoing scheduled maintenance during this time.

We will perform maintenance on the Settings page for Spiceworks Cloud Help Desk (CHD) starting at approximately 10:30PM CDT June 2, 2025 (3:30AM UTC June 3, 2025).We anticipate this downtime to take no more than 2 hours.During this maintenance, the Settings page will be unavailable and will display a maintenance mode page.No other aspects of the CHD will be affected.No data will be lost, and email processing and all other CHD functions will continue as normal.To keep up-to-date with our progress or any changes, keep an eye on our Status Page.We appreciate your patience and understanding.

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.

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

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

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

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.

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

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

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

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.

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

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.

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

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 support@spiceworks.com

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

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 support@spiceworks.com

We're seeing stability restored to the app. Please let us know at support@spiceworks.com if you are still having this issue.

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.

We have been monitoring a fix for this issue which appears to have been successful. Please email support@spiceworks.com if you are still having issues.

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.

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 support@spiceworks.com with the subject line "Registration Issue IP information". Thank you and sorry for the hassle.

A fix has been posted. If you're still seeing the error when signing up, please let us know by emailing support@spiceworks.com

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.

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 support@spiceworks.com. Thank you for helping us maintain a secure environment for all members and users.

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 support@spiceworks.com know.

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

A fix has been put in place. Please let support@spiceworks.com know if you're still seeing the issue on the "no split" ticket view.

We have reports of slow page load times (or failure to load) when using the back option to move away from a single ticket to the ticket list. The development team is aware of and investigating the issue.

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.

Starting approx 70 minutes ago, agents began to experience delays and error responses when pushing updates. We are working to resolve this issue with handling inbound requests. This impacts all agents for the Inventory online and Connectivity Dashboard products. Viewing device information in Inventory online is unaffected, but new information is delayed. Connectivity Dashboard stats will not be displayed until the issue is resolved.

No new reports and tests have all been successful. Notifications for tickets from around 2:30am central time to 8:20am will need to be sent manually (by admins/techs commenting on tickets) to ensure end users get a notification.

A fix had been deployed and we are monitoring for further issues. Please let support@spiceworks.com know if you are still not receiving email notifications for new tickets.

The development team is currently investigating this issue.

We have been monitoring the health of the application through normal peak traffic today and do not have indication of further issues or new issues associated with email notifications for tickets & ticket comments. Please refer to our post on the Community for more specific details (https://community.spiceworks.com/t/some-new-tickets-not-creating-agent-email-notifications/1091315/20).

At approx. 2024-06-29 0830UTC (~6 hours ago) the long-running fix process completed, and approx. 1030UTC outbound email jobs were restarted. We are evaluating expected behavior related to ticket attachments and email notifications for tickets created during the timeframe between 2024-06-28 1430UTC and 2024-06-29 0830UTC.

We are continuing to work on a fix for the issue. ETA for the fix is multiple hours out, pending a long running process and validation.

We are making changes to address the underlying issue preventing outbound ticket notification emails from firing in some cases. To address this we have temporarily stopped all outbound ticket notification email flow. Inbound email flow and ticket creation should not be impacted. As of now, the issue appears to be scoped to generating download URLs for ticket attachments, which in turn impacts the generation of ticket notification emails.

The issue has been identified and a fix is being implemented.

We've received reports that certain emails are creating tickets successfully in the cloud helpdesk, but notifications are not being sent out to admins or the end user. Our development team is investigating the issue.

Reports coming back indicate users who were affected can now access Spiceworks services. We're closing out this incident as resolved.

Traffic has been re-routed which appears to have solved the issue for those affected. Please test again if you were seeing problems. For any folks who still cannot access Spiceworks apps send the following information to support: Your external IP address A traceroute result for on.spiceworks.com

Research is ongoing with our edge network support. Thanks for your patience. As before, please report to support@spiceworks.com if you have not already done so.

Please continue to report issues if you have not already. Based on user reports the impacted users are primarily in northeastern US on a few different ISPs. We are working with our edge network provider to determine whether there are configuration changes we can make, or if impacted users' ISPs have necessary changes.

The issue with the inability to login persists despite the initial thought it had been resolved. Please continue to monitor this page for updates.

We are no longer receiving reports of connectivity issues. Based on our testing, while services were accessible for most users, some internet service providers were unable to route traffic to our edge network, resulting in connection timeout errors. If you are currently unable to reach any spiceworks.com site, please reach out to let us know by contacting support@spiceworks.com (or by updating your existing case if you reached out in the past few hours).

Developers are currently investigating an issue that is preventing some users from connecting to the Cloud Help Desk and Inventory. We'll update this page as soon as more is known about this issue.

This incident has been resolved.

It appears that there's still investigation needed to resolve this issue. If you experience this issue, you can create a ticket with Support but please include a screenshot of the error, including the IP address and Incident ID.

Further adjustments have been made which seems to have resolved the issue. If you're still getting Error 15 pages after UTC 19:20, let support@spiceworks.com know. It is helpful if you can screenshot the error for the incident ID and timestamp.

We've made changes to mitigate this error. Please let us know at support@spiceworks.com if you continue to see the error 15 message.

We're seeing reports from users getting this error often shortly after logging in. We've made the dev ops team aware and are investigating a solution.

The issue has been resolved for new accounts. All affected existing accounts have been fixed where needed. Please email support@spiceworks.com if you email your new help@orgname.on.spiceworks.com address and get a "550 No Such User" response.

We have reports that new cloud help desk accounts return the above error when emails are sent to the help@orgname.on.spiceworks.com address. The development team is looking into the cause.

The Community experienced service disruption over a period of ~90 minutes starting Apr 1, 2024 @ 0800 CDT. During this timeframe visitors were seeing the maintenance page while we investigated and worked to resolve the interruption. We were able to mitigate excessive/DDoS traffic and bring the Community back online at ~0925 CDT.

With the fix released during this (https://status.spiceworks.com/incidents/c32mg0pxf7lz) maintenance outage, this issue is resolved.

The ability to import a json file to bulk create tickets is not currently working. Import file uploads are successful, but the processing of the file to create tickets and users is not working. (Note the impact is limited to the bulk import feature, typically only used as a part of initial account set up, when migrating to the Cloud Help Desk.)

Reports back from folks affected show the rollback was effective and portal ticket submission is now working normally. If you are still experiencing issues submitting tickets from the end user portal, please let us know at support@spiceworks.com

A code change has been rolled out and we're asking affected users to test portal ticket submission once more. Let us know at support@spiceworks.com if you're still seeing the issue.

We're looking into reports that tickets cannot be submitted on the end user portal.

Nearly all of our previously delayed automated tests have now delivered, indicating we are nearly fully caught up with delivery of inbound emails. There are no indications of ongoing delays of new emails. We will continue monitoring to confirm there are no further delays.

Inbound emails to Cloud Help Desk that were sent over approx. the past 30 minutes are delivering normally, without delay. Emails that were sent between approx. 19:52 and 21:40 UTC are continuing to sporadically be delayed in delivery to Cloud Help Desk. We are monitoring while working with our ESP on identifying the cause.

We've received automated alerts and reports from users who are seeing delays with receiving new ticket and ticket comment updates via email. We are actively investigating the issue with inbound email to the Cloud Help Desk and we'll provide updates as available.

Our documentation originally recommended redirecting mail, which intermittently loses the cloud help desk email address and causes missing tickets. Changing this rule to CC the cloud help desk ensures the headers always contain the required information. The documentation has been updated to reflect this change https://community.spiceworks.com/support/help-desk-cloud-edition/troubleshooting/forwarding-email

A potential fix exists for users of O365, discovered by a user: - Sign in to the Office 365 admin center as an admin. - Go to the Exchange admin center by clicking on Admin centers > Exchange. - go to Recipients > Contacts - Click + Add a contact - Email: Enter your Spiceworks ORG helpdesk email address - In the Exchange admin center, click on Mail flow in the left-hand menu. - Click the plus (+) icon and select Create a new rule. - In the New rule window, give the rule a name and description. - Under Apply this rule if..., enter your internal help desk address - Under Do the following..., choose CC the message to > addresses and type in the newly created contact - Click Save to create the rule. **This should take the place of any existing Spiceworks-related Redirect rules. If those are in place, disable them temporarily while you determine whether the above resolve the issue for you.**

We have reports that mail delivered successfully to our servers is not creating tickets. It primarily occurs when forwarding/redirecting is used and the header data intermittently doesn't contain the orgname.on.spiceworks.com address to correctly route the email. The development team is looking into solutions for this. The workaround in the meantime is to send mail directly to your help@orgname.on.spiceworks.com address or have users submit tickets via the end user portal.

No further reports of this overnight, please contact support@spiceworks.com if you're experiencing this issue.

We believe this was caused by a temporary issue at a data center for our web application firewall. If you're still seeing this issue, please let us know at support@spiceworks.com

We're seeing some reports of folks unable to log in to their cloud help desk. The development team have been notified and are investigating the cause.

There have been no further issues and the site has been responsive and stable following the mentioned partial outage time period.

During the time period Aug 26, 2023 09:00 - 11:00 CDT (14:00-16:00 UTC) the Community experienced periods of partial outage resulting in the inability to load pages consistently for all visitors. During this time period inbound automated traffic was generating unusually high load in specific areas of the Community service, resulting in these periods of unavailability. Mitigations have been implemented. We will be monitoring to ensure stability.

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.

Our monitoring indicates the system has been stable since the deploy approx. 3 hours ago. Please report any new instances of this issue to our Support team.

The system has rapidly stabilized following the deploy. We are actively monitoring.

We are deploying a change related to system capacity and will monitor the impact.

We are actively investigating this issue.

Affected folks have let us know that they are no longer seeing the issue, so we believe the fix to be effective. Contact support@spiceworks.com if you're still seeing issues loading cloud inventory pages.

A fix has been implemented. We're monitoring to ensure this has resolved the issue.

Reports of this yesterday we're attributed to a database load issue which was rectified. We're still seeing some reports of users affected by their inventory not loading. The development team is investigating the issue as a priority.

A fix has been implemented and traffic has been restored to the data center.

Our CDN has identified an issue in their New York (NYC) data center. Traffic is being rerouted through an alternate data center in the region. You may encounter some latency for the duration of time that the reroute is in place. We'll update this page when they give the all-clear.

An Imperva issue is causing periodic issues accessing the Community and/or the Cloud Help Desk. This is being investigated.

Imports with greater than 5000 tickets are failing, even when under the documented file size limit. The main use for this feature is to import from the legacy help desk which was discontinued in 2021. Due to this, further development time cannot be committed to fully address this issue. A workaround reported by some users has been to split up the import file. A bash script that can be used for this purpose can be found at https://community.spiceworks.com/scripts/show/5263-spiceworks-json-export-file-splitter You can use your own method for splitting the file, though note that the following json arrays need to be present in order for every file: sites custom_attributes inventory_ticket_relations tickets users When you have the split files, head over to the Cloud Help Desk Setting page: Select Import/export tickets Choose the first file to upload e.g. split_export_1.json Ensure "Keep the same ticket numbers" is not selected Click "Continue import" Check the import log link to see the progress of the import Once the import is complete you can add the next file in the same manner Keep adding files until you have imported all of your tickets

We're getting reports of ticket import jobs failing. The development team is looking into the cause. Failing imports are unlikely to succeed until this issue is resolved or a workaround found, so we recommend not retrying the same data if your initial import fails to complete. A new import with a smaller subset of tickets may be successful in the meantime.

Setting Power BI to use a default web browser has resolved the login issue for users who raised support ticket. We recommend this as the standard configuration going forward. In Power BI, go to File > Options And Settings > Options > Security > Scroll down to "Authentication Browser" > Enable "Use my default browser".

Dave4564 on the community shared a workaround for those folks not getting the login box or being unable to delete old credentials: In Power BI, go to File > Options And Settings > Options > Security > Scroll down to "Authentication Browser" > Enable "Use my default browser" When you try to refresh the data now, the login should open up in a browser window and allow you to log in.

We are investigating reports that in some cases the Power BI connector is no longer able to log in to retrieve reporting information.

Resolved via a release Mar 23, refer to release notes https://community.spiceworks.com/blogs/help-desk-cloud-edition-release-notes/4050-cloud-help-desk-exports-power-bi-advanced-reporting-bugfix

A fix was put into place 22-Mar that appears to have resolved the issue. If you're still having trouble with Power BI, though, email support: support@spiceworks.com

When refreshing Power BI to retrieve updated values, you may receive an error like: "Web.Contents failed to get contents from 'https://on.spiceworks.com/api/public/power_bi/reports/xlsx' (404): Not Found" The cause for this is under investigation, however a workaround has been discovered by users: If you delete the exports that are triggered by opening PowerBi and manually run an export, you can then refresh PowerBi.

If you use SPAM filtering that may block the cloud help desk IP addresses, we recommend whitelisting them to maintain delivery of notifications. With hundreds of thousands of help desk accounts, some SPAM is likely to cause these IP's to be blacklisted from time to time. If you normally only get messages from your own help desk and not SPAM from other Spiceworks cloud help desks, it should be safe to permanently whitelist them. These IP addresses are only used for the cloud help desk. The current addresses we use are: 167.89.74.79 167.89.75.142 167.89.82.157 You can check the updated list at any time by visiting: https://community.spiceworks.com/support/help-desk-cloud-edition/troubleshooting/forwarding-email#whitelist-mail-server-ip-addresses

As of Feb. 14 we made changes not requiring a release and which appear to have resolved this issue with the intermittent loss of inbound email. We have been reaching out to those previously impacted and monitoring for the past 2 weeks to confirm resolution. Please reach out by emailing support@spiceworks.com if you're seeing deliverability problems in either direction (inbound or outbound). And thanks again to all of you who worked with us to troubleshoot on this.

We've learned more and have released additional email logging for the Cloud Help Desk detailed here [https://community.spiceworks.com/r/4745]. If you are experiencing this issue we could use your help to perform some testing/data capture - please reach out to support@spiceworks.com if you can help us test!

We have been investigating reports from users of problems with email-based ticket creation. We have a number of users from distinct and a limited number of accounts reporting what seems to be random/intermittent emails not reaching their help desk. The majority of accounts are not impacted. We are actively testing and troubleshooting with impacted users. And with assistance from our email provider, we have narrowed down the underlying cause and are working on a resolution. Current workarounds include re-sending missing emails or using the end user portal. We will provide updates here, as they're available.

We haven't received any user complaints today following the resolution, here, but please let us know if delivery issues recur. To follow along, we will be spending some time seeking out ways to manage and improve the Cloud Help Desk's email service reputation.

The IP addresses have been delisted - we expect outbound notifications will arrive without issue. If that's not the case, or if you have related questions, feel free to reach out: support@spiceworks.com

We're receiving reports that folks using Mimecast (and possibly other email protection services) may be seeing blocked mail from Spiceworks due to a blacklisted IP address. While we work to resolve that issue, you can ensure mail delivery in the meantime by whitelisting our main IP addresses: 167.89.74.79 167.89.75.142 167.89.82.157

Email delivery has been normal since the last update. We will be working on postmortem/prevention to avoid this type of outage in the future. We know that timely email delivery is key to providing you with a reliable help desk experience. We are taking this one very seriously!

Our email service provider (ESP) has released the outbound email hold and emails are now delivering. Messages queued during this outage should all be delivered, and new messages should see no delay. If you notice any issues please email support@spiceworks.com to let us know. We will continue monitoring through Feb. 7. We will also be working with our ESP to prevent such email delivery holds in the future.

We are working with our email service provider (ESP) to resolve the email delivery issue. Email flow outbound from Cloud Help Desk is sending to the ESP successfully, but is being enqueued/held for an unknown reason. The ESP indicated any enqueued messages will deliver once this is resolved.

We are currently investigating an issue that's causing notifications not to be sent out for ticket creation, comments, etc... We're looking into this as a high priority and will update here when more is known.

The mobile app issue has been resolved by rolling back a recent update.

We are continuing to investigate this issue.

A bug was recently discovered that's causing some users of the mobile apps to receive a 404 error or see other issues when taking certain actions in the application. This is being reviewed by developers. Keep an eye on this page for updates.

Further fixes have been rolled out and the backlog of new agents to register has caught up. Going forward, you should see registration of new agents within minutes. We will continue to monitor to ensure the service remains stable.

Issues with new device registration is still occurring. The development team are looking into other factors that can cause this. If you're deploying agents, there won't be a need to re-deploy when this issue is solved.

The issue has been identified and a fix is being deployed. We estimate normal reporting/registration of agents will occur over the next 2 hours and we will continue to monitor performance. If you are still seeing issues after that time, please get in touch at support@spiceworks.com

We're investigating reports of new agent installations not being shown in the inventory dashboard, despite appearing to have registered successfully.

This issue has been resolved.

We've reverted recent changes to inventory services which is allowing the agent data backlog to catch up. New agent devices/data may appear more slowly in inventory until the backlog is fully caught up. we will continue monitoring and investigating.

We're investigating reports that new agent installations for collection/scanning agents are not visible in the Cloud Inventory user interface. In some cases those devices are visible to the connectivity dashboard indicating they registered successfully.

This incident has been resolved.

We have identified an issue and taken action to address it. It appears to have resolved the issue, but we will continue to monitor the situation to ensure that is the case.

We are aware that the Spiceworks Community is currently inaccessible and we are investigating the issue.

This incident has been resolved.

We are extending the maintenance window specifically for the Spiceworks Community: https://status.spiceworks.com/incidents/wb8ch6wkfgqd At this time, you should be able to log into https://accounts.spiceworks.com/ and https://www.spiceworks.com/, but we are continuing to work on the Spiceworks Community and will be leaving it in maintenance mode until this is complete.

A recent backend update was the culprit for this. The update has been rolled back and the Power BI / CHD connection is working properly now.

We've received reports that some users are experiencing an issue trying to connect Power BI to their Cloud Help Desk instance. At this time, we're unclear what's causing this issue and are continuing to investigate.

A spamming attempt was blocked which delayed some genuine emails. Our filtering configuration has been adjusted to avoid this. We're now seeing good ingestion and mail delivery times. Reach out to support@spiceworks.com if you are still seeing this issue.

We're looking into an issue where new tickets emailed into the help desk are being delayed

We have not seen further issues related to this since the fix was posted. If you are seeing this issue, please reach out to support@spiceworks.com

A new fix has been implemented and we're monitoring to verify its effects.

The source of the issue has been identified and a fix is being worked up.

REOPENED: We have reports that some emails don't make it to the cloud help desk to update tickets. The development team are looking into the cause.

Between 18 Aug, 2022 and 30 Aug, 2022, reply notifications that included a custom footer did NOT include the text "Reply above this line to add a comment." This caused the reply to be improperly parsed, assumed to be an automatic reply, and dropped. There's not a way to retroactively fix notifications that have already been sent, so it's expected that as these older notifications "age out", the issue will naturally resolve. As always, email support@spiceworks.com with any questions about this.

Prior update was for another incident, this issue is still being investigated, apologies for the notifications.

This issue is only affecting organizations that configured a custom email footer. A fix is being tested to resolve.

We have reports that some emails don't make it to the cloud help desk to update tickets. The development team are looking into the cause.

This issue has been resolved.

A fix for this issue has been implemented and we are monitoring for any other related issues. Portal email authentication should now be working again. If you continue to have issues, email support: support@spiceworks.com

The issue has been identified and a fix is being developed.

We have some reports of portals with email authentication enabled not sending out the login emails to end users.

The cause of the issue was identified and fixed, and we've been able to observe mail flow resume (with previously queued messages included.) If you continue to see issues, or have any questions about this, send a note to support@spiceworks.com. We're sorry for the trouble this caused.

Some mail is still not making it through to create tickets in a reasonable timeframe. Our development and operations teams are continuing to work the issue.

Our dev ops team have implemented changes that are clearing the backlog of email. We are monitoring progress and will update further once this can be confirmed as a full resolution to the issue.

Our teams are continuing to investigate the issue along with our email provider. Missing mail is creating tickets but with a variable delay, so at this time we would recommend not re-sending missing messages (to avoid duplicates later on).

We have reports that some emails don't make it to the cloud help desk to become tickets. The development team are looking into the cause.

This incident has been resolved.

A fix has been implemented and the website is now properly loading. We will continue to monitor the results.

We are currently investigating an issue where the main Spiceworks website, www.spiceworks.com, is unavailable and resulting in a 500 Internal Server Error.

The issue has been resolved. More details about what occurred and how it has been fixed is included in the blog post here: https://community.spiceworks.com/topic/2350501-cloud-help-desk-delayed-incoming-email-march-1-2022?page=1#entry-9406157

The development team is working on resolving the issue as quickly as possible.

The queues are now fully caught up. Apologies for the hassles and thanks for bearing with us.

We're looking at around 15 minutes delay now. The team will continue to monitor after we're fully caught up.

We have identified the issue and a fix is in place. Extra processing is being done to "catch up" on the queued incoming email. We're currently running 70 minutes behind.

We have reports of mail being delayed or not reaching cloud help desk accounts. The development team are investigating.

No further reports of this issue after the fix. If you are still experiencing the issue, please let the support team know at support@spiceworks.com

A fix has been posted. If you were affected by this issue, please try to create an account now. If there are still issues and you don't have a support ticket, raise one by emailing support@spiceworks.com

The development team have been notified and are investigating

Last week we made some updates to better support the high volume of organizations importing tickets into the Spiceworks Cloud Help Desk (CHD). This resolved the issue with these imports taking longer than intended. We continued to monitor this late last week and over the weekend and we've seen these imports finish within 24 hours. Please note that you go back to your Import/Export area under Settings, you should also be able to view the status of any pending or in-progress imports. If the import fails or takes longer than 72 hours, do not hesitate to contact us via our support channels. Thank you for your patience.

We're seeing an increase in ticket imports queued up for the cloud help desk. It is going to take longer (possibly days) for imports to complete. Please don't resubmit imports as this will further add to the backlog, your import is being processed.