Veracode incident

Consultation Errors

Minor Resolved View vendor source →

Veracode experienced a minor incident on August 21, 2025, lasting 9h 18m. The incident has been resolved; the full update timeline is below.

Started
Aug 21, 2025, 11:40 AM UTC
Resolved
Aug 21, 2025, 08:58 PM UTC
Duration
9h 18m
Detected by Pingoru
Aug 21, 2025, 11:40 AM UTC

Update timeline

  1. investigating Aug 21, 2025, 11:40 AM UTC

    We are currently investigating this issue.

  2. investigating Aug 21, 2025, 12:13 PM UTC

    We are continuing to investigate this issue.

  3. investigating Aug 21, 2025, 12:25 PM UTC

    Other platform services and scanning services are not impacted by this.

  4. investigating Aug 21, 2025, 01:55 PM UTC

    We are continuing to investigate this issue.

  5. investigating Aug 21, 2025, 03:00 PM UTC

    We have confirmed that this incident has no impact on scanning or other services on the Veracode platform. The impact is limited to customers that are attempting to schedule a meeting with a Veracode security consultant. Veracode continues to investigate and are widening the investigation to include the third party services that are used to provide the scheduling and meeting services for the Consultation Service. The next update will be provided before 1:00 PM EDT.

  6. investigating Aug 21, 2025, 04:56 PM UTC

    We are continuing to investigate this issue.

  7. investigating Aug 21, 2025, 06:12 PM UTC

    We have opened a Sev1 issue with one of our third party vendors and are working together with this partner to find a root cause for the issue. We will update this page before 4:30PM EDT.

  8. identified Aug 21, 2025, 06:50 PM UTC

    We have identified the cause of the issue and are developing a fix. An estimate for when the fix will be fully tested, deployed, and available will be provided when the nature of the fix is known.

  9. resolved Aug 21, 2025, 08:58 PM UTC

    Consultation Scheduling capability is restored with a temporary solution that contacts Veracode Support to coordinate the scheduling. The full functionality will be restored in an upcoming release.