Deque Outage History

Earlier today, some users may have experienced slower than usual performance on Axe Developer Hub. Our engineering team identified the issue and deployed a hotfix which has now resolved the problem. Axe Developer Hub is fully operational and performing as expected. If you continue to experience any issues, please contact us at [email protected].

On September 15, 2026, starting at approximately 1:00 PM EST, some users experienced an error when attempting to use axe Assistant on Deque University. Users were unable to submit messages and received the following error: "Error encountered while processing user chat message." Our engineering team investigated the issue and has confirmed it has now been resolved. axe Assistant is fully operational and users should be able to use the chat functionality without any issues. We apologize for the disruption caused during this period. If you continue to experience any issues, please contact us at [email protected].

Some users were encountering a Privacy warning when accessing Deque University. The issue has been fixed and access should now work as expected. Please contact [email protected] if you continue to experience any issues.

Some users may have experienced brief, intermittent issues logging in or accessing our platform for a few minutes, including delays or "Failed to initialize auth" errors. The issue has been resolved, and full service has been restored. We apologize for any inconvenience this may have caused. If you continue to experience login issues, please contact [email protected]

Version 8.8.2 was applied to all customers on versions 8.8.0 and 8.8.1. This patch fixed an issue where some pages were failing with proxy-related errors. No action is required to resolve the issue, and scans will run normally without this error going forward. Please feel free to reach out to [email protected] if you have any further questions.

We have resolved the issue with the DevTools server outage. It was the result of a slow internal API request that caused the outage when a new version of the axe DevTools browser extension was released. If you have any further questions, please reach out to the Deque Helpdesk.

axe Assistant was unavailable in Deque University for a brief period today due to an upstream incident with our AI provider. The issue was resolved shortly after and axe Assistant is now functioning normally. We apologize for any inconvenience caused. Please feel free to reach out to [email protected] if you have any further questions.

Between approximately 3:00 PM and 4:05 PM EDT, automated assessments in Intelligent Guided Tests were not completing, causing all elements to appear as "Pending Review." Users were still able to complete IGTs manually during this period. The issue was caused by an unexpected disruption with a third-party AI service provider. The provider has since restored service, and automated IGT assessments are now functioning normally. No action is required from users. We apologize for any inconvenience and are reviewing safeguards to reduce the impact of similar third-party disruptions in the future. For any questions or assistance, please reach out to us at [email protected].

We are aware that some users are experiencing login issues with the axe Mobile Android Analyzer application following a recent update. Our team has investigated and resolved the issue. Users should now be able to sign in successfully. If you continue to experience any issues, please contact our support team at [email protected].

Axe Assistant is now fully operational. The earlier disruption was caused by a temporary overload on Anthropic's API servers, which is a third-party dependency outside of Deque's control. The issue has been resolved on Anthropic's end and all services are functioning as expected. We apologize for any inconvenience caused.

Axe Assistant was reported as unavailable and users were experiencing errors. The root cause was identified as an outage on the Claude (Anthropic) side, as Axe Assistant relies on one of their AI models. The issue was external and outside Deque's control. Service was confirmed restored shortly after.

This incident has been resolved.

Axe Reports 2.3.3 with the fix was released and confirmed working.

On December 26, 2025, dequeuniversity.com experienced an outage (Duration: 37 minutes). During this time, users were unable to access the site. The issue has been fully resolved, and the site is operating normally.

On January 23, 2026, dequeuniversity.com experienced an outage at 11:44:30 GMT+5:30 (Duration: 13m 2s). During this time, users were unable to access the site. The issue has been fully resolved, and the site is operating normally.

This incident has been resolved.

Some users may have experienced slowness or timeouts accessing agora.dequecloud.com over multiple brief windows (1–8 minutes each) beginning April 10, 2026. We have implemented a fix and are actively monitoring the service. We apologize for any inconvenience caused. For any further queries, please reach us at [email protected].

This issue has been resolved. Remediate should be functioning as expected

The fix was deployed and validated - the service is running normally.

On March 31, 2025, dequeuniversity.com experienced an outage between 4:08 PM and 4:16 PM Eastern. During this time, users were unable to access the site. The issue has been fully resolved, and the site is operating normally. We apologize for any inconvenience and appreciate your patience. For any further queries, please reach out to [email protected].

This incident has been resolved. For any questions or assistance, please reach out to us at [email protected].

This incident has been resolved. For any questions or assistance, please reach out to us at [email protected].

We identified and resolved an issue affecting the Profile page on Deque University. Users were encountering a "page cannot be found" error (HTTP 404). The issue has been fully resolved, and the Profile page is now accessible. We apologize for any inconvenience. For any further queries, please reach out to [email protected].

This incident has been resolved.

The fix has been deployed, and the issue is resolved now. For any further queries, please reach out to [email protected]