Live / Veracode / Incident
Veracode: Delays in Static pre-scan and scan results.
Veracode · veracode.comMinor incidentResolved2026-10-28 23:08 UTC
Public — what happened
Summary
Veracode reported a minor incident involving delays in static pre-scan and scan results. The company said it began investigating at 21:39 UTC on 2026-10-28, and by 22:10 UTC it said it had found the issue and was putting a fix in place. The incident was marked resolved at 23:08 UTC the same day. Veracode did not say in its updates what caused the delays or which customers were affected.
Affected
Static Analysis Services
Timeline
- Started — 2026-10-28 21:39 UTC
- Investigating — 2026-10-28 21:39 UTC
- Identified — 2026-10-28 22:10 UTC
- Resolved — 2026-10-28 23:08 UTC · 1h 29m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Veracode against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Veracode: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Veracode report →
More from Veracode
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.