- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
- Down Index
- 12of 100
What to do
Check whether you use Keeper in us. 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-05-15 22:00 UTC and 2024-05-15 22:00 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
From 2:45PM to 3:00PM PST, several of the Keeper application API instances in the US region were responding with HTTP 500 errors due to an internal application error. The Keeper DevOps team identified the error and restarted those affected instances. The software engineering team has been investigating the root cause and will be addressing in an upcoming backend release.
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-9a730583bd
Is Keeper still down?
No, this incident was resolved 2024-05-15 22:00 UTC. For Keeper's live state, see https://down.guide/keeper.
How long did it last?
0m, from 2024-05-15 22:00 UTC to 2024-05-15 22:00 UTC, by the times Keeper posted.
What was affected?
Keeper named in us.
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.