- Level
- confirmed
- Worst impact
- Degraded
- Components
- SCIM provisioning with Azure
- Down Index
- 19of 100
What to do
Check whether you use Keeper SCIM provisioning with Azure. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 6m it lasted.
Anything that failed between 2023-11-07 00:24 UTC and 2023-11-07 01:30 UTC may need a replay.Subscribe to Keeper's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=keeper works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Keeper 2
- identified
Today's backend release introduced errors with SCIM provisioning via Azure. A fix has been created and it is going through the deployment process right now. ETA 4:35PM PST.
provider
- resolved
The SCIM issue with Azure 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-873ea93612
Is Keeper still down?
No, this incident was resolved 2023-11-07 01:30 UTC. For Keeper's live state, see https://down.guide/providers/keeper.
How long did it last?
1h 6m, from 2023-11-07 00:24 UTC to 2023-11-07 01:30 UTC, by the times Keeper posted.
What was affected?
Keeper named SCIM provisioning with Azure.
What caused it?
Keeper hasn't published a root cause. If it does, it shows here.
Where does this come from?
Keeper's official status page, https://statuspage.keeper.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.