Is Cadmium down?

We are currently investigating reports of iOS app stats data being under counted for the attendee Eventscribe Mobile App. We do not believe Android device are affected. We are continuing to investigate and provide an update when available. Next update by: July 27 at 12:30 PM ET.

We've identified an issue affecting how app statistics were captured for iOS devices. Beginning on April 8, 2026, a change reduced how frequently some iOS activity was recorded for apps on the 26.04.08 build or later. As a result, a portion of statistics from that period may be incomplete. Android was not affected. Data for Android devices has continued to report as expected throughout this period. A fix is in progress and we expect a resolution shortly. Our next update will be tomorrow morning.

We've confirmed a fix for the iOS app statistics issue affecting the Eventscribe Mobile App. We'll release the update to the App Store later today. We appreciate your patience while we resolved this, and we'll post a final update once the release is live.

This issue has been resolved and is included in our most recent mobile app release. Earlier, a change reduced how frequently some iOS activity was recorded for apps on the 26.04.08 build or later, beginning April 8, 2026. As a result, a portion of statistics from that period may be incomplete. To see the fix, users need to be on version 26.07.28 or later. We recommend updating to the latest version to ensure app statistics are captured as expected going forward. Android was not affected and continued to report as expected throughout.

We are aware of a connectivity issue currently affecting some customers. Cloudflare, one of our third-party network providers, is experiencing service disruptions that may impact access to Cadmium products. Our team is monitoring the situation closely and will continue to provide updates as more information becomes available. Thank you for your patience while Cloudflare works to resolve the issue.

Cloudflare has reported that traffic engineering efforts have successfully mitigated the majority of congestion and packet drops. Cadmium services are now largely stable, though a small number of customers may still experience intermittent errors, particularly for services with origins in North America. We are continuing to monitor the situation closely and will provide additional updates as the remaining impact is fully resolved.

Cadmium services are currently stable following the earlier Cloudflare-related connectivity issue. Cloudflare has reported that traffic engineering efforts have mitigated the majority of congestion and packet drops, and we are continuing to monitor for any residual impact. We will keep this notice open while we confirm continued stability.

This issue has been resolved. Cadmium services have remained stable following Cloudflare’s mitigation efforts, and we are no longer observing related connectivity issues. We will continue standard monitoring and appreciate your patience.

We are aware of an issue where some customers are reporting that data is not being populated in their analytics dashboards. Our team is actively investigating the issue and working to identify the root cause. We will provide additional updates as more information becomes available.

We have identified the root cause of the issue impacting analytics dashboard data population. The issue was caused by a breaking change introduced in the API of one of our third-party vendors. Our team is actively working on implementing the necessary updates to restore normal data processing as quickly as possible. We will continue to provide updates as progress is made.

Our team has implemented a fix for the analytics dashboard data population issue, and the changes are currently undergoing QA testing. We will provide additional updates as testing is completed and deployment timing is confirmed.

We have successfully applied and validated the fix for a subset of customers. Deployment of the fix to all customers is now underway. Due to the scope of the rollout, it will take some time for the changes to fully propagate across all environments. We will continue to provide updates as deployment progresses.

The issue impacting analytics dashboard data population has been resolved. The fix has now been deployed to all customers, and we are continuing to monitor the system to ensure everything is functioning as expected.

The issue impacting analytics dashboard data population has been fully resolved. After a period of monitoring, we have confirmed that the system is functioning as expected and all dashboards are populating data normally.

Incident window: 5/7/2026 9:02 PM ET – 5/8/26 7:40 AM ET Last night, EthosCE LMS sites experienced intermittent 500 errors on pages that use search functionality. The issue has been resolved and all sites are operating normally. What happened At 9:02 PM ET, one of the data nodes in the OpenSearch cluster supporting EthosCE became unavailable. The remaining nodes were near disk capacity, which prevented the cluster from automatically rebalancing and self-healing. At 4:51 ET, the original node came back online and sites were operational. While the system was online, the replicas were still in a bad state and could not handle a failover. At 7:41, space was added to the replicas and they were fully operational again. Impact Between 9:02 PM ET on 5/7 and 4:51ET on 5/8, intermittent 500 errors on EthosCE LMS pages that rely on the Drupal Search API. After 4:51 ET, all site were fully operational again. Course content, user accounts, and non-search functionality were not affected. No data was lost. Resolution Engineering restored the failed node and brought the cluster back to a healthy state. Search-dependent pages have been verified as functioning normally. We apologize for the disruption and appreciate your patience.

Incident window: 5/7/26 8:15 PM PM PDT – 8:57 PM ET Yesterday evening, customers experienced widespread errors and timeouts when using the platform. Service has been fully restored. What happened Our primary database became overloaded under heavy concurrent activity, causing requests to stall. The system failed over standby database at 8:27 PM ET, which resolved the database issue. However, our application servers did not automatically reconnect to the new database and had to be replaced with fresh instances to restore service. Impact • Elevated errors and timeouts across the platform • Service restored progressively as new application servers came online • No data was lost Resolution Full service was restored by 8:57 PM ET and the platform has been stable since.