Keeper status history
Current state: operational — “All Systems Operational” per https://statuspage.keeper.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Keeper incidents last?
From 13 incidents with a vendor-posted start and resolve time. Longest on record: Direct record sharing enforcement issue — 7.9 h (2026-06-19 15:05 UTC). Excluded, never estimated: 1 scheduled maintenance. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (14)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-09 16:32 UTC | SMS 2FA issues with AWS aggregator | resolved | minor | 3 h 11 min |
| 2026-07-31 06:00 UTC | EU KeeperPAM router and gateway connections | postmortem | none | 0 min |
| 2026-07-08 18:51 UTC | Resolved: Keeper Gateway and KSM API errors | resolved | major | 22 min |
| 2026-06-26 22:43 UTC | GovCloud region maintenance | resolved | maintenance | 43 min |
| 2026-06-19 15:05 UTC | Direct record sharing enforcement issue | resolved | minor | 7 h 54 min |
| 2026-03-31 03:00 UTC | API errors during maintenance operation | resolved | major | 0 min |
| 2026-03-23 17:07 UTC | Resolved: KeeperPAM Connection Errors in US Data Center | postmortem | major | 4 h 37 min |
| 2026-03-16 18:25 UTC | Resolved: KeeperPAM Connection Errors in US Data Center | postmortem | major | 26 min |
| 2026-02-19 05:30 UTC | US GovCloud Region - Login Errors Resolved | postmortem | none | 0 min |
| 2025-12-02 22:48 UTC | EU data center login errors - Resolved | postmortem | minor | 1 h 59 min |
| 2025-10-20 17:25 UTC | AWS outage affecting KeeperPAM connections and scheduled rotations | resolved | major | 3 h 05 min |
| 2025-10-20 09:20 UTC | Email delivery in US region due to AWS US-EAST outage | resolved | minor | 5 h 56 min |
| 2025-09-10 15:42 UTC | EU Region login API errors | postmortem | major | 6 min |
| 2025-08-21 17:36 UTC | Resolved: Vault login API errors | resolved | none | 0 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Keeper with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"keeper"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}