InComm Payments Dashboard

We are actively exploring potential mitigation options to address the sub-optimal routing and reduce the impact on affected origin fetch traffic. In parallel, we are working with the third-party provider to address the underlying geolocation issue. We will provide further updates as more information becomes available.

We are providing an update on the ongoing service disruption. The Middle East (UAE) Region (ME-CENTRAL-1) has suffered damage as a result of the conflict in the Middle East and is currently unable to reliably support customer applications. While some workloads continue to function normally, we strongly recommend customers migrate all accessible resources to other Regions and restore inaccessible resources from remote backups as soon as possible. Relevant billing operations are currently suspended while we restore normal operations in this AWS Region. This process is expected to take several months.

Core Cloud Services - Data Protection: Zscaler has detected an issue with its zscaler.net, zscloud.net Cloud. Customers with an HTTP/2 Header Profile applied via a URL Control Policy may experience intermittent login failures when accessing claude.ai. The HTTP/2 profile disrupts the authentication flow, which may prevent login from completing successfully. All other traffic forwarding and policy enforcement remain unaffected.We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.Latest Update - Wed, 12 Aug 2026 06:54:30 UTCThe fix developed by Zscaler is currently undergoing validation. A corrected build has been prepared and is proceeding through the testing and validation pipeline. Once validation is successfully completed, the fix will be submitted for production deployment. Existing interim mitigations continue to remain active during this period. The next update will be provided when deployment timelines are confirmed.Update - Mon, 10 Aug 2026 16:39:38 UTCWe have identified the root cause of the issue and are currently assessing mitigation options and next steps.Update - Mon, 10 Aug 2026 17:20:15 UTCWe have identified the issue as a software-related regression affecting login access to claude.ai in certain environments. Our engineering team is actively working on a permanent fix, and interim mitigation measures remain in place while that work is underway. We are coordinating across teams and will provide further updates as we have more information on the fix timeline and deployment plan.Update - Tue, 11 Aug 2026 16:00:44 UTCZscaler has completed development of the fix and the validation is currently in progress. Interim mitigations remain in place while verification continues. We will share a further updates, including verification status and next steps once available.Update - Wed, 12 Aug 2026 03:13:05 UTCZscaler has completed development of the fix, and validation is currently in progress. The corrected build is being prepared for further validation and testing. Following successful validation, the fix will be submitted for production deployment. Interim mitigations remain in place while validation continues. We will provide the next update once deployment plans are available.Update - Wed, 12 Aug 2026 06:54:30 UTCThe fix developed by Zscaler is currently undergoing validation. A corrected build has been prepared and is proceeding through the testing and validation pipeline. Once validation is successfully completed, the fix will be submitted for production deployment. Existing interim mitigations continue to remain active during this period. The next update will be provided when deployment timelines are confirmed.