Veracode: vendor-reported major incident on September 28 (tracked 1h 31m)
Sep 28, 05:41 PM → Sep 28, 07:13 PM · 1h 31m · high
Veracode reported a major-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 1h 31m, from Mon, 28 Sep 2026 17:41:37 GMT to Mon, 28 Sep 2026 19:13:30 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.
Impact
PulseWatch recorded no user reports for this incident, so it cannot describe what users experienced. The vendor's own status page is the only source PulseWatch has for it.
Incident timeline
- Sep 28, 05:41 PM
The vendor reported a major-impact incident on its own status page; PulseWatch began tracking it
- Sep 28, 05:41 PM
Status updated: possible issue
- Sep 28, 07:13 PM
PulseWatch closed the incident
Official updates
- Sep 28, 05:41 PM
Veracode reported the incident on its status page.
View official source