- Level
- confirmed
- Worst impact
- Major outage
- Down Index
- 30of 100
What to do
Check whether your product depends on Keeper. 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 0m it lasted.
Anything that failed between 2024-01-01 15:30 UTC and 2024-01-01 15: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 1
- resolved
AWS RDS cluster instances were automatically rebooted at approximately 09:27 Central (04:27 UTC). We are investigating the issue with the AWS team and will update our statuspage with the findings.
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-09157aec48
Is Keeper still down?
No, this incident was resolved 2024-01-01 15:30 UTC. For Keeper's live state, see https://down.guide/keeper.
How long did it last?
0m, from 2024-01-01 15:30 UTC to 2024-01-01 15:30 UTC, by the times Keeper posted.
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.