Live / Veracode / Incident
Veracode · veracode.comResolved2026-11-13 16:39 UTC
Public — what happened
Summary
Veracode said emails sent to its [email protected] address might arrive late, starting 2026-11-12 at 20:19 UTC, and it attributed this to a problem at one of its vendors. The company suggested customers open support cases through the Veracode Platform or the Community Portal instead, and stated that its platform and services were working normally. By 13:21 UTC on 2026-11-13 Veracode said the vendor had made significant progress on recovery, though delays were still possible, and the incident was later marked resolved at 16:39.
Affected
Platform
Timeline
- Started — 2026-11-12 20:19 UTC
- Identified — 2026-11-12 20:19 UTC (2 updates)
- Resolved — 2026-11-13 16:39 UTC · 20h 20m 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 47, 2026, our weekly internet health report.