- Level
- confirmed
- Worst impact
- Degraded
- Components
- Web Application
- Down Index
- 19of 100
What to do
Check whether you use Secureframe Web Application. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 33m it lasted.
Anything that failed between 2026-05-27 19:12 UTC and 2026-05-27 19:44 UTC may need a replay.Subscribe to Secureframe's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=secureframe works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Secureframe 5
- investigating
We are aware of issues with using the "Sign in with Microsoft" login to the Secureframe application. We have identified a cause and we are starting mitigation
provider
- identified
The issue is identified, and we are also seeing Microsoft Intune syncs failing due to a similar issue. Both fixes are forthcoming shortly.
provider
- identified
Azure Devops syncs are similarly affected, with the same fix planned.
provider
- monitoring
A fix has been implemented and we are monitoring.
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-9e7d8ed2da
Is Secureframe still down?
No, this incident was resolved 2026-05-27 19:44 UTC. For Secureframe's live state, see https://down.guide/secureframe.
How long did it last?
33m, from 2026-05-27 19:12 UTC to 2026-05-27 19:44 UTC, by the times Secureframe posted.
What was affected?
Secureframe named Web Application.
What caused it?
Secureframe hasn't published a root cause. If it does, it shows here.
Where does this come from?
Secureframe's official status page, https://status.secureframe.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.