Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Sherweb outage history

    34 recorded Sherweb incidents since June 2026, with official updates, affected components, duration and resolution information.

    Back to current status

    Service Incident Update - Resolved

    Started October 26, 2026 at 6:33 PM UTC · 57m

    IssuesMinor incident
    Affected components
    APICumulus PortalBilling APIMFA: SMSShopping CartSherweb Hosted ServicesMFA: EmailGeneralShopping API
    1. October 26, 2026 at 6:33 PM UTCupdate

      We are currently investigating an issue impacting the GDAP page in Cumulus . Impact Level: Investigating Current Progress: Our engineering team has been mobilized and is actively investigating the problem to determine the root cause and restore service. Next update: We will provide an update within 60 minutes.

    2. October 26, 2026 at 6:44 PM UTCupdate

      This is an update regarding the ongoing disruption to the GDAP page in Cumulus Impact Level: Partial Outage You may currently be experiencing issue when accessing the GDAP page in Cumulus resulting in the following error: "The value 'null' is not valid for GUID" Current Progress: Our team had identified a potential cause within the page code and it currently working to implement a fix Next Update: We will continue to monitor the implementation and will provide our next update by 16:00 EDT on Oct 26th.

    3. October 26, 2026 at 7:06 PM UTCupdate

      This is an update regarding the ongoing disruption to the GDAP page in Cumulus Impact Level: Partial Outage You may currently be experiencing issue when accessing the GDAP page in Cumulus resulting in the following error: "The value 'null' is not valid for GUID" Current Progress: Our team is actively implementing a fix to address the issue and restore full service. We are closely monitoring the changes as they are applied. Next Update: We will continue to monitor the fix implemented and will provide our next update by 16:30 EDT on Oct 26th. .

    4. October 26, 2026 at 7:30 PM UTCresolved

      The issue affecting the GDAP page in Cumulus has been resolved, and all services are now operating normally. Impact Level: Resolved Latest Update: Our team successfully applied a patch at 15:28 , and we have verified that system stability has returned. If you are still experiencing service-related issues, please contact our support team for further assistance.

    Service Incident Update - resolved

    Started October 23, 2026 at 7:39 PM UTC · 44m

    IssuesMinor incident
    Affected components
    APICumulus PortalBilling APIMFA: SMSShopping CartSherweb Hosted ServicesMFA: EmailGeneralShopping API
    1. October 23, 2026 at 7:39 PM UTCupdate

      We are currently investigating an issue affecting license upgrades in Cumulus Impact Level: Investigating Current Progress: Our engineering team has been mobilized and is actively investigating the problem to determine the root cause and restore service. Next update: We will provide an update within 60 minutes.

    2. October 23, 2026 at 8:02 PM UTCupdate

      This is an update regarding the ongoing disruption affecting License upgrades in Cumulus Impact Level: Partial Outage You may currently be experiencing issue when upgrading licenses in Cumulus Current Progress: Our team is actively implementing a fix to address the issue and restore full service. We are closely monitoring the changes as they are applied. Workaround: While we work to fully resolve this issue, you can temporarily bypass the problem by creating a support ticket at [email protected]. We will be able to manually proceed with the upgrade Next Update: We will continue to monitor the fix implemented and will provide our next update by 16:45 EDT Oct 23rd

    3. October 23, 2026 at 8:23 PM UTCresolved

      The issue affecting License upgrades in Cumulus has been resolved, and all services are now operating normally. Before proceeding with a license upgrade, please perform a full browser refresh (Ctrl + F5) to ensure the latest script changes are loaded. Impact Level: Resolved Latest Update: Our team successfully applied a patch at 16:15 , and we have verified that system stability has returned. If you are still experiencing service-related issues, please contact our support team for further assistance.

    Incident Closure - Performance Cloud, C2 ISTM and In-House Archiving

    Started October 15, 2026 at 2:40 PM UTC · 3h 50m

    IssuesMinor incident
    Affected components
    Performance Cloud VMware - Quebec, CanadaVeeam Cloud Backup and Recovery - Montreal, CanadaPerformance Cloud VMware – Montreal, CanadaC2 ITSMPre-ProductionSherweb Hosted ServicesCanadaData WarehouseProductionPerformance CloudVMware Avi Load Balancer - Montreal, CanadaIn-House Archiving
    1. October 15, 2026 at 2:40 PM UTCupdate

      We are currently investigating an issue impacting Performance Cloud (Canada), C2 ITSM and In-House Archiving . Impact Level: Investigating Current Progress: Our engineering team has been mobilized and is actively investigating the problem to determine the root cause and restore service. Next update: We will provide an update within 60 minutes.

    2. October 15, 2026 at 2:43 PM UTCupdate

      This is an update regarding the ongoing disruption to Performance Cloud (Canada), C2 ITSM and In-House Archiving . Impact Level: Partial Outage Some customers may experience intermittent issues accessing or using certain functions within Performance Cloud or C2 ITSM. Current Progress: Our team is still investigating and working on identifying the cause of the issue. In-House Archiving is now working as expected. Workaround: While we work to fully resolve this issue, if your VM becomes stuck or unresponsive, rebooting the affected VM may restore functionality. Next Update: We will continue to monitor the status of service incident and will provide our next update by 12:00 EDT .

    3. October 15, 2026 at 3:14 PM UTCupdate

      This is an update regarding the ongoing disruption to P erformance Cloud (Canada), C2 ITSM and In-House Archiving . Impact Level: Recovering You should now be able to access the affected services normally. If you continue to experience issues, restarting the affected service may help restore functionality. Current Progress: Our Team has implemented the fix, and we are monitoring the service closely to ensure stability and confirm that the issue is fully resolved. Next Update: We will continue to monitor the fix implemented and will provide our next update by 15:00 EDT .

    4. October 15, 2026 at 6:30 PM UTCresolved

      This issue affected P erformance Cloud (Canada), C2 ITSM and In-House Archiving has been resolved and all services are now operating normally. Impact Level: Resolved Latest Update: Our team successfully restored the services at 11:15 EDT , and we have verified that system stability has returned. Next Update: We are conducting a thorough Root Cause Analysis (RCA) to understand why this happened and to implement safeguards preventing it from occurring again. We will share the post-incident report with you by the 22nd of October. If you are still experiencing service-related issues, please contact our support team for further assistance.

    5. October 23, 2026 at 10:58 AM UTCupdate

      Below is the post-incident report for the service disruption on October 15, 2026, including what happened, the cause, and the steps taken to prevent recurrence. Executive Summary • Date of Incident: October 15, 2026 • Duration of Outage: 1 hour, 30 minutes (9:45 AM – 11:15 AM) EDT • Maximum Impact Level: Major Outage • Services Impacted: Performance Cloud, C2, and In-House Archive • Client Impact: Some Performance Cloud virtual machines experienced service interruptions or reboots as workloads failed over to alternate infrastructure. C2 environments were temporarily unavailable, preventing affected customers from accessing the C2ITSM platform. In-House Archive customers were also temporarily unable to access affected portals to view or download their data. • Root Cause Summary: The disruption was caused by a hardware failure on one of our Performance Cloud hosts. The hardware vendor confirmed that the host’s motherboard was faulty and required replacement. Technical Root Cause The disruption was triggered by a hardware failure affecting one of our Performance Cloud hosts. The failure caused workloads running on the affected host to automatically fail over to alternate infrastructure. While most workloads recovered through failover, some dependent services required additional recovery actions before full functionality was restored. Resolution Timeline All times are in EDT. • 9:45: One of our Performance Cloud hosts became unavailable, triggering the failover of affected workloads to another host. • 10:02: Our monitoring systems detected the host failure, and investigation began. • 10:30: The affected host was isolated to prevent further impact. • 10:40: In-House Archive was restored following recovery actions on affected database services. • 11:00: C2 environments began recovering following database failover. • 11:14: C2 environments were restored. • 11:15: All affected customer-facing services were fully restored. • 12:15: Remaining database synchronization issues were resolved. Preventative Measures To prevent a recurrence of this specific issue, we are taking the following actions: • Replacing the hardware on the affected Performance Cloud host. • Adding additional hardware diagnostics to the host deployment process. • Reviewing and adjusting database infrastructure affinity rules. If you are still experiencing service-related issues, please contact our support team for further assistance.

    Update: Resolved - Provisioning for Microsoft 365

    Started September 28, 2026 at 8:06 PM UTC · 18h 14m

    IssuesMinor incident
    Affected components
    Cumulus PortalExternal Marketplace ServicesAzureOffice 365Sherweb Hosted ServicesDynamics 365Microsoft 365GeneralMicrosoft
    1. September 28, 2026 at 8:06 PM UTCupdate

      We are currently investigating an issue impacting M365 Provisioning via Cumulus Portal . Impact Level: Investigating Current Progress: Our engineering team has been mobilized and is actively investigating the problem to determine the root cause and restore service. Next update: We will provide an update within 60 minutes.

    2. September 28, 2026 at 9:01 PM UTCupdate

      Impact Level: Major Outage You may currently be experiencing issues when trying to provision or modify Microsoft 365 and Dynamics 365 licences in Cumulus. Current Progress: Our team has identified the potential cause as an issue on Microsoft's side is impacting the provisioning of the licences. We are investigating with them.. Next Update: We will continue to monitor the implementation and will provide our next update by September 28th, 6:00PM EST

    3. September 28, 2026 at 9:56 PM UTCupdate

      This is an update regarding the ongoing disruption to Provisioning for Microsoft 365. Impact Level: Recovering You should now be able to do provisioning request. The provisioning requests that were previously in error or queued are now being processed. . Current Progress: We are monitoring the service closely to ensure no more provisioning requests are getting stuck. Next Update: We will continue to monitor the fix implemented and will provide our next update by September 28th, 7:00PM EST

    4. September 28, 2026 at 10:59 PM UTCupdate

      This is an update regarding the ongoing disruption to Provisioning for Microsoft 365. Impact Level: Recovering You should now be able to do provisioning request. The provisioning requests that were previously in error or queued have all been processed Current Progress: We are monitoring the service closely to ensure no more provisioning requests are getting stuck. Next Update: We will continue to monitor the fix implemented and will provide our next update by September 29th, 10:00AM EST

    5. September 29, 2026 at 2:20 PM UTCresolved

      The issue affecting the provisioning of Microsoft 365 products has been resolved, and all services are now operating normally. Impact Level: Resolved Latest Update: Our team successfully worked with Microsoft to identify the cause of the provisioning issue, and we have verified that system stability has returned. Next Steps: We will be working with Microsoft to prevent the issue from happening again. If you are still experiencing service-related issues, please contact our support team for further assistance.

    Issue detected on C2 - Production / P03

    Started September 18, 2026 at 6:11 AM UTC · 1h 0m

    IssuesMinor incident
    Affected components
    C2 ITSMSherweb Hosted ServicesProduction
    1. September 18, 2026 at 6:11 AM UTCupdate

      We are currently investigating an issue impacting C2 - Production / P03 . Impact Level: Investigating Current Progress: Our engineering team has been mobilized and is actively investigating the problem to determine the root cause and restore service. Next update: We will provide an update within 60 minutes.

    2. September 18, 2026 at 7:11 AM UTCresolved

      Issue is resolved.

    Update: Resolved - Sherweb.com contact & registration forms

    Started September 17, 2026 at 7:45 PM UTC · 17h 33m

    IssuesMinor incident
    Affected components
    GeneralSherweb Hosted Services
    1. September 17, 2026 at 7:45 PM UTCupdate

      We are currently investigating an issue impacting Sherweb.com contact & registration forms . Impact Level: Investigating Current Progress: Our engineering team has been mobilized and is actively investigating the problem to determine the root cause and restore service. Next update: We will provide an update within 60 minutes.

    2. September 17, 2026 at 8:20 PM UTCupdate

      This is an update regarding the ongoing disruption to Sherweb.com contact & registration forms . Impact Level: Performance Degraded You maybe unable to submit any contact & registration form on sherweb.com site. Current Progress: Our team has identified the potential cause from a 3rd party provider and is currently implementing a fix. Next Update: We will continue to monitor the implementation and will provide our next update by 17h45 EDT

    3. September 17, 2026 at 9:45 PM UTCupdate

      This is an update regarding the ongoing disruption to Sherweb.com contact & registration forms . Impact Level: Performance Degraded You maybe unable to submit any contact & registration form on sherweb.com site. Current Progress: Our team has identified the potential cause from a 3rd party provider and is currently implementing a fix. Workaround: If you require immediate assistance, you can contact our support team through calls or reaching out via email Next Update: We will continue to monitor the implementation and will provide our next update by 20h00 EDT

    4. September 17, 2026 at 10:04 PM UTCupdate

      This is an update regarding the ongoing disruption to Sherweb.com contact & registration forms . Impact Level: Recovering You should now be able successfully submit Contact & Registration forms on the Sherweb.com website. Current Progress: Our team has confirmed that the third-party provider has implemented a fix. We have verified that customers can now successfully submit contact and registration forms. We are continuing to monitor the service closely to ensure stability. Next Update: We will continue to monitor the fix implemented and will provide our next update by 9:00 EDT on the 18th of September .

    5. September 18, 2026 at 1:18 PM UTCresolved

      The issue affecting Sherweb.com contact & registration forms has been resolved, and all services are now operating normally. Impact Level: Resolved Latest Update: Our team has confirmed that the third-party provider's fix remains effective, and we have verified that customers can successfully submit contact and registration forms. Next Steps: W e are conducting a thorough Root Cause Analysis (RCA) to understand why this happened and to implement safeguards preventing it from occurring again. We will share the post-incident report with you by September 25, 2026. If you are still experiencing service-related issues, please contact our support team for further assistance.

    Update: Resolved - Cumulus

    Started September 17, 2026 at 1:39 PM UTC · 1h 36m

    IssuesMinor incident
    Affected components
    Cumulus PortalSherweb Hosted ServicesGeneral
    1. September 17, 2026 at 1:39 PM UTCupdate

      We are currently investigating an issue impacting Cumulus Portal . Impact Level: Investigating Current Progress: Our engineering team has been mobilized and is actively investigating the problem to determine the root cause and restore service. Next update: We will provide an update within 60 minutes.

    2. September 17, 2026 at 2:01 PM UTCupdate

      This is an update regarding the ongoing disruption to Cumulus. Impact Level: Investigating You may currently experience issues when managing or updating customer subscriptions and services within Cumulus. Current Progress: Our team is still investigating and working on identifying the cause of the issue. Next Update: We will continue to monitor the status of service incident and will provide our next update by 11:30 EDT .

    3. September 17, 2026 at 2:20 PM UTCupdate

      This is an update regarding the ongoing disruption to Cumulus . Impact Level: Recovering You should now be able to manage or update your subscription in Cumulus . Current Progress: Our Team has implemented the fix, and we are monitoring the service closely to ensure stability and confirm that the issue is fully resolved. Next Update: We will continue to monitor the fix implemented and will provide our next update by 2026-09-17 11h30 EDT .

    4. September 17, 2026 at 3:15 PM UTCresolved

      The issue affecting Cumulus has been resolved, and all services are now operating normally. Impact Level: Resolved Latest Update: Our team successfully restored full functionality at 10:15 EDT , and we have verified that system stability has returned. Next Steps: We are conducting a thorough Root Cause Analysis (RCA) to understand why this happened and to implement safeguards preventing it from occurring again. We will share the post-incident report with you by the 24th of September . If you are still experiencing service-related issues, please contact our support team for further assistance.

    Duplicate transactions affecting some Payroll and Payments customers

    Started September 16, 2026 at 5:30 PM UTC · 5h 32m

    IssuesMinor incident
    Affected components
    CanadaExternal Marketplace ServicesQuickBooks Online
    1. September 16, 2026 at 5:30 PM UTCmonitoring

      We're aware that some customers are experiencing duplicate transactions in Payroll and Payments. Our teams are actively working to resolve this issue and correct any duplicate transactions. If you have questions or need immediate help, visit intuit.com/support. We're sorry for the disruption and appreciate your patience while we make this right.

    2. September 16, 2026 at 5:31 PM UTCmonitoring

      We are continuing to monitor for any further issues.

    3. September 16, 2026 at 11:02 PM UTCresolved

      This issue is resolved. Payroll and Payments customers have been contacted. Refunds of duplicate transactions are being processed. We're sorry for the disruption and appreciate your patience.

    Update: Resolved - Azure Billing

    Started September 15, 2026 at 11:07 PM UTC · 5d 19h

    IssuesMinor incident
    Affected components
    External Marketplace ServicesAzureMicrosoft
    1. September 15, 2026 at 11:07 PM UTCupdate

      We are currently investigating an issue impacting Azure Billing . Impact Level: Investigating Customers using Microsoft Azure services whose invoices are generated while this incident remains ongoing will receive invoices that do not include Azure-related charges. Once the issue has been resolved, the outstanding Azure charges will be invoiced separately through a new invoice. Current Progress: Our engineering team has been mobilized and is actively investigating the problem to determine the root cause and restore Azure-related billing processing. Next Update: We will provide our next update by 9:00 EDT September 16th.

    2. September 16, 2026 at 12:45 PM UTCupdate

      This is an update regarding the ongoing disruption to Azure Billing . Impact Level: Investigating Customers using Microsoft Azure services whose invoices are generated while this incident remains ongoing will receive invoices that do not include Azure-related charges. Once the issue has been resolved, the outstanding Azure charges will be invoiced separately through a new invoice. Current Progress: Our team is still investigating and working on identifying the cause of the issue. Next Update: We will continue to monitor the status of service incident and will provide our next update by 10:00 EDT.

    3. September 16, 2026 at 1:47 PM UTCupdate

      This is an update regarding the ongoing disruption to Azure Billing . Impact Level: Investigating Customers using Microsoft Azure services whose invoices are generated while this incident remains ongoing will receive invoices that do not include Azure-related charges. Once the issue has been resolved, the outstanding Azure charges will be invoiced separately through a new invoice. Current Progress: Our team continues to investigate and work toward identifying the root cause of the issue. The team is actively implementing and validating corrective measures to restore Azure billing processing while the investigation remains ongoing. Next Update: We will continue to monitor the status of service incident and will provide our next update by 12:00 EDT .

    4. September 16, 2026 at 3:46 PM UTCupdate

      This is an update regarding the ongoing disruption to Azure Billing . Impact Level: Investigating Customers using Microsoft Azure services whose invoices are generated while this incident remains ongoing will receive invoices that do not include Azure-related charges. Once the issue has been resolved, the outstanding Azure charges will be invoiced separately through a new invoice. Current Progress: Our team continues to investigate and work toward identifying the root cause of the issue. The team is actively implementing and validating corrective measures to restore Azure billing processing while the investigation remains ongoing. Next Update: We will continue to monitor the status of service incident and will provide our next update by 14 :00 EDT .

    5. September 16, 2026 at 6:00 PM UTCupdate

      This is an update regarding the ongoing disruption to Azure Billing . Impact Level: Major Outage Customers using Microsoft Azure services whose invoices are generated while this incident remains ongoing will receive invoices that do not include Azure-related charges. Once the issue has been resolved, the outstanding Azure charges will be invoiced separately through a new invoice. Current Progress: Our team is actively implementing a fix to address the issue and restore full service. We are closely monitoring the changes as they are applied. Next Update: We will continue to monitor the fix implemented and will provide our next update by 16:00 EDT.

    6. September 16, 2026 at 8:00 PM UTCupdate

      This is an update regarding the ongoing disruption to Azure Billing . Impact Level: Major Outage Customers using Microsoft Azure services whose invoices are generated while this incident remains ongoing will receive invoices that do not include Azure-related charges. Once the issue has been resolved, the outstanding Azure charges will be invoiced separately through a new invoice. Current Progress: Our team is actively implementing a fix to address the issue and restore full service. We are closely monitoring the changes as they are applied. Next Update: We will continue to monitor the fix being implemented and will provide our next update by 9:00 EDT on the 17th of September.

    7. September 17, 2026 at 1:01 PM UTCupdate

      This is an update regarding the ongoing disruption to Azure Billing . Impact Level: Major Outage Customers using Microsoft Azure services whose invoices are generated while this incident remains ongoing will receive invoices that do not include Azure-related charges. Once the issue has been resolved, the outstanding Azure charges will be invoiced separately through a new invoice. Current Progress: Our team is actively implementing a fix to address the issue and restore full service. We are closely monitoring the changes as they are applied. Next Update: We will continue to monitor the fix being implemented and will provide our next update by 16:00 EDT.

    8. September 17, 2026 at 8:00 PM UTCupdate

      This is an update regarding the ongoing disruption to Azure Billing . Impact Level: Major Outage Customers using Microsoft Azure services whose invoices are generated while this incident remains ongoing will receive invoices that do not include Azure-related charges. Once the issue has been resolved, the outstanding Azure charges will be invoiced separately through a new invoice. Current Progress: Our team is actively implementing a fix to address the issue and restore full service. We are closely monitoring the changes as they are applied. Next Update: We will continue to monitor the fix being implemented and will provide our next update by 9:00 EDT on the 18th of September.

    9. September 18, 2026 at 1:00 PM UTCupdate

      This is an update regarding the ongoing disruption to Azure Billing . Impact Level: Recovering Invoice generation has resumed. Customers who were impacted during the incident period will receive a separate invoice for Azure-related charges that were not included in their original invoice. Current Progress: Our team has implemented the fix, and invoice processing is progressing normally. Additional invoices for outstanding Azure charges are being generated and should be available this afternoon. We are monitoring the service closely to ensure stability and confirm that the issue is fully resolved. Impacted customers who will receive a separate invoice will be contacted directly. Next Update: We will continue to monitor the fix implemented and will provide our next update by 14:00 EDT .

    10. September 18, 2026 at 6:01 PM UTCupdate

      This is an update regarding the ongoing disruption to Azure Billing . Impact Level: Recovering Invoice generation has resumed. Customers who were impacted during the incident period will receive a separate invoice for Azure-related charges that were not included in their original invoice. Current Progress: Our team has implemented the fix, and invoice processing is progressing normally. Additional invoices for outstanding Azure charges are being generated and should be available this afternoon. We are monitoring the service closely to ensure stability and confirm that the issue is fully resolved. Impacted customers who will receive a separate invoice will be contacted directly. Next Update: We will continue to monitor the fix implemented and will provide our next update by 16:00 EDT .

    11. September 18, 2026 at 7:59 PM UTCupdate

      This is an update regarding the ongoing disruption to Azure Billing . Impact Level: Recovering Invoice generation has resumed. Customers who were impacted during the incident period will receive a separate invoice for Azure-related charges that were not included in their original invoice. Current Progress: Our team has implemented the fix, and invoice processing is progressing normally. Additional invoices for outstanding Azure charges are being generated and should be available this afternoon. We are monitoring the service closely to ensure stability and confirm that the issue is fully resolved. Impacted customers who will receive a separate invoice will be contacted directly. Next Update: We will continue to monitor the fix implemented and will provide our next update by 18:15 EDT .

    12. September 18, 2026 at 10:11 PM UTCupdate

      This is an update regarding the ongoing disruption to Azure Billing . Impact Level: Recovering Invoice generation has resumed. Customers who were impacted during the incident period will receive a separate invoice for Azure-related charges that were not included in their original invoice. Current Progress: Our team has implemented the fix, and invoice processing is progressing normally. Additional invoices for outstanding Azure charges are being generated and should be available this afternoon. We are monitoring the service closely to ensure stability and confirm that the issue is fully resolved. Impacted customers who will receive a separate invoice will be contacted directly. Next Update: We will continue to monitor the fix implemented and will provide our next update by 20:15 EDT .

    13. September 19, 2026 at 12:09 AM UTCupdate

      This is an update regarding the ongoing disruption to Azure Billing . Impact Level: Recovering Invoice generation has resumed. Customers who were impacted during the incident period will receive a separate invoice for Azure-related charges that were not included in their original invoice. Current Progress: Our team has implemented the fix, and invoice processing is progressing normally. Additional invoices for outstanding Azure charges are being generated and should be available soon. We are monitoring the service closely to ensure stability and confirm that the issue is fully resolved. Next Update: We will continue to monitor the fix implemented and will provide our next update by 22:15 EDT .

    14. September 19, 2026 at 12:37 AM UTCupdate

      This is an update regarding the ongoing disruption to Azure Billing . Impact Level: Recovering Invoice generation has resumed. Customers who were impacted during the incident period have now received a separate invoice for Azure-related charges that were not included in their original invoice. Current Progress: Our team has successfully implemented the fix, and all impacted invoices have now been generated and delivered. We continue to monitor the service closely to ensure ongoing stability and confirm the issue remains fully resolved. Customers with questions regarding their Azure invoices are encouraged to contact our Billing Support team for assistance. Next Update: We will continue to monitor the fix implemented and will provide our next update by 16 :00 EDT on September 21, 2026 .

    15. September 21, 2026 at 6:37 PM UTCresolved

      The issue affecting Azure billing has been resolved, and all services are now operating normally. Impact Level: Resolved Latest Update: Our team successfully resolved Azure billing issue and successfully generated the complementary Azure specific invoices from the 15 and 16th of September. All customers invoiced after the 17th of September have been invoiced. Next Steps: We are conducting a thorough Root Cause Analysis (RCA) to understand why this happened and to implement safeguards preventing it from occurring again. If you are still experiencing service-related issues, please contact our support team for further assistance.

    Cloud PBX - Intermittent Phone Registration Issues

    Started September 10, 2026 at 3:08 PM UTC · 5h 11m

    IssuesMinor incident
    Affected components
    Cloud PBXSherweb Hosted ServicesPhone / SIP Device Registration
    1. September 10, 2026 at 3:08 PM UTCupdate

      We are investigating a brief issue that affected some Cloud PBX services and may have caused certain SIP phones to lose registration.

    2. September 10, 2026 at 3:10 PM UTCupdate

      Service has been restored; however, a small number of devices may remain unregistered. If your phone is showing "Phone Unregistered", "Service Down", or is unable to place or receive calls, please reboot the device to force a new registration.

    3. September 10, 2026 at 8:19 PM UTCresolved

      The issue affecting Cloud PBX - phone registration issues has been resolved, and all services are now operating normally. Impact Level: Resolved If you are still experiencing service-related issues, please contact our support team for further assistance.

    Cloud PBX - Intermittent Phone Registration Issues

    Started September 10, 2026 at 3:08 PM UTC · Ongoing

    IssuesMinor incident
    1. September 10, 2026 at 3:08 PM UTCupdate

      We are investigating a brief issue that affected some Cloud PBX services and may have caused certain SIP phones to lose registration.

    Update: Service Incident updated - Resolved

    Started September 4, 2026 at 7:01 PM UTC · 1h 13m

    IssuesMinor incident
    Affected components
    C2 ITSMSherweb Hosted ServicesProduction
    1. September 4, 2026 at 7:01 PM UTCupdate

      We are currently investigating an issue impacting C2 ITSM . Impact Level: Investigating Current Progress: Our engineering team has been mobilized and is actively investigating the problem to determine the root cause and restore service. Next update: We will provide an update within 60 minutes.

    2. September 4, 2026 at 7:16 PM UTCupdate

      This is an update regarding the ongoing disruption to our C2 ITSM environment Impact Level: Major Outage You may currently be experiencing delay accessing C2 or the inability to login into the environment Current Progress: Our team is still investigating and working on identifying the cause of the issue. Next Update: We will continue to monitor the status of service incident and will provide our next update by 17:00 EDT Sept 4th

    3. September 4, 2026 at 7:57 PM UTCupdate

      This is an update regarding the ongoing disruption to our C2 ITSM environnment Impact Level: Major Outage You may currently be experiencing delay accessing C2 or the inability to login into the environment Current Progress: Our team is actively implementing a fix to address the issue and restore full service. We are closely monitoring the changes as they are applied. Slowness and the inability to login into c2 has been resolved Next Update: We will continue to monitor the fix implemented and will provide our next update by 17:00 EDT Sept 4th

    4. September 4, 2026 at 8:14 PM UTCresolved

      The issue affecting our ITSM environment has been resolved, and all services are now operating normally. Impact Level: Resolved Latest Update: Our team successfully restarted the mail engine at 16:05 , and we have verified that system stability has returned. Next Steps: We are conducting a thorough Root Cause Analysis (RCA) to understand why this happened and to implement safeguards preventing it from occurring again. We will share the post-incident report with you by September 14th . If you are still experiencing service-related issues, please contact our support team for further assistance.

    Some users may encounter issues when trying to Login to QuickBooks Online

    Started September 1, 2026 at 8:56 PM UTC · 7h 24m

    IssuesMinor incident
    Affected components
    CanadaExternal Marketplace ServicesQuickBooks Online
    1. September 1, 2026 at 8:56 PM UTCinvestigating

      We're currently investigating an issue affecting QBO logins. Some users may also see errors while using the different features inside the application. Our engineering team is actively working to resolve this, and we'll share updates as they become available. We apologize for the inconvenience.

    2. September 1, 2026 at 9:12 PM UTCinvestigating

      We are continuing to investigate this issue.

    3. September 1, 2026 at 10:20 PM UTCinvestigating

      We are continuing to investigate this issue.

    4. September 2, 2026 at 12:02 AM UTCidentified

      Our engineering team has figured out the root cause of the issue and a fix is in deployment, we are already seeing recovery across our systems and soon the service will be fully restored. We'll share updates as they become available. We apologize for the inconvenience this caused and thank you for your patience.

    5. September 2, 2026 at 4:16 AM UTCidentified

      Our engineering team has figured out the root cause of the issue and a fix is in deployment, we are already seeing recovery across our systems and soon the service will be fully restored. We'll share updates as they become available. We apologize for the inconvenience this caused and thank you for your patience.

    6. September 2, 2026 at 4:19 AM UTCresolved

      The issue has been fixed and we confirm the system recovery across all regions. We apologize for the inconvenience this caused and thank you for your patience.

    Update: Resolved - PurelyHR website

    Started September 1, 2026 at 5:30 PM UTC · 2h 24m

    IssuesMinor incident
    Affected components
    Sherweb Hosted ServicesPurelyHR
    1. September 1, 2026 at 5:30 PM UTCupdate

      We are currently investigating an issue impacting PurelyHR Web site . Impact Level: Investigating Current Progress: Our engineering team has been mobilized and is actively investigating the problem to determine the root cause and restore service. Next update: We will provide an update within 60 minutes.

    2. September 1, 2026 at 6:11 PM UTCupdate

      This is an update regarding the ongoing disruption to PurelyHR . Impact Level: Recovering You should now be able to access the PurelyHR website ( https://www.purelyhr.com/). Current Progress: Our Team has implemented the fix, and we are monitoring the service closely to ensure stability and confirm that the issue is fully resolved. Next Update: We will continue to monitor the fix implemented and will provide our next update by 16:00 EDT.

    3. September 1, 2026 at 7:54 PM UTCresolved

      The issue affecting PurelyHR website has been resolved, and all services are now operating normally. Impact Level: Resolved Latest Update: Our team successfully implemented remediation measures at 14:00 EDT and has confirmed that website stability has been restored. Next Steps: We are conducting a thorough Root Cause Analysis (RCA) to understand why this happened and to implement safeguards preventing it from occurring again. We will share the post-incident report with you by the 8th of September . If you are still experiencing service-related issues, please contact our support team for further assistance.

    Some QuickBooks users receive errors and are unable to view transactions when searching.

    Started August 31, 2026 at 6:26 PM UTC · 2h 4m

    IssuesMinor incident
    Affected components
    CanadaExternal Marketplace ServicesQuickBooks Online
    1. August 31, 2026 at 6:26 PM UTCinvestigating

      We are currently investigating the cause of the errors when searching or viewing transactions.

    2. August 31, 2026 at 6:27 PM UTCinvestigating

      We're currently investigating an issue affecting Search. Some users may see errors or be unable to find recently added data. Our engineering team is actively working to resolve this, and we'll share updates as they become available. We apologize for the inconvenience.

    3. August 31, 2026 at 8:30 PM UTCresolved

      The search issues affecting QuickBooks have been resolved. We're continuing to monitor for full recovery. Thank you for your patience

    RESOLVED: Issue detected on Cumulus Billing engine

    Started August 27, 2026 at 9:03 PM UTC · 31m

    IssuesMinor incident
    Affected components
    APICumulus PortalBilling APIMFA: SMSShopping CartSherweb Hosted ServicesMFA: EmailGeneralShopping API
    1. August 27, 2026 at 9:03 PM UTCupdate

      We are currently investigating an issue impacting Cumulus Billing engine. Impact Level: Investigating Current Progress: Our engineering team has been mobilized and is actively investigating the problem to determine the root cause and restore service. Next update: We will provide an update within 60 minutes.

    2. August 27, 2026 at 9:34 PM UTCresolved

      This is an update regarding the ongoing disruption to Cumulus. Impact Level: Resolved Latest Update: Our team successfully identified and fixed an issue with the billing engine at 17:25 EST. The affected partners will be contacted individually. If you are still experiencing service-related issues, please contact our support team for further assistance.

    Update: Resolved - VSPC (Veeam Service Provider Console)

    Started August 21, 2026 at 4:00 PM UTC · 26d 6h

    IssuesMinor incident
    Affected components
    License rentalGeneralLicense rentalSherweb Hosted ServicesSelf-Service PortalUnited States East 1Canada East 1GeneralVeeam Service Provider ConsoleSelf-Service Portal
    1. August 21, 2026 at 4:00 PM UTCupdate

      We are currently investigating an issue impacting VSPC (Veeam Service Provider Console) Impact Level: Performance Degraded You may currently be experiencing issues with the backup usage reporting and billing within VSPC (Veeam Service Provider Console). The reporting is not functioning correctly. Billing calculations based on reported usage may be affected. No direct impact to backup operations has been identified; the issue is currently limited to reporting and billing. Current Progress: Our team is still investigating and working on identifying the cause of the issue. We have opened a ticket with Veeam to investigate the issue. Next Update: We will provide our next update by August 27th, 12:00 PM EDT

    2. August 27, 2026 at 5:16 PM UTCupdate

      We are currently investigating an issue impacting VSPC (Veeam Service Provider Console) Impact Level: Performance Degraded You may currently be experiencing issues with the backup usage reporting and billing within VSPC (Veeam Service Provider Console). The reporting is not functioning correctly. Billing calculations based on reported usage may be affected. No direct impact to backup operations has been identified; the issue is currently limited to reporting and billing. Current Progress: Our team is still investigating and working on identifying the cause of the issue. We have opened a ticket with Veeam to investigate the issue. The ticket has been escalated on their end for further investigation. Next Update: We will provide our next update by August 28th, 12:00 PM EDT

    3. August 28, 2026 at 7:21 PM UTCupdate

      We are currently investigating an issue impacting VSPC (Veeam Service Provider Console) Impact Level: Recovering Billing for the current month-end cycle is expected to proceed normally. We have implemented a workaround that allows usage data to be processed and billed as expected. Please contact us if there is any discrepancy in your expected Veeam billing for August. Next Update: We will provide our next update by August 31th, 12:00 PM EDT

    4. August 31, 2026 at 5:17 PM UTCupdate

      We are currently investigating an issue impacting VSPC (Veeam Service Provider Console) Impact Level: Recovering Billing for the current month-end cycle is expected to proceed normally. We have implemented a workaround that allows usage data to be processed and billed as expected. We are working directly with Veeam for a permanent fix. Please contact us if there is any discrepancy in your expected Veeam billing for August. Next Update: We will provide our next update by September 4th, 12:00 PM EDT

    5. September 4, 2026 at 5:56 PM UTCupdate

      We are currently investigating an issue impacting VSPC (Veeam Service Provider Console) Impact Level: Recovering Billing for the current month-end cycle is expected to proceed normally. We have implemented a workaround that allows usage data to be processed and billed as expected. We still working directly with Veeam for a permanent fix. Please contact us if there is any discrepancy in your expected Veeam billing for August. Next Update: We will provide our next update by September 8th, 12:00 PM EDT

    6. September 11, 2026 at 5:17 PM UTCupdate

      We are currently investigating an issue impacting VSPC (Veeam Service Provider Console) Impact Level: Recovering The affected server has been updated, and usage data is now reporting as expected. We will continue to monitor over the weekend to ensure everything is fully recovered. Please contact us if there is any discrepancy in your expected Veeam billing for August. Next Update: We will provide our next update by September 14th, 12:00 PM EDT

    7. September 16, 2026 at 10:09 PM UTCresolved

      The issue affecting VSPC (Veeam Service Provider Console) has been resolved, and all services are now operating normally. Impact Level: Resolved Latest Update: We have confirmed the usage data is reporting as expected. Next Steps: We are conducting a thorough Root Cause Analysis (RCA) to understand why this happened and to implement safeguards preventing it from occurring again. If you are still experiencing service-related issues, please contact our support team for further assistance.

    Update: Closed - Technical Support

    Started August 20, 2026 at 1:41 PM UTC · 6h 4m

    IssuesMinor incident
    Affected components
    Technical SupportGeneral
    1. August 20, 2026 at 1:41 PM UTCupdate

      We are currently investigating an issue impacting our technical support tools . Impact Level: Investigating Current Progress: Our engineering team has been mobilized and is actively investigating the problem to determine the root cause and restore service. Next update: We will provide an update within 60 minutes.

    2. August 20, 2026 at 2:20 PM UTCupdate

      This is an update regarding the ongoing disruption to our technical support tools . Impact Level: Investigating You may currently experience longer than expected delays when contacting our different support teams by email, chat or phone. Current Progress: Our team is still investigating and working on identifying the cause of the issue. Next Update: We will continue to monitor the status of service incident and will provide our next update by 11:30 EDT.

    3. August 20, 2026 at 3:18 PM UTCupdate

      This is an update regarding the ongoing disruption to our technical support tools . Impact Level: Investigating You may currently experience longer than normal wait times when contacting our support teams by email, chat, or phone. Customers may also encounter intermittent call failures when attempting to reach our teams. Current Progress: Our team is still investigating and working on identifying the cause of the issue. Next Update: We will continue to monitor the status of service incident and will provide our next update by 13:00 EDT.

    4. August 20, 2026 at 5:03 PM UTCupdate

      This is an update regarding the ongoing disruption to our technical support . Impact Level: Recovering You should now be able to contact our teams normally through email, chat and phone services. Current Progress: A fix was implemented, and we are monitoring the service closely to ensure stability and confirm that the issue is fully resolved. Next Update: We will continue to monitor the fix implemented and will provide our next update by 16:00 EDT .

    5. August 20, 2026 at 7:45 PM UTCresolved

      The issue affecting ur technical support has been resolved, and all services are now operating normally. Impact Level: Resolved Latest Update: A fix was successfully implemented at 11:45 EDT , and we have verified that system stability has returned. Next Steps: We are conducting a thorough Root Cause Analysis (RCA) to understand why this happened and to implement safeguards preventing it from occurring again. If you experience service-related issues, please contact our support team for further assistance.

    Quickbooks Online Latency Issue

    Started August 19, 2026 at 2:30 PM UTC · 2h 23m

    IssuesMinor incident
    Affected components
    CanadaExternal Marketplace ServicesQuickBooks Online
    1. August 19, 2026 at 2:30 PM UTCinvestigating

      We are aware that some customers are experiencing latency when using QuickBooks Online. Our engineering team is actively investigating the issue to identify the root cause and restore normal performance as quickly as possible. We appreciate your patience and will provide further updates as more information becomes available.

    2. August 19, 2026 at 4:13 PM UTCmonitoring

      The latency issue with QuickBooks has been resolved. Engineering Team have implemented a fix and continue to monitor for full recovery

    3. August 19, 2026 at 4:54 PM UTCresolved

      Earlier today, some users experienced issues with QuickBooks Online (QBO) features. Our teams have identified and resolved the underlying problem. All services are now restored and functioning normally. We appreciate your understanding and patience.

    Update: Resolved - Cumulus

    Started August 3, 2026 at 6:53 PM UTC · 1d 19h

    IssuesMinor incident
    Affected components
    APICumulus PortalBilling APIMFA: SMSShopping CartSherweb Hosted ServicesMFA: EmailGeneralShopping API
    1. August 3, 2026 at 6:53 PM UTCupdate

      We are currently investigating an issue impacting Cumulus. Impact Level: Partial Outage You may currently be experiencing Users accessing Cumulus through Firefox may be unable to access organization pages. A generic application error is displayed when opening organizations, preventing navigation and management activities. The issue appears to affect all organizations tested and may impact any partner using Firefox as their primary browser. Current Progress: Our team is still investigating and working on identifying the cause of the issue. Workaround: While we work to fully resolve this issue, you can temporarily bypass the problem by using Chrome or another supported browser until the issue is resolved. Next Update: We will provide our next update by 2026-08-04 12:00 EST

    2. August 4, 2026 at 3:49 PM UTCupdate

      This is an update regarding the ongoing disruption to Cumulus. Impact Level: Partial Outage You may currently be experiencing Users accessing Cumulus through Firefox may be unable to access organisation pages. A generic application error is displayed when opening organisations, preventing navigation and management activities. The issue appears to affect all organisations tested and may impact any partner using Firefox as their primary browser. Current Progress: Our team is still investigating and working on identifying the cause of the issue. Workaround: While we work to fully resolve this issue, you can temporarily bypass the problem by using Chrome or another supported browser until the issue is resolved. Next Update: We will provide our next update by 2026-08-05 12:00PM EST

    3. August 5, 2026 at 2:39 PM UTCresolved

      Title Subject: Update: Resolved - Cumulus This is an update regarding the ongoing disruption to Cumulus. Impact Level: Resolved Latest Update: Our team successfully fixed a JavaScript exception originating from a third-party widget is being logged when opening organisation pages in Firefox. The widget intermittently failed to load correctly due to an issue on the vendor's infrastructure. Cumulus didn't handle that failure gracefully. Now if the widget fails to load or execute properly, the rest of the page is not impacted anymore. at 1:27 PM, August 5th, 2026, and we have verified that system stability has returned. If you are still experiencing service-related issues, please contact our support team for further assistance.