SecurityScorecard status history
Current state: operational — “All Systems Operational” per https://status.securityscorecard.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do SecurityScorecard incidents last?
From 6 incidents with a vendor-posted start and resolve time. Longest on record: Custom Scorecard Issue — 10.7 h (2026-08-14 10:43 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (6)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-08-14 10:43 UTC | Custom Scorecard Issue | resolved | minor | 10 h 44 min |
| 2026-05-25 12:20 UTC | Scorecard page load error | resolved | major | 1 h 39 min |
| 2026-04-20 15:19 UTC | Atlas and Questionnaires issue | resolved | minor | 4 h 42 min |
| 2025-12-01 15:29 UTC | Evidence Locker Issue | resolved | minor | 1 h 44 min |
| 2025-11-25 16:35 UTC | Microsoft Entra ID users may experience login issues | resolved | minor | 44 min |
| 2025-10-20 12:31 UTC | Some Platform Services Degraded Related to AWS Incident | resolved | minor | 9 h 17 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch SecurityScorecard with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"securityscorecard"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
