Jenzabar Outage History

Started Jul 17, 2026, 02:43 AM UTC· resolved Jul 17, 2026, 05:17 PM UTC

1. investigating Jul 17, 2026, 02:43 AM UTC

   We are currently experiencing an issue with connectivity within our Google Cloud environment. Our team is actively investigating and working to resolve the problem with Google as quickly as possible. We appreciate your patience and will provide updates as more information becomes available.

2. resolved Jul 17, 2026, 05:17 PM UTC

   The issue affecting multiple Google Cloud services in the us-east1 has been fully resolved as of 3:30 AM PDT on July 17. The disruption was caused by a datacenter power infrastructure issue. Power has been restored, systems have been returned to normal operation, and all impacted services are now functioning normally.

Read the full incident report →

Started Jul 13, 2026, 08:38 PM UTC· resolved Jul 14, 2026, 01:44 AM UTC

1. investigating Jul 13, 2026, 08:38 PM UTC

   IBM is currently experiencing an issue within its data center. Our team is actively investigating the situation and working closely with IBM to restore service as quickly as possible. We appreciate your patience and will provide updates as more information becomes available.

2. resolved Jul 14, 2026, 01:44 AM UTC

   IBM Has resolved the networking issue. Per their statement: Network Specialists investigated and identified a routing issue on the backbone network affecting multiple regions. Network Specialists have mitigated the route issue by 21:47 UTC 13 July 2026.

Read the full incident report →

Started Jul 08, 2026, 06:53 PM UTC· resolved Jul 08, 2026, 10:36 PM UTC

1. investigating Jul 08, 2026, 06:53 PM UTC

   We are currently experiencing an issue within our Google Cloud environment. Our team is actively investigating and working to resolve the problem with Google as quickly as possible. If you are experiencing issues with sites not loading or other service disruptions, please submit a "System Down" ticket. This will help us accurately track the impact on your institution and prioritize our response efforts. We appreciate your patience and will provide updates as more information becomes available.

2. investigating Jul 08, 2026, 07:35 PM UTC

   We are continuing to investigate this issue.

3. identified Jul 08, 2026, 08:29 PM UTC

   Google has identified the issue and are working towards a resolution. We have noticed that many servers have become available again and some sites should be functioning. We will continue to let you know of updates as we gain more information.

4. resolved Jul 08, 2026, 10:36 PM UTC

   Google implemented a fix, and we've been monitoring the situation for the last couple of hours. Connectivity has remained stable during that time, so we are going to close out the incident. If you experience any issues that you believe may still be related to the outage, please submit a ticket. Thank you for your patience while Google worked through the issue!

Read the full incident report →

Started Dec 05, 2025, 08:00 AM UTC· resolved Dec 05, 2025, 09:12 AM UTC

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 →

Started Nov 18, 2025, 02:32 PM UTC· resolved Nov 18, 2025, 06:56 PM UTC

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 →

Started Oct 31, 2025, 05:50 PM UTC· resolved Nov 01, 2025, 11:07 AM UTC

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 →

Started Oct 22, 2025, 07:02 PM UTC· resolved Oct 22, 2025, 08:44 PM UTC

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 →

Started Sep 22, 2025, 03:30 PM UTC· resolved Sep 22, 2025, 05:13 PM UTC

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 →

Started Sep 18, 2025, 03:56 PM UTC· resolved Sep 18, 2025, 07:02 PM UTC

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 →

Started Apr 28, 2025, 01:31 PM UTC· resolved Apr 28, 2025, 03:25 PM UTC

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 →

Started Mar 29, 2025, 12:42 AM UTC· resolved Mar 29, 2025, 01:06 PM UTC

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 →

Started Dec 10, 2024, 08:37 PM UTC· resolved Dec 12, 2024, 01:42 PM UTC

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 →

Started Dec 09, 2024, 09:42 PM UTC· resolved Dec 10, 2024, 02:49 AM UTC

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 →