Jenzabar Outage History

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.

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.

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!

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/

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!

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.

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.

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

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

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.

This incident has been resolved.

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.

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

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

This incident has been resolved.