AppCheck NG Outage History

We have identified affected scans are are reassigning them to other hubs. Affected scans will show as aborted and then restarted. We are still investigating the cause of the incident.

All effected scans have now been reassigned to other public scan hubs, and no new scans are affected. We are continuing to investigate the initial cause of the incident.

We are investigating an issue causing 520 Unknown Error responses from AppCheck's API. The AppCheck portal is available and scheduled scans are running as expected.

We are currently investigating an issue preventing some users from signing in to AppCheck using Single Sign-On (SSO). We have identified the cause of the error and expect to have a solution deployed shortly. Scheduled scans will continue to run. Users are able to sign in without SSO.

We have identified a problem preventing GoScripts from running on private scan hubs when using the GoScripts development and testing interface in the AppCheck portal. This presents with a warning that the scan hub returned a "bad response". Only GoScript testing is affected, GoScripts in scans are functioning normally.

An issue has been detected which is causing erroneous findings in scan results in the AppCheck Portal. The cause has been identified and we are working on a solution.

We have identified an issue causing an error when attempting to edit the settings for certain scans. A fix has been developed and is currently being tested ready for deployment.

An error is causing the warning "AppCheck Update Service connection failed" to be incorrectly generated on a number of Infrastructure scans. Our development team are working to correct this. Until this is resolved, this warning message should be ignored.

An issue has been identified which is causing some scans to appear as Running after they have in fact completed. We believe this is affecting only scans which include Infrastructure scanning. Our development team have identified the cause and are working on a solution. We are updating affected scans as we identify them, in most cases no action should be required on the customer side. If you believe your scan may still be affected compare the run time and results with previous scans – if it has run longer than previous scans and has a similar number of findings then you can abort the current scan. If you are in doubt, please contact AppCheck Support.

We are investigating an issue affecting some Word reports generated in the AppCheck portal. Affected reports are raising an error when attempting to open them in some versions of Microsoft Word.

The documentation for AppCheck's API is currently unavailable. The API itself is functioning normally. We have identified the cause of the problem and are working on a fix.

The Asset Discovery screen is currently not visible in the AppCheck portal. Asset discovery is continuing to run in the background, only visibility of the results is affected.

We have identified an issue causing an error when users attempt to access or configure their Trust Monitor dashboard.

We are continuing to work on a fix for this issue.

We are aware of an issue affecting a subset of private scan hubs being used for internal infrastructure scans. Affected hubs are failing to clear down temporary files and therefore running out of storage space, which prevents scans from running or existing scans from completing. We have resolved the root cause, so no more hubs should be affected, and are investigating a solution for already affected hubs.

We are investigating an issue affected the ability to start scans. A number of scans are currently listed as queued or initalising.