Jenzabar Outage History

Jenzabar is up right now

Jenzabar had 13 outages in the last 2 years totaling 370h 18m of downtime — averaging 0.5 incidents per month.

There were 13 Jenzabar outages since July 19, 2024 totaling 370h 18m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.jenzabarcloud.com

Notice December 9, 2025

Cloudflare Outage, December 5th

Detected by Pingoru
Dec 09, 2025, 12:41 PM UTC
Resolved
Dec 05, 2025, 08:00 AM UTC
Duration
Timeline · 1 update
  1. resolved Dec 09, 2025, 12:41 PM UTC

    On December 5th, a portion of Cloudflare routed traffic experience an outage of approximately 25 minutes, from 08:47 UTC to 09:12 UTC. During this time, customer public-facing websites could have experience an outage that would have resulted in HTTP 500 errors being served to clients. This did directly impact some of Jenzabar's hosted clients. The issue was not caused, directly or indirectly, by a cyber attack on Cloudflare’s systems or malicious activity of any kind to customer systems. Rather, it was triggered by Cloudflare internal changes attempting to detect and mitigate an industry-wide vulnerability disclosed late last week regarding React Server Components. This outage was not caused by any Jenzabar related changes. You can read more about the Cloudflare outage here: https://blog.cloudflare.com/5-december-2025-outage/ You can read more about the React Server Components here: https://blog.cloudflare.com/waf-rules-react-vulnerability/

Read the full incident report →

Major November 18, 2025

CloudFlare Outage affecting JAAS customers

Detected by Pingoru
Nov 18, 2025, 02:32 PM UTC
Resolved
Nov 18, 2025, 06:56 PM UTC
Duration
4h 24m
Affected: North America EastNorth America CentralUS Central 1US East 1SONISUS East 5Jenzabar One & EXUS West 1Higher ReachCX
Timeline · 3 updates
  1. monitoring Nov 18, 2025, 02:32 PM UTC

    Our DNS provider, CloudFlare, is experiencing an outage that may affect JAAS customers. They are working to resolve the issue, but users of jenzabarcloud.com may experience intermittent disruptions. You can follow the status directly from CloudFlare here https://www.cloudflarestatus.com/

  2. monitoring Nov 18, 2025, 02:33 PM UTC

    We are continuing to monitor for any further issues.

  3. resolved Nov 18, 2025, 06:56 PM UTC

    CloudFlare has reported that the incident is now resolved and all operations are back to functioning as expected. If you feel you're still suffering some anything related to this event please submit a support ticket and we can investigate further!

Read the full incident report →

Notice October 31, 2025

Jenzabar Support Portal

Detected by Pingoru
Oct 31, 2025, 05:50 PM UTC
Resolved
Nov 01, 2025, 11:07 AM UTC
Duration
17h 17m
Affected: North America EastNorth America CentralUS Central 1US East 1SONISUS East 5Jenzabar One & EXUS West 1Higher ReachCX
Timeline · 2 updates
  1. investigating Oct 31, 2025, 05:50 PM UTC

    We are currently experiencing a known outage affecting support.jenzabar.com. Our IT team is actively working to resolve the issue and restore full functionality as quickly as possible. What you need to know: • Impact: Access to support.jenzabar.com is unavailable. • Next Update: We will provide additional information as soon as it becomes available. If you need immediate assistance, please email [email protected]. We apologize for any inconvenience this may cause and appreciate your patience while we work to resolve the issue.

  2. resolved Nov 01, 2025, 11:07 AM UTC

    Our IT team resolved the issue with support.jenzabar.com. Please return to the portal for all your support needs. We apologize for any inconvenience this may cause and appreciate your patience.

Read the full incident report →

Notice October 22, 2025

Host Failure In North America Central

Detected by Pingoru
Oct 22, 2025, 07:02 PM UTC
Resolved
Oct 22, 2025, 08:44 PM UTC
Duration
1h 41m
Affected: North America Central
Timeline · 2 updates
  1. identified Oct 22, 2025, 07:02 PM UTC

    Jenzabar Cloud Services detected a host failure in our North America Central data center location. The host has been taken out of service at this time, and all customer workloads carried by this host have been restarted on other hosts within the cluster.

  2. resolved Oct 22, 2025, 08:44 PM UTC

    All issues with the faulty host have been identified and corrected at this time. No additional interruptions to customer workloads have taken place through this process.

Read the full incident report →

Minor September 22, 2025

Edge Router Memory Issue - HA Failover Planned 11am EST

Detected by Pingoru
Sep 22, 2025, 03:30 PM UTC
Resolved
Sep 22, 2025, 05:13 PM UTC
Duration
1h 43m
Affected: North America East
Timeline · 2 updates
  1. identified Sep 22, 2025, 03:30 PM UTC

    Cloud Infrastructure engineers have been closely monitoring a router's health in our North America East IBM data center region. Currently there are no known outages, but due to growing concerns for this particular router, we will be performing a failover to a secondary unit so that further troubleshooting and corrective actions can be taken before the situation worsens. Failover Scheduled When: September 22nd @ 11:45am EST Duration: 0-20 seconds What to expect: at most, a very brief interruption of public traffic could be expected. Internal systems will remain connected to one another during this process. This issue does not affect our other Data Center locations. We apologize for any inconvenience. Cloud Infrastructure

  2. resolved Sep 22, 2025, 05:13 PM UTC

    The failover took place at 11:45am EST as planned, with any potential disruption right at 11:46:19am EST. We thank you for your patience during this procedure - all systems are operating normally at this time. -Cloud Infrastructure

Read the full incident report →

Minor September 18, 2025

Dallas VPN Edge Node Memory Issues

Detected by Pingoru
Sep 18, 2025, 03:56 PM UTC
Resolved
Sep 18, 2025, 07:02 PM UTC
Duration
3h 5m
Affected: North America Central
Timeline · 3 updates
  1. identified Sep 18, 2025, 03:56 PM UTC

    Jenzabar's Cloud Infrastructure team has identified a memory issue on 2 of the edge nodes within the firewall/VPN cluster in our Dallas location. In order to correct this issue, services will be transitioned to other edge nodes within the cluster at 12:00pm EST. This will cause a brief VPN outage (1-5 seconds) for customers currently running on either of these two edge nodes. We apologize for the inconvenience.

  2. monitoring Sep 18, 2025, 04:18 PM UTC

    The maintenance has been performed and we believe the issues to be resolved at this time. We are continuing to monitor resources on our side and will close out this incident accordingly. Thank you for your patience during this process!

  3. resolved Sep 18, 2025, 07:02 PM UTC

    The maintenance performed at noon EST today has corrected the issue.

Read the full incident report →

Major April 28, 2025

Network connectivity issue in North America East datacenter

Detected by Pingoru
Apr 28, 2025, 01:31 PM UTC
Resolved
Apr 28, 2025, 03:25 PM UTC
Duration
1h 54m
Affected: North America East
Timeline · 2 updates
  1. investigating Apr 28, 2025, 01:31 PM UTC

    We are currently investigating a network connectivity issue in our North America East datacenter. At this time, all connectivity issues appear to be isolated to the North America East location only.

  2. resolved Apr 28, 2025, 03:25 PM UTC

    The Cloud Infrastructure team was able to correct the issue -- all connectivity issues that were present before should no longer be a problem at this time. Additionally, there are on-going efforts to find out why this keeps happening. Cloud Infrastructure is currently working with IBM to determine next steps and develop an action plan to help keep this from happening in the future.

Read the full incident report →

Notice March 29, 2025

Network connectivity issues in datacenter

Detected by Pingoru
Mar 29, 2025, 12:42 AM UTC
Resolved
Mar 29, 2025, 01:06 PM UTC
Duration
12h 24m
Affected: North America East
Timeline · 3 updates
  1. investigating Mar 29, 2025, 12:42 AM UTC

    Jenzabar is aware of connectivity issues within our North America East data center. We are working to investigate the problem further. At this time, all connectivity issues appear to be isolated to the North America East location only.

  2. monitoring Mar 29, 2025, 01:07 AM UTC

    Jenzabar engineers have identified the cause of the intermittent outages and implemented measures to mitigate the issue. The situation is being monitored.

  3. resolved Mar 29, 2025, 01:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 10, 2024

Networking Hardware Issues Discovered

Detected by Pingoru
Dec 10, 2024, 08:37 PM UTC
Resolved
Dec 12, 2024, 01:42 PM UTC
Duration
1d 17h
Affected: North America East
Timeline · 5 updates
  1. investigating Dec 10, 2024, 08:37 PM UTC

    Addition issues were discovered with one of the edge firewalls in our North America East location. This a continuation of the issues discovered yesterday, December 9th, and we will be working to restore full functionality. At this time, all systems are up and operational, however there may be brief moments of dropped packets in flight between this cluster and the internet. We hope to have an update within the hour.

  2. identified Dec 10, 2024, 08:59 PM UTC

    Jenzabar Cloud Infrastructure has identified and isolated improperly functioning hardware and is currently working with IBM support to take corrective action. Additionally, an unexpected failover event took place at the following time: 2024/12/10 15:11:37 EST Cloud infrastructure isolated the bad hardware and performed another failover at: 2024/12/10 15:47:12 Disconnects to hosted resources could have occurred during the times mentioned above. At this time, we expect all services to remain stable. Please stay tuned as we will continue to provide updates as they are available.

  3. monitoring Dec 11, 2024, 02:47 AM UTC

    Work is still being performed in the IBM data center. All systems have remained stable since the last update and are expected to remain stable at this time. We will continue to monitor the status of this and will provide another update when it is available.

  4. monitoring Dec 11, 2024, 01:41 PM UTC

    Update: As of 2024/12/11 04:30 EST, corrective changes were completed by IBM technicians. Since that time, systems have been monitored throughout this event and no further failover conditions have taken place since the last one yesterday, at 2024/12/10 15:47:12. Jenzabar Cloud Infrastructure will continue to monitor the environment for the next 24 hours before marking this incident as resolved. If you have any questions, concerns, or issues to report, please report them through normal channels at this time. Jenzabar Cloud Infrastructure

  5. resolved Dec 12, 2024, 01:42 PM UTC

    At this time, all hardware is in great standing in our North America East data center location and no further corrective action is needed within the cluster. Marking this incident as resolved.

Read the full incident report →

Minor December 9, 2024

Network Issues Identified

Detected by Pingoru
Dec 09, 2024, 09:42 PM UTC
Resolved
Dec 10, 2024, 02:49 AM UTC
Duration
5h 7m
Affected: North America East
Timeline · 2 updates
  1. identified Dec 09, 2024, 09:42 PM UTC

    Emergency network configuration changes December 9th, starting at 9pm EST. We have discovered an issue with one of the edge firewalls in our North America East location that will require emergency work later tonight, December 9th, starting at around 9pm EST. Work should be concluded by 11pm EST. Currently, no outages have been caused by this issue. A re-route of network services will be triggered at some point during the maintenance window, and a router will be rebooted to commit those changes. While there is no anticipated impact on customer workloads during the maintenance, be advised that this work is being done during this time. An update will be sent out later tonight once the work has been completed.

  2. resolved Dec 10, 2024, 02:49 AM UTC

    All maintenance has been completed at this time and was successfully completed as planned. All customer workloads remained up and online throughout the outage. Public connectivity would have experienced a dropped packet or two while traffic was temporarily re-routed through redundant devices. If you have any questions or concerns, please don't hesitate to put in a support ticket with your questions or requests. Jenzabar Cloud Infrastructure

Read the full incident report →

Notice October 14, 2024

VMware Host Failure in East Coast Datacenter

Detected by Pingoru
Oct 14, 2024, 03:31 PM UTC
Resolved
Oct 14, 2024, 07:31 PM UTC
Duration
3h 59m
Affected: North America East
Timeline · 3 updates
  1. identified Oct 14, 2024, 03:31 PM UTC

    At approximately 10:20am EST this morning, one of the VMware hosts failed due to a memory module/DIMM failure. All virtual servers running on that host would have been immediately automatically powered off, then powered back on once transferred to a different host within the cluster. Total downtime would have been approximately 1-3 minutes. All systems should now be functioning normally, and the failed host will be repaired and brought back into production later today.

  2. identified Oct 14, 2024, 06:40 PM UTC

    IBM engineers are engaged to repair the failed memory module on the offline host. All systems continue to function normally at this time.

  3. resolved Oct 14, 2024, 07:31 PM UTC

    The failed memory modules have been replaced, the host is fully booted, and is again hosting virtual workloads. The issue is now fully resolved.

Read the full incident report →

Notice August 4, 2024

*.jenzabarcloud.com DigiCert Wildcard certificate Revocation

Detected by Pingoru
Aug 04, 2024, 06:24 PM UTC
Resolved
Aug 14, 2024, 11:11 PM UTC
Duration
10d 4h
Affected: SONISJenzabar One & EXHigher ReachCX
Timeline · 4 updates
  1. investigating Aug 04, 2024, 06:24 PM UTC

    DigitCert has identified a vulnerability within certain subsets of their SSL certificates, impacting the *.jenzabarcloud.com certificate for some Managed Services customers. As a response, DigiCert has revoked this certificate on 8/3 and we are actively engaged in deploying the new one. If you have already provided us with your wildcard certificates, you remain unaffected by this situation. However, those impacted may encounter an invalid SSL certificate error when accessing affected servers - particularly RDS, JFA, and TEST servers. For any specific inquiries or concerns, please don't hesitate to reach out by submitting a ticket. -Managed Services

  2. investigating Aug 05, 2024, 02:14 AM UTC

    We have updated the certificate on all Production RDS servers at this time. Users may need to clear their cache / cookies to see the new certificate if they use the Web Client. If you continue to have issues please submit a support ticket. We will work to remedy TEST systems throughout the day tomorrow. -Managed Services Team

  3. monitoring Aug 05, 2024, 02:14 AM UTC

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

  4. resolved Aug 14, 2024, 11:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 19, 2024

IBM Cloud Services

Detected by Pingoru
Jul 19, 2024, 08:28 AM UTC
Resolved
Jul 20, 2024, 05:15 PM UTC
Duration
1d 8h
Affected: North America EastNorth America Central
Timeline · 7 updates
  1. investigating Jul 19, 2024, 08:28 AM UTC

    IBM has reported problems at both Datacenters Jenzabar utilizes for our SaaS services. This has caused intermittent outages for all Jenzabar customers. As soon as we have more information from IBM, we will provide an update. This outage started around 2:00 AM EST

  2. identified Jul 19, 2024, 12:25 PM UTC

    Although IBM also listed outages at the same time, we have determined a CrowdStrike update is the cause. Many of our clients are ok and online and did not experience any issues because the update did not make it to all systems. Crowdstrike has provided us with steps to resolve the problem. Our team is working to manually apply the fix to each system.

  3. identified Jul 19, 2024, 03:37 PM UTC

    The team is making good progress applying the fix Crowdstrike provided. We are almost finished with the North America East data center. Access is being restored as quickly as possible.

  4. identified Jul 19, 2024, 04:44 PM UTC

    We are continuing to work on a fix for this issue.

  5. monitoring Jul 19, 2024, 04:45 PM UTC

    We have a few production systems remaining and most client test systems. If you are still experiencing issues with a production system, please submit a ticket via https://support.jenzabar.net. Our team applied the changes needed to over 800 servers in five hours. Each system needed to be restarted into safe mode with networking support. A specific file was removed and then the system was restarted. We apologize for the inconvenience this has caused and we will continue to work to resolve any remaining issues.

  6. monitoring Jul 19, 2024, 07:31 PM UTC

    We are continuing to monitor for any further issues.

  7. resolved Jul 20, 2024, 05:15 PM UTC

    This incident has been resolved.

Read the full incident report →