Carbonite Outage History

Carbonite is up right now

Pingoru has recorded 180 incidents for Carbonite: 180 in the last 12 months and 38 in the last 90 days.

Source: status.carbonite.com

180incidents recorded
180last 12 months
38last 90 days
45 hourstypical duration
Incidents per month
02040AprMayJunJulAugSepOct14
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct54%
Pingoru began tracking Carbonite in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202617432 of 720 (60%)
May 202623605 of 744 (81%)
June 202634460 of 720 (64%)
July 202626469 of 744 (63%)
August 202613273 of 744 (37%)
September 20268239 of 720 (33%)
October 202614322 of 594 (54%)

Incidents, newest first

Notice January 29, 2026 Core Messaging - Email may have experienced intermittent message delivery delays – Core Messaging - Email

Started Jan 29, 2026, 09:46 PM UTC· resolved Jan 29, 2026, 09:46 PM UTC

  1. resolved Jan 29, 2026, 09:46 PM UTC

    Core Messaging - Email may have experienced intermittent message delivery delays, which started on 23 January 2026 at 05:00 UTC. Service has been restored on 29 January 2026 at 21:41 UTC. The issue is now resolved. We appreciate your patience. Tracking Number: IM3859146

Read the full incident report →

Notice January 29, 2026 Email Delay Opening Tickets 5h 35m Zix Support Infrastructure - Support Ticketing System

Started Jan 29, 2026, 03:43 PM UTC· resolved Jan 29, 2026, 09:18 PM UTC

  1. investigating Jan 29, 2026, 03:43 PM UTC

    Email to our ticketing system is currently experiencing issues with long delays. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: OTSM 51714775

  2. monitoring Jan 29, 2026, 05:55 PM UTC

    Email to our ticketing system experienced an issue with long delays. Service has been restored and is now being validated. We appreciate your patience. Tracking Number: OTSM 51714775

  3. resolved Jan 29, 2026, 09:18 PM UTC

    Email to our ticketing system experienced an issue with long delays. The issue is now resolved. We appreciate your patience. Tracking Number: OTSM 51714775

Read the full incident report →

Major January 29, 2026 Core Secure Access and Core Collaboration Access was unavailable. 1h 29m B2B Connect, Core Collaboration Access, Core Secure Access, ProviderLink and 2 more

Started Jan 29, 2026, 02:33 PM UTC· resolved Jan 29, 2026, 04:03 PM UTC

  1. investigating Jan 29, 2026, 02:33 PM UTC

    The following services are unavailable. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - OpenText Core Secure Access - OpenText Core Collaboration Access - ProviderLink login - B2B Connect (formerly Covisint Connect) login and UI capability; messaging is currently not impacted. - Supplier Connection login and UI; messaging is currently not impacted. Tracking Number: IM3860358

  2. investigating Jan 29, 2026, 03:30 PM UTC

    The following services are unavailable. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - OpenText Core Secure Access - OpenText Core Collaboration Access - ProviderLink login - B2B Connect (formerly Covisint Connect) login and UI capability; messaging is currently not impacted. - Supplier Connection login and UI; messaging is currently not impacted. Tracking Number: IM3860358

  3. monitoring Jan 29, 2026, 03:51 PM UTC

    The following services experienced an issue and have been restored. - ProviderLink login - B2B Connect (formerly Covisint Connect) login and UI capability; messaging was not impacted. - Supplier Connection login and UI; messaging was not impacted. - Supplier Portal Core Secure Access and Core Collaboration Access are still being validated. We appreciate your patience. Tracking Number: IM3860358

  4. resolved Jan 29, 2026, 04:03 PM UTC

    The following services experienced an issue and have all been restored. The issue is now resolved. We appreciate your patience. - OpenText Core Secure Access - OpenText Core Collaboration Access - ProviderLink login - B2B Connect (formerly Covisint Connect) login and UI capability; messaging is currently not impacted. - Supplier Connection login and UI; messaging is currently not impacted. Tracking Number: IM3860358

Read the full incident report →

Notice January 22, 2026 Zix - Microsoft 365 - Unable to send/receive 17h 1m Zix Office 365

Started Jan 22, 2026, 07:59 PM UTC· resolved Jan 23, 2026, 01:01 PM UTC

  1. investigating Jan 22, 2026, 07:59 PM UTC

    We are getting multiple reports of M365 users unable to send or receive emails. Microsoft has posted a couple of Service Alerts due to the volume of reports. At this time, the server alerts are providing general information. We will post an update as soon as they provide more details. Microsoft Service Alerts: Issue ID - MO1221364 As Microsoft rapidly pursue an investigation into the nature of the impact and the source of the issue, Microsoft received reports that users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to access the service portals or use Outlook Issue ID - EX1221363 Microsoft is investigating a potential issue and checking for impact to your organization. Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods.

  2. investigating Jan 22, 2026, 08:05 PM UTC

    Update from Microsoft: Issue ID - MO1221364 Some of the impacted service functions include, but may not be limited to: - Sending and receiving email through Exchange Online - Accessing service portals

  3. identified Jan 22, 2026, 08:44 PM UTC

    Update from Microsoft: Issue ID - MO1221364 Microsoft identified a portion of dependent service infrastructure in the North America region that is not processing traffic as expected. This is impacting Microsoft load balancing processes and general service availability. Microsoft is working to restore this infrastructure to a heathy state and rebalance the service traffic to achieve recovery.

  4. identified Jan 22, 2026, 09:18 PM UTC

    Update from Microsoft: Issue ID - MO1221364 Current status: While Microsoft restored the affected infrastructure to a heathy state, further load balancing is required to mitigate persistent impact. Microsoft identified and are implementing additional actions to direct requests and traffic to additional healthy sections of infrastructure to achieve withstanding recovery.

  5. identified Jan 22, 2026, 10:11 PM UTC

    Issue ID - MO1221364 Microsoft has implemented a traffic balancing solution within a limited portion of infrastructure and telemetry shows success. Microsoft is applying this solution incrementally across all affected infrastructure to ensure the environment remains balanced as recovery continues. This quick update is designed to give the latest information on this issue.

  6. identified Jan 22, 2026, 11:19 PM UTC

    Update from Microsoft: Issue ID - MO1221364 Current status: Microsoft is carefully rebalancing traffic across all affected infrastructure in the region, while monitoring the corresponding health telemetry, to ensure the environment enters into a balanced state as their remediation efforts continue. Microsoft is proceeding as quickly as possible and this incremental approach will also help them identify whether any additional actions may be required to ensure longstanding recovery.

  7. identified Jan 23, 2026, 01:50 AM UTC

    Update from Microsoft: Issue ID - MO1221364 Current status: Microsoft is continuing to refine their load balancing configurations to remedy residual imbalances across the environment and further their ongoing recovery efforts.

  8. monitoring Jan 23, 2026, 02:57 AM UTC

    Update from Microsoft: Issue ID - MO1221364 Microsoft is seeing continued improvements in service availability and functionality as a result of our load-balancing efforts. Microsoft is actively monitoring performance and making targeted adjustments to further improve stability and availability, while continuing recovery actions to ensure a reliable service experience.

  9. resolved Jan 23, 2026, 01:01 PM UTC

    Update from Microsoft: Microsoft confirmed that the affected infrastructure has returned to a healthy state and is operating as expected. Microsoft will continue to closely monitor the remediation actions taken and make any necessary adjustments to maintain stability. If users experience any residual issues, clearing local DNS caches or temporarily lowering DNS TTL values may help ensure a quicker remediation.

Read the full incident report →

Minor January 20, 2026 Core US is currently degraded 1h 29m Core Collaboration for Engineering (xchange.us.opentext.com), Core Content Management (corecontent.us.opentext.com), Core Content Management for SAP® SuccessFactors | SAP® SuccessFactors Document Management Core by OpenText, Core Digital Asset Management (coredam.us.opentext.com)

Started Jan 20, 2026, 08:15 PM UTC· resolved Jan 20, 2026, 09:44 PM UTC

  1. investigating Jan 20, 2026, 08:15 PM UTC

    Core US is currently degraded. Teams are being assembled to investigate and provide resolution.

  2. monitoring Jan 20, 2026, 08:34 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jan 20, 2026, 09:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 13, 2026 Core Fax North America was experiencing degradation in service 3h 7m Core Fax - US

Started Jan 13, 2026, 10:34 PM UTC· resolved Jan 14, 2026, 01:41 AM UTC

  1. investigating Jan 13, 2026, 10:33 PM UTC

    Core Fax Canada and North America are experiencing degradation in service. Backlogs exists. Teams are assembled and troubleshooting the issue. We appreciate your patience. Tracking Number: IM3851319

  2. investigating Jan 13, 2026, 10:34 PM UTC

    Core Fax North America only is experiencing degradation in service. Backlogs exist. Teams are assembled and troubleshooting the issue. We appreciate your patience. Tracking Number: IM3851319

  3. investigating Jan 13, 2026, 10:51 PM UTC

    Core Fax North America is experiencing degradation in service. Backlogs exist. Teams are assembled and troubleshooting the issue. We appreciate your patience. Tracking Number: IM3851319

  4. investigating Jan 13, 2026, 11:37 PM UTC

    Core Fax North America is experiencing degradation in service. Backlogs exist. Teams are assembled and troubleshooting the issue. Updates for this issue will be sent every 2 hours or if there are significant updates, whichever comes first. We appreciate your patience. We appreciate your patience. Tracking Number: IM3851319

  5. investigating Jan 14, 2026, 01:40 AM UTC

    Core Fax North America was experiencing degradation in service. Backlogs have been cleared. The issue is now resolved. We appreciate your patience. Tracking Number: IM3851319

  6. resolved Jan 14, 2026, 01:41 AM UTC

    Core Fax North America was experiencing degradation in service. Backlogs have been cleared. The issue is now resolved. We appreciate your patience. Tracking Number: IM3851319

Read the full incident report →

Minor January 12, 2026 Zix Encryption Services - Email Message Privacy (EMP) - Unable to Compose for some US domains 8h 59m Zix Encryption Services - Email Message Privacy (EMP)

Started Jan 12, 2026, 02:53 PM UTC· resolved Jan 12, 2026, 11:52 PM UTC

  1. investigating Jan 12, 2026, 02:53 PM UTC

    Zix Encryption Services - Email Message Privacy (EMP) is currently experiencing an issue with some US domains receiving an error when composing a secure message. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number:

  2. investigating Jan 12, 2026, 02:53 PM UTC

    (Updated Tracking Number) Zix Encryption Services - Email Message Privacy (EMP) is currently experiencing an issue with some US domains receiving an error when composing a secure message. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3849179

  3. monitoring Jan 12, 2026, 04:26 PM UTC

    Zix Encryption Services - Email Message Privacy (EMP) experienced an issue with some US domains receiving an error when composing a secure message. Service has been restored and is now being validated. We appreciate your patience. Tracking Number: IM3849179

  4. resolved Jan 12, 2026, 11:52 PM UTC

    Zix Encryption Services - Email Message Privacy (EMP) experienced an issue with some US domains receiving an error when composing a secure message. The issue is now resolved. We appreciate your patience. Tracking Number: IM3849179

Read the full incident report →

Minor January 6, 2026 Zix Encryption Services - Email Message Privacy (EMP) - Australian Users having issues composing 5d 22h Zix Encryption Services - Email Message Privacy (EMP)

Started Jan 06, 2026, 04:04 PM UTC· resolved Jan 12, 2026, 03:01 PM UTC

  1. investigating Jan 06, 2026, 04:04 PM UTC

    Zix Encryption Services - Email Message Privacy (EMP) is currently experiencing an issue with Australian users having issues composing secure messages. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3846958

  2. investigating Jan 08, 2026, 05:55 PM UTC

    Zix Encryption Services - Email Message Privacy (EMP) is still experiencing an issue with Australian users having issues composing secure messages. Teams have assembled and are working to resolve the issue. We appreciate your patience. Tracking Number: IM3846958

  3. resolved Jan 12, 2026, 03:01 PM UTC

    Zix Encryption Services - Email Message Privacy (EMP) experienced an issue with Australian users having issues composing secure messages. The issue is now resolved. We appreciate your patience. Tracking Number: IM3846958

Read the full incident report →

Minor December 6, 2025 Cloud Fax services experienced service interruption 54d 3h Desktop Messaging BMS, Desktop Messaging BMS, Desktop Messaging BMS, Fax Cloud Connect (RightFax) and 3 more

Started Dec 06, 2025, 01:55 PM UTC· resolved Jan 29, 2026, 05:31 PM UTC

  1. investigating Dec 04, 2025, 06:58 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) Updates for this issue will be sent every 5 hours or if there are significant updates, whichever comes first. Tracking Number: IM3714284

  2. investigating Dec 04, 2025, 08:29 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) The tracking number has been updated to reflect the correct ticket number that is being used for this incident. Updates for this issue will be sent every 5 hours or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  3. investigating Dec 05, 2025, 12:00 AM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) Updates for this issue will be sent every 5 hours or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  4. investigating Dec 05, 2025, 05:07 AM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) Updates for this issue will be sent every 8 hours or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  5. investigating Dec 05, 2025, 01:07 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) Updates for this issue will be sent every 8 hours or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  6. investigating Dec 05, 2025, 09:11 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) Updates for this issue will be sent every 12 hours or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  7. investigating Dec 06, 2025, 01:55 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) Updates for this issue will be sent every 12 hours or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  8. investigating Dec 07, 2025, 02:30 AM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) Updates for this issue will be sent every 12 hours or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  9. investigating Dec 07, 2025, 02:31 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) Updates for this issue will be sent every 12 hours or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  10. investigating Dec 08, 2025, 02:35 AM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) Updates for this issue will be sent every 12 hours or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  11. investigating Dec 08, 2025, 02:41 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) Updates for this issue will be sent every 12 hours or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  12. investigating Dec 09, 2025, 02:51 AM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) Updates for this issue will be sent every 12 hours or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  13. investigating Dec 09, 2025, 02:50 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) Updates for this issue will be sent every 12 hours or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  14. investigating Dec 10, 2025, 03:09 AM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) Updates for this issue will be sent every 12 hours or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  15. investigating Dec 10, 2025, 02:34 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) Updates for this issue will be sent every 12 hours or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  16. investigating Dec 11, 2025, 02:34 AM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) Updates for this issue will be sent every 12 hours or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  17. investigating Dec 11, 2025, 02:31 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) Updates for this issue will be sent every 12 hours or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  18. investigating Dec 12, 2025, 03:25 AM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) Updates for this issue will be sent every 12 hours or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  19. investigating Dec 12, 2025, 02:30 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) The next update for this issue will be sent on 15 December 2025 at 14:30 GMT or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  20. investigating Dec 15, 2025, 02:30 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) The next update for this issue will be sent on 16 December 2025 at 14:30 GMT or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  21. investigating Dec 16, 2025, 04:02 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) The next update for this issue will be sent on 17 December 2025 at 16:00 GMT or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  22. investigating Dec 17, 2025, 04:30 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) The next update for this issue will be sent on 18 December 2025 at 16:30 GMT or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  23. investigating Dec 18, 2025, 04:00 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) The next update for this issue will be sent on 19 December 2025 at 16:00 GMT or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  24. investigating Dec 19, 2025, 05:51 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) The next update for this issue will be sent on 22 December 2025 at 16:00 GMT or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  25. investigating Dec 22, 2025, 04:10 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) The next update for this issue will be sent on 23 December 2025 at 16:00 GMT or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  26. investigating Dec 23, 2025, 04:02 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) The next update for this issue will be sent on 24 December 2025 at 16:00 GMT or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  27. investigating Dec 24, 2025, 06:21 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) The next update for this issue will be sent on 26 December 2025 at 16:00 GMT or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  28. investigating Dec 26, 2025, 04:11 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) The next update for this issue will be sent on 29 December 2025 at 16:00 GMT or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  29. investigating Dec 29, 2025, 04:03 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) The next update for this issue will be sent on 31 December 2025 at 16:00 GMT or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  30. investigating Dec 31, 2025, 04:44 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) The next update for this issue will be sent on 2 January 2026 at 16:00 GMT or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  31. investigating Jan 02, 2026, 04:16 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) The next update for this issue will be sent on 5 January 2026 at 16:00 GMT or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  32. investigating Jan 05, 2026, 05:08 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) The next update for this issue will be sent on 7 January 2026 at 16:00 GMT or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  33. investigating Jan 07, 2026, 04:00 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) The next update for this issue will be sent on 9 January 2026 at 16:00 GMT or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  34. investigating Jan 09, 2026, 04:00 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) The next update for this issue will be sent on 12 January 2026 at 16:00 GMT or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  35. investigating Jan 12, 2026, 04:01 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) The next update for this issue will be sent on 14 January 2026 at 16:00 GMT or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  36. investigating Jan 14, 2026, 04:00 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) The next update for this issue will be sent on 16 January 2026 at 16:00 GMT or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  37. investigating Jan 16, 2026, 04:00 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) The next update for this issue will be sent on 19 January 2026 at 16:00 GMT or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  38. investigating Jan 19, 2026, 05:00 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) The next update for this issue will be sent on 21 January 2026 at 16:00 GMT or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  39. investigating Jan 21, 2026, 07:15 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) The next update for this issue will be sent on 23 January 2026 at 16:00 GMT or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  40. investigating Jan 23, 2026, 04:03 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) The next update for this issue will be sent on 26 January 2026 at 16:00 GMT or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  41. investigating Jan 26, 2026, 06:45 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) The next update for this issue will be sent on 28 January 2026 at 16:00 GMT or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  42. investigating Jan 28, 2026, 06:31 PM UTC

    The following services may be experiencing service interruption with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC. Teams are currently assembled and working to resolve the issue. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) The next update for this issue will be sent on 30 January 2026 at 16:00 GMT or if there are significant updates, whichever comes first. Tracking Number: IM3830090

  43. resolved Jan 29, 2026, 05:31 PM UTC

    The following services experienced an issue with EMEA regional numbers. The issue started on 2 December 2025 at 09:00 UTC and is now resolved. We appreciate your patience. - Desktop Messaging BMS (APAC, EMEA, NA) - Fax Cloud Connect (EMEA, NA) - Fax2Mail (EMEA, NA) Tracking Number: IM3830090

Read the full incident report →

Notice December 1, 2025 Zix Encryption Services - ZixPortal - Sporadic Issues with receiving OTP 50d 18h Secure Messaging Portal (ZixPortal)

Started Dec 01, 2025, 07:45 PM UTC· resolved Jan 21, 2026, 01:55 PM UTC

  1. identified Dec 01, 2025, 07:45 PM UTC

    The Zix Encryption Services - ZixPortal users are currently experiencing sporadic issues when trying to receive the system-generated OTP code. Teams are currently assembled and working to resolve the issue as quickly as possible. We appreciate your patience. Here are some notes we have seen: - Email addresses should be entered in all lowercase. - Try using the incognito version of your browser Tracking Number: 251106-000617

  2. identified Dec 02, 2025, 08:41 PM UTC

    The Zix Encryption Services - ZixPortal users are currently experiencing sporadic issues when trying to receive the system-generated OTP code. Teams are assembled and working to resolve the issue as quickly as possible, but it will take time to resolve. We appreciate your patience. Here are some notes we have seen: - Email addresses should be entered in all lowercase. - Try using the incognito version of your browser Tracking Number: 251106-000617

  3. identified Dec 05, 2025, 08:07 PM UTC

    The Zix Encryption Services - ZixPortal users are currently experiencing sporadic issues when trying to receive the system-generated OTP code. Teams have assembled and are working to resolve the issue as quickly as possible, but it will take time to resolve. Updates will only be posted when there is a significant change. We appreciate your patience. Here are some notes we have seen: - Email addresses should be entered in all lowercase. - Try using the incognito version of your browser Tracking Number: 251106-000617

  4. identified Dec 15, 2025, 01:48 PM UTC

    The Zix Encryption Services - ZixPortal users are currently experiencing sporadic issues when trying to receive the system-generated OTP code. Teams have worked to resolve the issue as quickly as possible. The fix should be implemented after the year-end change freeze is lifted. Updates will only be posted when there is a significant change. We appreciate your patience. Here are some notes we have seen: - Email addresses should be entered in all lowercase. - Try using the incognito version of your browser Tracking Number: 251106-000617

  5. identified Dec 29, 2025, 05:34 PM UTC

    The Zix Encryption Services - ZixPortal users are currently experiencing sporadic issues when trying to receive the system-generated OTP code. The Dev Teams have completed a resolution to the issue. The fix should be implemented after the year-end change freeze is lifted and change notifications sent. Updates will only be posted when there is a significant change. We appreciate your patience. Here are some notes we have seen: - Email addresses should be entered in all lowercase. - Try using the incognito version of your browser Tracking Number: 251106-000617

  6. identified Jan 05, 2026, 10:07 PM UTC

    The Zix Encryption Services - ZixPortal users are currently experiencing sporadic issues when trying to receive the system-generated OTP code. The Dev Teams have completed a resolution to the issue. The fix should be implemented 18 Jan 2026 during our maintenance window. Updates will only be posted when there is a significant change. We appreciate your patience. Here are some notes we have seen: - Email addresses should be entered in all lowercase. - Try using the incognito version of your browser Tracking Number: 251106-000617

  7. resolved Jan 21, 2026, 01:55 PM UTC

    The Zix Encryption Services - ZixPortal users are currently experiencing sporadic issues when trying to receive the system-generated OTP code. The DEV teams have implemented the resolution. Tracking Number: 251106-000617

Read the full incident report →