Secureframe: Invalid Authentication Tokens leading to 500s
Timeline of updates
- resolved
This incident has been resolved.
From Secureframe’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.secureframe.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Secureframe, started 2022-06-07 18:44 UTC, resolved after 4.6 h, 1 update(s).
- Title
- Invalid Authentication Tokens leading to 500s
- Vendor
- Secureframe
- Date
- URL
- https://rewindex.com/company/secureframe/incidents/nj44k04yvbzg
Secureframe profileRecent Secureframe incidentsAll outages on June 7, 2022Secureframe in June 2022MarkdownJSON